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