COMPOUND_TEXT versus UTF8_STRING

[Roland Mainz]

Keith Packard wrote:
> > The alterantive is to break backwards-compatibility and that will cause
> > big interoperability problems. The Linux desktop already has enougth of
> > these issues so adding another one will cause even more grief.
> 
> Ensuring backwards compatibility should remain an important goal; adopting
> separate properties for UTF-8 data preserves compatibility while not
> further gilding the COMPOUND-TEXT turd.

This will likely require at least to depreciate some libX11 API, add new
ones which accept UTF-8 and a bump of the major shared library version
number of libX11... ;-(

----

Bye,
Roland

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