Re: SPEC - Text (I18N)

Jan Hardenbergh ([email protected])
Thu, 20 Apr 95 16:41:00 E

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrew C. Esh: "Re: VRML usage"
Previous message: Mark Waks: "Re: VRML 2.0 and Behaviours"
Maybe in reply to: Jan Hardenbergh: "SPEC - Text (I18N)"
Next in thread: Chris Marrin: "Re: SPEC - Text (I18N)"

> > If we wanted to do something, I would argue for specifying the
> > coded character set to be ASCII instead of ISO-Latin-1, since ASCII
> > is a subset of most other character sets (including ISO-Latin-1 and
> > ISO 10646). This should be an attribute of the text.
>
> Is your concern that ISO-Latin-1 is too hard to implement?

No, it is that ISO-Latin-1 conflicts with other encoding schemes. ASCII is
a subset of most encoding schemes.

> 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.

If we stick to ASCII text, then it is upwardly compatable with ISO-Latin-1,
ISO-10646, and I believe ISO2022 & EUC. Do we really gain that much by
choosing ISO-Latin-1 (8859/1) over 8859/2... ?

-Jan

Next message: Andrew C. Esh: "Re: VRML usage"
Previous message: Mark Waks: "Re: VRML 2.0 and Behaviours"
Maybe in reply to: Jan Hardenbergh: "SPEC - Text (I18N)"
Next in thread: Chris Marrin: "Re: SPEC - Text (I18N)"