A last missing link for interoperable representation

[Marcel Schneider via Unicode]

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