Is your concern that ISO-Latin-1 is too hard to implement? I've seen many
HTML documents in German, Spanish and French, which ASCII does not
support. Even British English is left out since ASCII does not have a
British Pound sign.
I see the purpose of this first cut at text as reducing the volume of data
(and making authoring easier) for text that is in the supported encoding.
All other glyphs can still be represented as polygons. With that in mind
supporting ASCII would accomplish that but virtually all Macs, PCs and
Unix systems support at least ISO-Latin-1 and have outlines for enough
glyphs to support that encoding. I think even the latest release of the
Hershey fonts have enough symbols to accomplish ISO-Latin-1 so
implementation would not be hard.
I would not object to naming the node "LatinText" or something to be more
specific and to allow us to replace it with a real "Text" node when we
have the I18N issues sorted out.
--
chris marrin ,,.
Silicon Graphics, Inc. ,`` 1$`
(415) 390-5367 ,|` ,$`
[email protected] b` ,P` ,,.
mP b" , 1$'
,.` ,b` ,` :$$'
,|` mP ,` ,mm
,b" b" ,` ,mm m$$ ,m ,,`P$$
m$` ,b` .` ,mm ,.`'|$P ,|"1$` ,b$P ,,` :$1
b$` ,$: :,`` |$$ ,:` $$` ,|` ,$$,,`"$$ .` :$|
b$| _m$`,:` :$1 ,:` ,$Pm|` ` :$$,..;"' |$:
P$b, _;b$$b$1" |$$ ,,`` ,$$" ``' $$
```"```'" b$P `""` ""` ,P`
`"` '$$b,,...-'
"As a general rule, don't solve puzzles that open portals to Hell."
- excerpt from "A Horror Movie Character's Survival Guide"