Bug 271 - UTF8_STRING additions to ICCCM 2.0 spec
Summary: UTF8_STRING additions to ICCCM 2.0 spec
Status: RESOLVED MOVED
Alias: None
Product: XStandards
Classification: Unclassified
Component: ICCCM (show other bugs)
Version: X11R6.6
Hardware: All All
: high normal
Assignee: Paul Anderson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-04 10:19 UTC by Alan Coopersmith
Modified: 2019-02-21 10:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Diffs showing changes made by XFree86 (2.37 KB, patch)
2004-03-04 10:19 UTC, Alan Coopersmith
Details | Splinter Review

Description Alan Coopersmith 2004-03-04 10:19:06 UTC
XFree86 has added a UTF8_STRING type to the ICCCM spec and converted the 
spec's reference to specific byte value from octal to hex.
Comment 1 Alan Coopersmith 2004-03-04 10:19:42 UTC
Created attachment 122 [details] [review]
Diffs showing changes made by XFree86
Comment 2 Markus Kuhn 2004-09-22 06:22:23 UTC
This is a very minimalistic change, and perhaps some more guidance needs to be
provided in the ICCC document on how to use UTF8_STRING in clients and window
managers, with a minimum impact on backwards compatibility. What about all the
many properties, for which UTF8_STRING is not yet defined as one of the
available options? What about selections?

See

  http://www.pps.jussieu.fr/~jch/software/UTF8_STRING/

for some more discussion on the issue.
Comment 4 Tollef Fog Heen 2010-02-09 13:45:42 UTC
Adding missing QA contact
Comment 5 GitLab Migration User 2019-02-21 10:28:34 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/doc/xorg-docs/issues/5.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.