Bug 247 - Keysyms with unclear meaning and origin
Summary: Keysyms with unclear meaning and origin
Status: RESOLVED WONTFIX
Alias: None
Product: XStandards
Classification: Unclassified
Component: KeySyms (show other bugs)
Version: X11R6.6
Hardware: All All
: high normal
Assignee: Paul Anderson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 246
  Show dependency treegraph
 
Reported: 2004-03-01 12:57 UTC by Markus Kuhn
Modified: 2004-09-21 13:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Markus Kuhn 2004-03-01 12:57:52 UTC
Most of the keysyms for which I failed to identify an obvious and plausible
mapping to Unicode when I prepared

  http://www.cl.cam.ac.uk/~mgk25/ucs/keysym2ucs.c

seem to come from the byte-3 = 10 "Publishing" area. I was able to identify most
other characters by cross-referencing the value of byte-4 with the code
positions in various ancient DEC fonts or character sets, but I failed in a
quite thorough search to find a code chart, font, or description for the
original 8-bit "Publishing" character set that led to this area. Any ideas and
references welcome!

Otherwise, if nobody can find the original documentation of what a
"signifblank", "signaturemark", or "decimalpoint" is good for, or who might ever
have used the "Publishing" character set, I suggest that we simply retire such
keysyms and give those that we can made sense of a Unicode-based value.
Comment 1 Markus Kuhn 2004-09-22 06:15:51 UTC
After my correspondence with the former DEC corporate standards maintainer, Eric
Williams (now @hp.com), it has become clear that the late 1980s version of the
standard DEC STD 169 that might have defined the DEC Publishing character set
has probably been lost forever and is definitely no longer of any practical
concern. Neither can any DEC user I contacted find corresponding DECWrite fonts.
So I'm giving up on this little computer-archeology project. We should declare
any KEYSYM in the Publishing set that has no obvious clear name relationship to
a Unicode character to be deprecated, and reflect this in future updates to the
KEYSYM spec.


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.