petercon at microsoft.com
Mon Sep 30 00:12:21 CEST 2013
For the platform on which I work, there are fonts that have broad Latin coverage, and matching fonts to language tags is something we deal with in several components. We can certainly “know” that unifon implies Latin script, but having that in the LSTR would have been helpful.
Sent from Windows Mail
From: John Cowan
Sent: Saturday, September 28, 2013 12:07 PM
To: Peter Constable
Cc: Mark Davis ☕, ietf-languages at iana.org
Peter Constable scripsit:
> However, if you receive content tagged "hup-unifon", that plus the
> LSTR doesn't tell you enough to know what the script is so that you
> can make processing decisions, such as choosing an appropriate font.
You either know what "unifon" means or you don't. If you do, that tells
you that you need a font with Unifon characters. Knowing that it's a
subset of the Latin script isn't really that helpful, as most Latin fonts
don't handle the whole script anyway.
John Cowan <cowan at ccil.org>
Yakka foob mog. Grug pubbawup zink wattoom gazork. Chumble spuzz.
--Calvin, giving Newton's First Law "in his own words"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ietf-languages