Re: Encoding italic

Responding to David Starner, > I might complain about the people who claim to like plain text yet would > only be happy with massive changes to it, though. Most movie lovers welcomed talkies. People are free to cling to their rotary phones as long as they like.  They just can't press the pou

Re: Encoding italic

On Tue, Jan 15, 2019 at 5:17 PM James Kass via Unicode wrote: > Enabling plain-text doesn't make rich-text poor. > Adding italics to Unicode will complicate the implementation of all rich text applications that currently support italics. > People who regard plain-text with derision, disdain, o

Re: Encoding italic (was: A last missing link)

Victor Gaultney wrote, > Use of variation selectors, a single character modifier, or combining > characters also seem to be less useful options, as they act at the individual > character level and are highly impractical. They also violate the key concept > that italics are a way of marking a

Re: Encoding italic

On 16/01/2019 02:15, James Kass via Unicode wrote: Enabling plain-text doesn't make rich-text poor. People who regard plain-text with derision, disdain, or contempt have every right to hold and share opinions about what plain-text is *for* and in which direction it should be heading. Such opin

Re: Encoding italic

Enabling plain-text doesn't make rich-text poor. People who regard plain-text with derision, disdain, or contempt have every right to hold and share opinions about what plain-text is *for* and in which direction it should be heading.  Such opinions should receive all the consideration they d

Re: Encoding italic (was: A last missing link)

On Tue, Jan 15, 2019 at 1:47 PM James Kass via Unicode wrote: > > Although there probably isn't really any concerted effort to "keep > plain-text mediocre", it can sometimes seem that way. > Dennis Ritchie allegedly replied to requests for new features in C with “If you want PL/I, you know where

Re: A last missing link for interoperable representation

On 15/01/2019 13:25, Philippe Verdy via Unicode wrote: Note that even if this NNBSP character is not mapped in a font, it should be rendered correctly with all modern renderers (the mapping is necessary only when a font design wants to tune its metrics, because its width varies between 1/8 and 1

Re: Encoding italic (was: A last missing link)

Although there probably isn't really any concerted effort to "keep plain-text mediocre", it can sometimes seem that way. As we've been told repeatedly, just because something has been done over and over again doesn't mean that there's a precedent for it. Using spans of text as a general in

wws dot org

Dear list, I am happy to report that www.worldswritingsystems.org is now online. The web site is a joint venture by — Institut Designlabor Gutenberg (IDG), Mainz, Germany, — Atelier National de Recherche Typographique (ANRT), Nancy, France and — Script Enc

Re: Encoding italic (was: A last missing link)

Hi You are the gentleman who kindly made the Gentium typeface open source. Thank you for your generous gift to the world. > Use of variation selectors, a single character modifier, or combining characters also seem to be less useful options, as they act at the individual character level and

Encoding italic (was: A last missing link)

I've been alerted to this thread by a friend, so just rejoined in order to respond. I'm currently doing research into italics. Some of the confusion and disagreement about italics centers around whether it is typographic markup or textual content. Both historically and currently italics can be

Re: A last missing link for interoperable representation

Martin J. Dürst wrote: So rich text technology is already way ahead when it comes to styled text. Do we want to encode background-color variant selectors in Unicode? If yes, how many? Yes. You would only need one. Background colour was a feature of teletext in the United Kingdom from 1976.

Re: A last missing link for interoperable representation

Note that even if this NNBSP character is not mapped in a font, it should be rendered correctly with all modern renderers (the mapping is necessary only when a font design wants to tune its metrics, because its width varies between 1/8 and 1/6 em (the narrow space is a bit narrower in traditional E

Re: A last missing link for interoperable representation

On 15/01/2019 10:24, Philippe Verdy via Unicode wrote: Le lun. 14 janv. 2019 à 20:25, Marcel Schneider via Unicode mailto:unicode@unicode.org>> a écrit : On 14/01/2019 06:08, James Kass via Unicode wrote: > > Marcel Schneider wrote, > >> There is a crazy typeface out there,

Re: A last missing link for interoperable representation

On 2019-01-15, Philippe Verdy via Unicode wrote: > This is not for Mongolian and French wanted this space since long and it > has a use even in English since centuries for fine typography. > So no, NNBSP is definitely NOT "exotic whitespace". It's just that it was > forgotten in the early stages o

Re: A last missing link for interoperable representation

> On 15 Jan 2019, at 02:18, Richard Wordingham via Unicode > wrote: > > On Mon, 14 Jan 2019 16:02:05 -0800 > Asmus Freytag via Unicode wrote: > >> On 1/14/2019 3:37 PM, Richard Wordingham via Unicode wrote: >> On Tue, 15 Jan 2019 00:02:49 +0100 >> Hans Åberg via Unicode wrote: >> >> On 14

Re: A last missing link for interoperable representation

Le lun. 14 janv. 2019 à 20:25, Marcel Schneider via Unicode < unicode@unicode.org> a écrit : > On 14/01/2019 06:08, James Kass via Unicode wrote: > > > > Marcel Schneider wrote, > > > >> There is a crazy typeface out there, misleadingly called 'Courier > >> New', as if the foundry didn’t anticipat

Re: A last missing link for interoperable representation

On 15/01/2019 03:02, Asmus Freytag via Unicode wrote: On 1/14/2019 5:41 PM, Mark E. Shoulson via Unicode wrote: On 1/14/19 5:08 AM, Tex via Unicode wrote: This thread has gone on for a bit and I question if there is any more light that can be shed. BTW, I admit to liking Asmus definition for