COMPOUND_TEXT versus UTF8_STRING

[Roland Mainz]

Keith Packard wrote:
> 
> Around 18 o'clock on Sep 22, Roland Mainz wrote:
> 
> > It is not easy to get rid of COMPOUND_TEXT since many X11 specs have to
> > be rewritten/updated to do that. And backwards-compatibility to existing
> > (binary) applications is required, too.
> 
> We don't have to eliminate it, but we should make sure the standards all
> have some way of using UTF8 instead and mark the COMPOUND_TEXT (and STRING)
> support as 'obsolete' so that application developers are encouraged to use
> the more modern methods.
> 
> Adopting the EWMH as an X.org standard might be a good place to start.

... or "enhanche" the ISO2022/COMPUND_TEXT spec (see my other email in
this thread) to include an escape-sequence which says: "UTF-8 starts
here..." :)
That may be a less aggressive approach to the problem...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)