Bug 9480 - typographic apostrophe (U+2019) on latin keyboard
Summary: typographic apostrophe (U+2019) on latin keyboard
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-29 12:49 UTC by Helge Hielscher
Modified: 2007-01-02 17:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Helge Hielscher 2006-12-29 12:49:37 UTC
There should be a typographic apostrophe on latin keyboard layouts.

http://en.wikipedia.org/wiki/Apostrophe#Computers_and_Unicode states:
“In most cases, the preferred apostrophe character is the punctuation apostrophe
(distinguished as typographic, or curly apostrophe).”

On the German keyboard layout both apostrophe (next to ä) and
<Shift>+<ISO_Level3_Shift>+<b> give U+0027.
Maybe one of it could be changed to U+2019?
Comment 1 Sergey V. Udaltsov 2006-12-29 13:05:27 UTC
I dont mind. Which of them would you like to change? What do Windows users have
on these keys?
Comment 2 Helge Hielscher 2006-12-29 13:24:39 UTC
In the German layout I would like to have <Shift>+<ISO_Level3_Shift>+<b> changed
to give U+0027, because the standard apostrophe U+0027 is already provided.

AFAIK Windows does not provide enhanced keyboard functionality, only alt codes
(alt+0146) work. On the Mac the typographic apostrophe is option-shift-right
bracket (english layout?).
Comment 3 Sergey V. Udaltsov 2007-01-02 01:36:05 UTC
Ok, several additional questions:
1. I would not like the idea to change "latin" layout, since it would affect too
many layouts. So which particular layouts/variants would you like to modify?
2. I understand your idea in terms of unicode. But let's go back to the terms of
keysymdef.h. Is XK_rightsinglequotemark what you mean?
Comment 4 Sergey V. Udaltsov 2007-01-02 01:50:01 UTC
Sorry, I did not look at the existing symbols/latin file in xkeyboard-config:
AC11 gives "apostrophe" which is U+0027, AB05 gives rightdoublequotemark
(U+201D) and rightsinglequotemark (U+2019) on levels 3 and 4 respectively. So I
presume this bug is already fixed. Could you please check the latest
xkeyboard-config?
Comment 5 Helge Hielscher 2007-01-02 09:30:06 UTC
(In reply to comment #4)
> 2. I understand your idea in terms of unicode. But let's go back to the
> terms of keysymdef.h. Is XK_rightsinglequotemark what you mean?

Sorry, but of us you are the only one who understands both the standard unicode
and X-specific slang.
With keysymdef.h you mean
http://cvsweb.xfree86.org/cvsweb/xc/include/keysymdef.h ,right? 
Where can I find the latest version of keysymdef.h in
http://gitweb.freedesktop.org ?

How can I check if XK_rightsinglequotemark and U+2019 RIGHT SINGLE QUOTATION
MARK are the same?

(In reply to comment #4)
> Sorry, I did not look at the existing symbols/latin file in xkeyboard-config:
> AC11 gives "apostrophe" which is U+0027, AB05 gives rightdoublequotemark
> (U+201D) and rightsinglequotemark (U+2019) on levels 3 and 4 respectively.
> So I
> presume this bug is already fixed. Could you please check the latest
> xkeyboard-config?

Could you please translate? AC11 is the 11th key in the 3rd row counting from
the bottom, right? 
On German keyboard there I have ä, Ä, dead_circumflex, dead_caron.

I am going to retest as soon as my distribution Mandriva Cooker changes to
x.org 7.2.
Comment 6 Sergey V. Udaltsov 2007-01-02 09:45:53 UTC
> Sorry, but of us you are the only one who understands both the standard unicode
> and X-specific slang.
Well, it is easy to explain - X is using its own 2-byte encoding which is not
compatible with unicode. That encoding is documented in keysymdef.h. And it is
recommended to use that encoding in the XKB configuration files (well, stripping
the "XK_" prefix). When it is not possible, we fallback to unicode (for some
Asian characters) but it seems for the current bug it is not the case.

> With keysymdef.h you mean
> http://cvsweb.xfree86.org/cvsweb/xc/include/keysymdef.h ,right? 
Yes.
> Where can I find the latest version of keysymdef.h in
> http://gitweb.freedesktop.org ?
Ghm.. Gitweb has rather strange interface, so I am not sure I could be any help
with it. The latest xorg CVS version was here:
http://webcvs.freedesktop.org/xorg/proto/X11/keysymdef.h?revision=1.10&view=markup

> How can I check if XK_rightsinglequotemark and U+2019 RIGHT SINGLE QUOTATION
> MARK are the same?
Well, at least that what keysymdef promises:) The actual translation of "X
encoding" to the characters depends on the current locale. So in unicode locales
XK_rightsinglequotemark should generate U+2019 character. But in non-unicode
locales it can be something different.

> Could you please translate? AC11 is the 11th key in the 3rd row counting from
> the bottom, right? 
> On German keyboard there I have ä, Ä, dead_circumflex, dead_caron.
> I am going to retest as soon as my distribution Mandriva Cooker changes to
> x.org 7.2.
If you are using xkbdata package from xorg - you can have anything:). Because it
is not supported. But if you are using xkeyboard-config package (recommended by
xorg), you should have something like in symbols/de:
http://webcvs.freedesktop.org/xkeyboard-config/xkeyboard-config/symbols/de?revision=1.15&view=markup
Comment 7 James Cloos 2007-01-02 17:57:24 UTC
You can view the current version of keysymdef.h at:

http://gitweb.freedesktop.org/?p=xorg/proto/x11proto.git;a=blob;f=keysymdef.h

and download the raw file via:

http://gitweb.freedesktop.org/?p=xorg/proto/x11proto.git;a=blob_plain;f=keysymdef.h

(NB that the latter is being sent as text/x-chdr, and some browsers — including
seamonkey, I find — will refuse to display it, and force a download instead....)


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.