Summary: | Add XK_dead_stroke to keysymdef.h | ||
---|---|---|---|
Product: | xorg | Reporter: | Egbert Eich <eich> |
Component: | Lib/Xlib | Assignee: | Daniel Stone <daniel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | simos.bugzilla |
Version: | git | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Egbert Eich
2006-05-10 19:59:46 UTC
that would be 0x1000fe63, rather than 0xfe63, but I don't see a problem with this. Is there a unicode code point for this? If so, why not just use the unicode part of the keysym space for defining this. UFE63 seems to be 'small hyphen-minus', or so gucharmap tells me. is that the intention? I picked the value as it is the value after "XK_dead_horn 0xfe62." Dead stroke doesn't really exist in the same sense as the other dead letters (which have a corresponding unicode character). The mapping to unicode characters must be done on a character by character basis. It is just convenient to have it, as otherwise we need to assign a key on the keyboard for each of the characters which have some kind of stroke in them. Bug 6901, the new Finnish keyboard map, uses this key. For now the value is used, not the word dead_stroke. See the Compose file referenced in the bug report for how dead_stroke will be used. I guess it makes sense to submit a bug report on the additions to Compose file only after dead_stroke can be used as a name... committed to xproto HEAD, released as 7.0.7 |
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.