We seem to have a problem that if the actual program shortcuts in
Audacity are translated (as well as the commands themselves),
they don't work on a first run of Audacity. For example, in the
French .po file, "Home" is translated as "Début":
Retour au début\tDébut
The shortcut then appears on first run as "Début" in the Transport
Menu (in CVS builds) and in the keyboard preferences, but pressing
the Home key won't work. To make it work, you have to go to
Preferences, change language to English, then set the keyboard bindings
to "Defaults", then finally change language back to French. Note the
effect of these changes is that "Home" is now untranslated in the menu
and key bindings.
So in a nutshell, can we fix this so that shortcuts can be (and remain)
translated, or should we request our translators not to translate
shortcuts? If we can't fix it, then I have already removed the translated
shortcuts from pt_BR.po, so should I commit that?
Get latest updates about Open Source Projects, Conferences and News.