Re: SPEC - Text

Gavin Nicol ([email protected])
Tue, 18 Apr 1995 13:30:18 -0400

>I saved the best for last. Let's do text! Chris Marrin of SGI,
>bless his heart, came up with a great proposal for a simple text node
>based on Inventor's SoText3. I've included his message below. I
>generally like his proposal, but I have two questions which I would
>like to put to the list:

This proposal is absolutely unusable.

>1. Can we avoid I18N issues in the first version?
>How can we *not* avoid it?

The only way to avoud I18N issues is to avoid proposals that fly in
the face of any notion of internationalisation.

>2. Should we accept the FontStyle node?

This is not so bad.

>The above reservation aside, we need to do *something* with text
>styles. This proposal is simple and generic, while providing for a
>fair amount of expressiveness.

It is certainly not generic. How about:

Text3
Fields:
MFString string - array of strings to display. Each
string is a new "line."
MFString language - as according to RFC XXXX

and leave spacing and justification for the moment.