[Xcb] [PATCH:xwininfo 0/2] Handle UTF8 window names & EMWH hints

Alan Coopersmith alan.coopersmith at oracle.com
Wed Jun 30 10:02:42 PDT 2010

James Cloos wrote:
> In short, there unfortunately remain modern, usable and useful apps
> which continue to use WM_NAME() rather than _NET_WM_NAME().  We
> probably, therfore, need to support COMPOUND_TEXT for a bit longer.

Unfortunately, I couldn't find any existing XCB API for COMPOUND_TEXT
decoding, and reading the spec made my head spin and I had to go lay
down before I puked.

The libX11 code doesn't seem to be a simple function we can copy, but
tied into the whole Xlib i18n module system, so may not help much.

If someone has a good way to solve this problem or wants to sign up
to write an xcb-util library for COMPOUND_TEXT encoding/decoding, great,
but I don't think I'll be solving it.

If we did ship with this regression, would it actually cause critical
problems?   Hopefully nothing is trying to parse xwininfo output to get
names instead of just getting the properties themselves.

> On a related note, we should make xprop(1) report UTF8_STRING props
> using code similar to what you added here, falling back to the current
> output when conversion to the locale cannot work.

Is this sort of thing common enough to make it worthwhile to have a
xcb/util library for property encoding/decoding?   Certainly Xlib
handled this for you and hid it from applications, though it built
the huge xlibi18n infrastructure around it.

	-Alan Coopersmith-        alan.coopersmith at oracle.com
	 Oracle Solaris Platform Engineering: X Window System

More information about the Xcb mailing list