[Xcb] about XTextProperty

Jamey Sharp jamey at minilop.net
Sun May 15 13:25:46 PDT 2005

On Sat, 2005-05-14 at 21:23 -0700, Keith Packard wrote:
> This is, sadly, not quite true.  X uses a custom encoding called
> COMPOUND_TEXT which is based on ISO 2022 to merge multiple other
> encodings together in the same property.

Ooh, right, I forgot.

> These legacy encodings are not necessary to interoperate with Mozilla,
> Qt or Gtk+ based applications; those all happily use the new UTF-8
> property encodings.  So, if you're cavalier about legacy non-US
> application support, you could bail on COMPOUND_TEXT and stick with ISO
> 8859-1 and ISO 10646.

Maybe ecore can get away with that, I don't know. Vincent can surely
ignore COMPOUND_TEXT for a first cut at his port, anyway.


More information about the xcb mailing list