Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-17 Thread Marcel Schneider via Unicode
On 17/01/2019 12:21, Philippe Verdy via Unicode wrote: [quoted mail] But the French "espace fine insécable" was requested long long before Mongolian was discussed for encodinc in the UCS. The problem is that the initial rush for French was made in a period where Unicode and ISO were competing

Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-17 Thread Marcel Schneider via Unicode
On 17/01/2019 14:36, I wrote: […] The only thing that searches have brought up It was actually the best thing. Here’s an even more surprising hit: B. In the rules, allow these characters to bridge both alphabetic and numeric words, with: * Replace MidLetter by

Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-17 Thread Marcel Schneider via Unicode
On 17/01/2019 12:21, Philippe Verdy via Unicode wrote: [quoted mail] But the French "espace fine insécable" was requested long long before Mongolian was discussed for encodinc in the UCS. Then we should be able to read its encoding proposal in the UTC document registry, but Google Search se

Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-17 Thread Philippe Verdy via Unicode
Le jeu. 17 janv. 2019 à 05:01, Marcel Schneider via Unicode < unicode@unicode.org> a écrit : > On 16/01/2019 21:53, Richard Wordingham via Unicode wrote: > > > > On Tue, 15 Jan 2019 13:25:06 +0100 > > Philippe Verdy via Unicode wrote: > > > >> If your fonts behave incorrectly on your system becau

Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-17 Thread Marcel Schneider via Unicode
Courier New was lacking NNBSP on Windows 7. It is including it on Windows 10. The tests I referred to were made 2 years ago. I confess that I was so disappointed to see Courier New unsupporting NNBSP a decade after encoding, while many relevant people in the industry were surely aware of its role

Re: NNBSP (was: A last missing link for interoperable representation)

2019-01-16 Thread Marcel Schneider via Unicode
On 16/01/2019 21:53, Richard Wordingham via Unicode wrote: On Tue, 15 Jan 2019 13:25:06 +0100 Philippe Verdy via Unicode wrote: If your fonts behave incorrectly on your system because it does not map any glyph for NNBSP, don't blame the font or Unicode about this problem, blame the renderer (

NNBSP (was: A last missing link for interoperable representation)

2019-01-16 Thread Richard Wordingham via Unicode
On Tue, 15 Jan 2019 13:25:06 +0100 Philippe Verdy via Unicode wrote: > If your fonts behave incorrectly on your system because it does not > map any glyph for NNBSP, don't blame the font or Unicode about this > problem, blame the renderer (or the application or OS using it, may > be they are very