> So, where does the *display* of a String come in?
> > It is one thing to suggest that a String is only an arbitrary list of
> characters, and another to suggest that ASCII-text handlers > are all that
> are needed to handle Unicode text-needs. 

This is a straw man.  Noone has made that statement.  At most, it was suggested that the two functionalities be decoupled to permit reasonable implementations of the former, while maintaining the ability to build the latter thereupon.

>At the least, one > needs to keep
> track of groupings of characters in different languages and > accomidate the
> cases of various languages.
> > How does one store a string of Hebrew text and numbers in a single
> string-object?

Either way, depending upon the kind of operations you are performing on the data.  The example of

		MLCh 123
or

		MLCh 321

or even

		123 MLCh

all make sense -- but that is an implementation concern.  As conceived, a GeneralString class should support all of these representations just fine.  The string can present itself to the programmer interface logically as a sequence of characters, however the application finds it most useful to perform operations thereupon.


> Is it all one string or is it a collect of strings or what?

One string.  What's the problem?