Localization of keyboard shortcuts
Hi all,
now that the keyboard shortcuts are customizable (see http://wiki.inkscape.org/wiki/index.php/Release_Notes#Configurable_keyboard ), I was wondering if some of you had already began generating some localized version of the keyboard shortcuts adapted to their local keyboard layout ?
regards,
matiphas
On 22/06/2006, at 8:58 PM, matiphas@...9... wrote:
now that the keyboard shortcuts are customizable (see http://wiki.inkscape.org/wiki/index.php/ Release_Notes#Configurable_keyboard ), I was wondering if some of you had already began generating some localized version of the keyboard shortcuts adapted to their local keyboard layout ?
When translating, we try to position keyboard accelerators to match the original, e.g.
msgid "S_hift" msgstr "Dịc_h"
or as appropriately as possible:
msgid "_Edit" msgstr "_Sửa"
Can these choices be overwritten by a custom keybindings file?
If so, it's an intriguing opportunity, because for my language, at least, positioning keyboard accelerators becomes extremely difficult, since most of the language is accented vowels, often with combined diacritics, and according to
http://bugzilla.gnome.org/show_bug.cgi?id=104112
gtk can't handle any non-ASCII keyboard shortcuts. I don't know if any other toolset handles them better.
For example:
msgid "_Edit session" msgstr "Sửa phi_ên chạy"
The e-circumflex can't be used, since it requires two keystrokes (one being a dead key). We can't use the normal "e", leaving the user to assume the normal e from the string, because gtk can't associate those two characters.
Our problem becomes acute with long menus, or very short translations like:
msgid "Hide" msgstr "Ẩn"
The only currently possible choice for a keyboard accelerator in the above string is "n", which is often already assigned in a menu.
So any extra opportunities for assigning keyboard shortcuts would be very welcome to our users. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
When translating, we try to position keyboard accelerators to match the original, e.g.
msgid "S_hift" msgstr "Dá»c_h"
or as appropriately as possible:
msgid "_Edit" msgstr "_Sá»a"
Yes accerators can be modified, but the translator must pay attention to their consistency (avoid twice the same accelerator in a menu roll, or in a dialog...)
Can these choices be overwritten by a custom keybindings file?
No it's different. * The accelerators are linked to the undercored chars, and facilitate navigations in the menus/dialogs with the keyboard). * Shortcuts are linked to the key combinations (such ast Ctrl+Alt+M....), they don't appear in the translatable strings, but are automatically inserted in the interface at run time. They are not aimed at facilitating navigation in menus, but they directly call a function/verb.
If so, it's an intriguing opportunity, because for my language, at least, positioning keyboard accelerators becomes extremely difficult, since most of the language is accented vowels, often with combined diacritics, and according to
http://bugzilla.gnome.org/show_bug.cgi?id=104112 gtk can't handle any non-ASCII keyboard shortcuts. I don't know if any other toolset handles them better.
I think the best thing to do is : - install inkscape (this should be already done) - modify the accelerators in a temporay po file - compile the po file, and replace the original message file by the result of the compilation of your temp po file in the inkscape directory tree (i think it's in the locale directory) - launch inkscape, and see how it reacts with the new accelerators and your locale keyboard.
Hope it helps you,
regards,
matiphas
Thanks for your helpful reply, matiphas :)
On 22/06/2006, at 10:26 PM, matiphas@...9... wrote:
Yes accerators can be modified, but the translator must pay attention to their consistency (avoid twice the same accelerator in a menu roll, or in a dialog...)
Yes, of course. :)
Can these choices be overwritten by a custom keybindings file?
No it's different.
- The accelerators are linked to the undercored chars, and facilitate
navigations in the menus/dialogs with the keyboard).
- Shortcuts are linked to the key combinations (such ast Ctrl+Alt
+M....), they don't appear in the translatable strings, but are automatically inserted in the interface at run time. They are not aimed at facilitating navigation in menus, but they directly call a function/verb.
So this file simply shows the keybindings indicated by the underscore- preceded character?
If so, it's an intriguing opportunity, because for my language, at least, positioning keyboard accelerators becomes extremely difficult, since most of the language is accented vowels, often with combined diacritics, and according to
http://bugzilla.gnome.org/show_bug.cgi?id=104112 gtk can't handle any non-ASCII keyboard shortcuts. I don't know if any other toolset handles them better.
I think the best thing to do is :
- install inkscape (this should be already done)
- modify the accelerators in a temporay po file
- compile the po file, and replace the original message file by the
result of the compilation of your temp po file in the inkscape directory tree (i think it's in the locale directory)
- launch inkscape, and see how it reacts with the new accelerators
and your locale keyboard.
I'll pass this on to my GNOME team leader, who is having this problem. I don't have the same keyboard layout, since I'm running Mac OSX: my layout allows single-key input for the characters:
ă â ê ô ư ơ đ
which are dead-key input on Linux layouts. So I'm not a good test subject. Until I found out about the differing layouts, I assigned keyboard shortcuts which would work with mine. Since by far the majority of free software users would run Linux, I need to work with the Linux layout(s). So my team leader and I have discussed this. He will want to test this situation.
Hope it helps you,
Thanks. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
Hi Clytie
Can these choices be overwritten by a custom keybindings file?
No it's different.
- The accelerators are linked to the undercored chars, and facilitate
navigations in the menus/dialogs with the keyboard).
- Shortcuts are linked to the key combinations (such ast Ctrl+Alt
+M....), they don't appear in the translatable strings, but are automatically inserted in the interface at run time. They are not aimed at facilitating navigation in menus, but they directly call a function/verb.
So this file simply shows the keybindings indicated by the underscore- preceded character?
Yes vi.po or fr.po (or any po file) will only show accelerators (underscore-preceded characters in interface strings).
Just an example : with the string "Fill and Stroke".
In the interface, when you open the Object menu, it is displayed as : "_Fill and stroke... Shift+Ctrl+F".
"_", the underscore is the accelerator, and is displayed in the po file. "Shift+Ctrl+F" is the shortcut and is not displayed in the po file.
- The accelerator is used for the following navigation : from the interface, "Alt+O" will open the Object menu, then "F" will launch the fill&stroke dialog.
- The shortcut aims at a more direct navigation from the interface "Shift+Ctrl+F" will directly launch the fill&stroke dialog.
If so, it's an intriguing opportunity, because for my language, at least, positioning keyboard accelerators becomes extremely difficult, since most of the language is accented vowels, often with combined diacritics, and according to
http://bugzilla.gnome.org/show_bug.cgi?id=104112 gtk can't handle any non-ASCII keyboard shortcuts. I don't know if any other toolset handles them better.
Ah this sound annoying. Will take look and try to get more info/find workarounds...
Your e-mail is very important because it shows us that internationalization of Inkscape will maybe require some more infrastructure work. (see also the following bug : http://sourceforge.net/tracker/index.php?func=detail&aid=1508404&gro... )
It's maybe time to - list all our problems with internationalization - according to those issues, open a few RFEs/Bugs against GTK or Inkscape
Thanks for your remarks Regards,
matiphas
Sorry it has taken a while to try this out.
On 22/06/2006, at 10:26 PM, matiphas@...9... wrote:
I think the best thing to do is :
- install inkscape (this should be already done)
- modify the accelerators in a temporay po file
- compile the po file, and replace the original message file by the
result of the compilation of your temp po file in the inkscape directory tree (i think it's in the locale directory)
- launch inkscape, and see how it reacts with the new accelerators
and your locale keyboard.
My Gnome team-leader tried this, changing:
_Mới
to
M_ới
(if your mailer doesn't display this correctly, the new accelerator is an o with a hook on the right hand side, and an acute accent).
but pressing an ordinary "o" did not enable the command (New).
As you know, we can't press the non-ASCII character indicated, because it requires a dead key. On Linux layouts, all our non-ASCII characters (the bulk of our language) require dead keys to input. Currently, dead-key accelerator input is not supported.
We wanted to try this out, to see if Inkscape (or more correctly, the software underpinning it) would connect a non-ASCII accelerator with the closest ASCII analogue. No luck.
But worth a try. ;)
Thanks for your help with this.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
participants (2)
-
unknown＠example.com -
Clytie Siddall