Automatically generated by Pod::Man 4.07 (Pod::Simple 3.32) Standard preamble: ========================================================================
NAMEEncode::X11 -- character encodings for X11
use Encode; use Encode::X11; my $chars = Encode::decode ('x11-compound-text', $bytes);
DESCRIPTIONThis module encodes and decodes X11
Compound text is found in window properties of type "COMPOUND_TEXT". It's not usual to use it outside that context. Compound text consists of
The plain name ``x11-compound-text'' tries to encode in a sensible and compatible way. Perhaps in the future there'll be some options or variations for which charsets to use. For now encoding prefers the original
The decode is meant to recognise anything, but may be a bit limited yet. Perhaps it could be just a full
Decoding cns11643 segments requires the "Encode::HanExtra" module. Such segments are not normally generated by the Xlib conversions (as of X.org libX11 1.4.0). Have HanExtra available if you think you might encounter them.
Emacs has some ``private encoding'' sequences for big5. They're not supported currently.
When working with compound text you might in fact not want to convert it to Perl wide chars. If drawing with the core X requests then split it into segments of the various charsets and find a font for each encoding. Some oopery could no doubt represent such a breakdown and have things like concatenate or compare. That would work almost directly with the bytes without converting.
SEE ALSOEncode, Encode::HanExtra
``Compound Text Encoding'' specification, ``usr/share/doc/xorg-docs/specs/CTEXT/ctext.txt.gz'', <www.x.org/docs/CTEXT/ctext.pdf>
LICENSECopyright 2011, 2012, 2013 Kevin Ryde
X11-Protocol-Other is free software; you can redistribute it and/or modify it under the terms of the
X11-Protocol-Other is distributed in the hope that it will be useful, but
You should have received a copy of the