Feature request #8346. We'll get to it.
But seriously, everything takes time. It is not as simple as you say, but it
is not terribly difficult either. If this was the only thing to do, we'd do
it, but it has to fit in with the other priorities. There are just thousands
of other things to do as well. Since there is an effective workaround (use
another font), the priority is fairly low but not zero. Certainly lower than
supporting a new language IMHO (which can be hard or easy depending on the
language). For example, if I can push for added Cyrillic glyphs in our fonts
in order to support Central Asian languages that use as yet unsupported
Cyrillic characters, I'd do that before pushing for supporting multiple
glyphs in a single font.
Chris Pratley
Group Program Manager
Microsoft Word
-----Original Message-----
From: John Hudson [mailto:tiro@tiro.com]
Sent: Thursday, January 20, 2000 2:42 PM
To: Unicode List
Subject: RE: Language Tagging And Unicode
At 02:22 PM 20-01-00 -0800, Chris Pratley wrote:
>But regarding the topic du jour (Serbian vs. Russian glyphs in fonts), it
is
>more likely that we would work on getting a new language (e.g. Khmer or
>Yoruba) to function in the apps before going back and adding the nicety of
>language-selectable glyphs from a single font. Currently the
Serbian-Russian
>problem (just like the CJK problem) can be worked around by using a Serbian
>font rather than a Russian one, so that lessens the urgency of that problem
>relative to being unable to use Khmer at all (in a Unicode way - I know
>there are hacks to support Khmer but these have big interop problems)
If the one hand of Microsoft knows what the other hand of Microsoft is
doing, it should be possible to add 'the nicety of language selectable
glyph from a single font' simply by supporting the registered OpenType
layout feature /locl/.
John Hudson
Tiro Typeworks
Vancouver, BC
www.tiro.com
tiro@tiro.com
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:58 EDT