I think we can do something that will work by sidestepping the character set
switching mechanism. Each "string" must be in a single character set. We
could reuse PEX terminology and refer to these as "mono-encdoded" strings.
A "character set" is a set of relations between "code points" (integer
indices) and
generic notions of glyphs. For example, 0x41 is an "A" in ASCII (& 8859/1 or
ISO
Latin-1). The character set has nothing to do with what type face
(appearance -
Helvetica, Old English, etc) the "A" is.
A "font" is a set of specific glyphs which can be indexed.
I think a minimalist approach would be to add a character set tag to the
SoText3,
and be able to identify Fonts and give them character sets, too. And, add
the
ability to have String16 character strings in SoText3.
This approach gets the gritty details out of the VRML spec. But, it puts the
responsibility into the browsers.
Can anyone summarize what is going on with I18n in the HTML world? I saw
a link to some info the other day, but did not follow it.
> 2. Should we accept the FontStyle node?
Yes.
YON, [email protected], Jan C. Hardenbergh, Oki Advanced Products 508-460-8655
http://www.oki.com/people/jch/ =|= 100 Nickerson Rd. Marlborough, MA 01776
Imagination is more important than knowledge - Albert Einstein (1879-1955)