Re: A last missing link for interoperable representation

From: Marcel Schneider via Unicode <unicode_at_unicode.org>
Date: Mon, 14 Jan 2019 20:14:34 +0100

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 anticipate that at some point it
>> would be better called "Courier Obsolete". ...
>
> ๐ด๐‘Ÿ๐‘ก ๐‘›๐‘œ๐‘ข๐‘ฃ๐‘’๐‘Ž๐‘ข seems a bit ๐‘๐‘Ž๐‘ ๐‘ <i>รฉ</i> nowadays, as well.
>
> (Had to use mark-up for that โ€œspanโ€ of a single letter in order to
> indicate the proper letter form. But the plain-text display looks
> crazy with that HTML jive in it.)
>

I apologize for seeming to question the font name ๐‘๐‘’๐‘Ÿ ๐‘ ๐‘’ while targeting only
the fact that this typeface is not updated to support the <NNBSP>. It just
looks like the grand name is now misused to make people believe that if
**this** great font is unsupporting <NNBSP>, it has a good reason to do so,
and we should keep people off using that โ€œexotic whitespaceโ€ otherwise than
โ€œintended,โ€ ie for Mongolian. Since fortunately TUS started backing its use
in French (2014) and ended up raising this usage to the first place, I canโ€™t
see why major vendors are both using this obsolete font as monospace default
in main software *and* are not seeming to think at updating its coverage.

OK, in fact I *can* see a โ€œgoodโ€ reason, that Iโ€™ve hinted in the cited ticket,
but I wonโ€™t be going to dump it on the List again and again.

Thanks for pointing the flaw in my wording.

Best regards,

Marcel
Received on Mon Jan 14 2019 - 13:15:04 CST

This archive was generated by hypermail 2.2.0 : Mon Jan 14 2019 - 13:15:04 CST