>> Your basic ideas are OK though, even if they're not worded well. How
>> about:
>>
>> Text3
>> Fields
>> MFString text
>> MFString language
>> MFString encoding
>> MFString charset
>
>If we make VRML own the language & encoding, it will takes months just
>to specify. This implies that the browser/VRML library knows everything
>about rendering all languages, ne? Or, half seriously, we could have
>text rendering servers hanging around. The browser would get the text,
>decide if it can do it itself, if not, ship it out to a 3D text server
>with a polygon budget...
I freely admit to not knowing much about all this, but what if we create all
these fields, set defaults for the ones most designers won't use, and leave
implementation levels up to browser designers? If someone wants to design both
a browser and a series of VRML models using Mandarin, the mechanism will be
there.
--Andy
[email protected]