Thread: [Audacity-translation] Removed key combinations from translatable strings
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: <ga...@au...> - 2009-06-01 18:08:15
|
Hi everyone In the past our source code displayed menu items with the menu name followed by its shortcut in one string, for example: _("Zoom &In\tUp") In the past this has caused problems because if translators translate the shortcut as well as the menu item, the shortcut will not work in the translated language. So we've now split the menu name and the shortcut into two strings and made the shortcut string untranslatable. It appears like this in the code: _("Zoom &In"), wxT("Up") So the next time you download the .po file for the software you will now only see the string for the menu item, for example "Zoom &In" and not the associated shortcut combination. Gale |
From: Christian B. <chr...@ac...> - 2009-06-03 17:57:12
|
Hello, I think it's a good thing. I did myself the error. But I think the best thing would to separate the shortcuts that are displayed in menus from the "real" shorcuts used by code. So it would be possible to translate the shortcuts without creating problems. When non english speaking people see *Shift *they can't know witch key they have to hint. I can't find a real example because I translated all new strings. But this could give something like that : *Original* _("Zoom &In"), wxT("Up") *Translated* _("Zoom &avant \tFlèche haut"), wxT("Up") so french (and other foreigners) people could understand what to do. Christian Brochec French translator ga...@au... a écrit : > Hi everyone > > In the past our source code displayed menu items with the menu > name followed by its shortcut in one string, for example: > > _("Zoom &In\tUp") > > In the past this has caused problems because if translators > translate the shortcut as well as the menu item, the shortcut > will not work in the translated language. > > So we've now split the menu name and the shortcut into > two strings and made the shortcut string untranslatable. It > appears like this in the code: > > _("Zoom &In"), wxT("Up") > > So the next time you download the .po file for the software you > will now only see the string for the menu item, for example > "Zoom &In" and not the associated shortcut combination. > > > > Gale > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Audacity-translation mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > |
From: Cleber T. <cle...@gm...> - 2009-06-04 00:03:55
|
Hi Christian, Now you got me curious... Are the keys "shift", "Caps Lock", "tab", etc... translated in a french keyboard? Because the standard brazilian keyboard have this keys untranslated. Even 'Enter', 'Home', 'End' are in english. (and we say it in english, as for 'enter', 'shift' and 'backspace'... do you call it differently?) Btw, I translated the shortcuts and my translated files didn't work for a while 'till they figure out what was happening... I'm really glad that they had fixed that :) C'ya! cleber 2009/6/3 Christian Brochec <chr...@ac...> > Hello, > > I think it's a good thing. I did myself the error. > But I think the best thing would to separate the shortcuts that are > displayed in menus from the "real" shorcuts used by code. > So it would be possible to translate the shortcuts without creating > problems. > When non english speaking people see *Shift *they can't know witch key > they have to hint. > I can't find a real example because I translated all new strings. > > But this could give something like that : > *Original* > _("Zoom &In"), wxT("Up") > *Translated* > _("Zoom &avant \tFlèche haut"), wxT("Up") > so french (and other foreigners) people could understand what to do. > > Christian Brochec > French translator > > ga...@au... a écrit : > > Hi everyone > > In the past our source code displayed menu items with the menu > name followed by its shortcut in one string, for example: > > _("Zoom &In\tUp") > > In the past this has caused problems because if translators > translate the shortcut as well as the menu item, the shortcut > will not work in the translated language. > > So we've now split the menu name and the shortcut into > two strings and made the shortcut string untranslatable. It > appears like this in the code: > > _("Zoom &In"), wxT("Up") > > So the next time you download the .po file for the software you > will now only see the string for the menu item, for example > "Zoom &In" and not the associated shortcut combination. > > > > Gale > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Audacity-translation mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Audacity-translation mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > |
From: <hum...@fr...> - 2009-06-04 10:21:30
|
> Hi Christian, > > Now you got me curious... Are the keys "shift", "Caps Lock", "tab", etc... translated in a french keyboard? Because the standard brazilian keyboard have this keys untranslated. > Even 'Enter', 'Home', 'End' are in english. > > (and we say it in english, as for 'enter', 'shift' and 'backspace'... do you call it differently?) > > Btw, I translated the shortcuts and my translated files didn't work for a while 'till they figure out what was happening... I'm really glad that they had fixed that :) Hi ! Yes, on my keyboard, for exemple : Caps lock --> Verr. Maj Shift ------> Maj Tab --------> Tab Home -------> Orig ... ... Bye ! Olivier |
From: Gale A. <ga...@au...> - 2009-06-04 18:43:19
|
| From Christian Brochec <chr...@ac...> | Wed, 03 Jun 2009 19:57:09 +0200 | Subject: [Audacity-translation] Removed key combinations from translatable strings > I think it's a good thing. I did myself the error. > But I think the best thing would to separate the shortcuts that are > displayed in menus from the "real" shorcuts used by code. > So it would be possible to translate the shortcuts without creating > problems. > > When non english speaking people see *Shift *they can't know witch key > they have to hint. > > I can't find a real example because I translated all new strings. > > But this could give something like that : > *Original* > _("Zoom &In"), wxT("Up") > > *Translated* > _("Zoom &avant \tFlèche haut"), wxT("Up") > so french (and other foreigners) people could understand what to do. Hi Christian Well I think this depends if we can actually make "dummy" strings for shortcuts that are visible in the menus, but are not the ones that activate in the code. I'm Cc'ing to Leland. Also I looked on the internet for "French keyboards" and found a number with AZERTY layout but some still had Home, End, Tab and so on in English. So I'm a little wary of translating the shortcuts (even if it were possible) without also giving the English equivalent. Gale > ga...@au... a écrit : > > Hi everyone > > > > In the past our source code displayed menu items with the menu > > name followed by its shortcut in one string, for example: > > > > _("Zoom &In\tUp") > > > > In the past this has caused problems because if translators > > translate the shortcut as well as the menu item, the shortcut > > will not work in the translated language. > > > > So we've now split the menu name and the shortcut into > > two strings and made the shortcut string untranslatable. It > > appears like this in the code: > > > > _("Zoom &In"), wxT("Up") > > > > So the next time you download the .po file for the software you > > will now only see the string for the menu item, for example > > "Zoom &In" and not the associated shortcut combination. > > > > > > > > Gale > > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > > _______________________________________________ > > Audacity-translation mailing list > > Aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > > > |
From: Christian B. <chr...@ac...> - 2009-06-04 21:01:22
|
Hello, We - french people - are very proud of our french language ;) So - even on a keyboard - all is in french. Of course, some hardware don't translate keys in order to re-use english keys. But most of keyboards are all in french. And iconic keys are known with french name (upper arrow = flèche en haut). So new menus with english shortcuts can't be understood by "standard" french people. That's why I tried top translate them (that was a wrong Idea). I don't know if it's the same thing with "major" languages (spanish, german, italian ....) but it's a real problem for Audacity's french users. Christian Brochec Audacity's french translator Gale Andrews a écrit : > | From Christian Brochec <chr...@ac...> > | Wed, 03 Jun 2009 19:57:09 +0200 > | Subject: [Audacity-translation] Removed key combinations from translatable strings > >> I think it's a good thing. I did myself the error. >> But I think the best thing would to separate the shortcuts that are >> displayed in menus from the "real" shorcuts used by code. >> So it would be possible to translate the shortcuts without creating >> problems. >> >> When non english speaking people see *Shift *they can't know witch key >> they have to hint. >> >> I can't find a real example because I translated all new strings. >> >> But this could give something like that : >> *Original* >> _("Zoom &In"), wxT("Up") >> >> *Translated* >> _("Zoom &avant \tFlèche haut"), wxT("Up") >> so french (and other foreigners) people could understand what to do. >> > > Hi Christian > > Well I think this depends if we can actually make "dummy" strings for > shortcuts that are visible in the menus, but are not the ones that > activate in the code. I'm Cc'ing to Leland. > > Also I looked on the internet for "French keyboards" and found a > number with AZERTY layout but some still had Home, End, Tab > and so on in English. So I'm a little wary of translating the shortcuts > (even if it were possible) without also giving the English equivalent. > > > Gale > > > > > > >> ga...@au... a écrit : >> >>> Hi everyone >>> >>> In the past our source code displayed menu items with the menu >>> name followed by its shortcut in one string, for example: >>> >>> _("Zoom &In\tUp") >>> >>> In the past this has caused problems because if translators >>> translate the shortcut as well as the menu item, the shortcut >>> will not work in the translated language. >>> >>> So we've now split the menu name and the shortcut into >>> two strings and made the shortcut string untranslatable. It >>> appears like this in the code: >>> >>> _("Zoom &In"), wxT("Up") >>> >>> So the next time you download the .po file for the software you >>> will now only see the string for the menu item, for example >>> "Zoom &In" and not the associated shortcut combination. >>> >>> >>> >>> Gale >>> >>> >>> ------------------------------------------------------------------------------ >>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >>> is a gathering of tech-side developers & brand creativity professionals. Meet >>> the minds behind Google Creative Lab, Visual Complexity, Processing, & >>> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian >>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >>> _______________________________________________ >>> Audacity-translation mailing list >>> Aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-translation >>> >>> >>> > > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Audacity-translation mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > |
From: Leland <le...@au...> - 2009-06-04 21:36:08
|
Don't give up hope just yet. :-) I'll install the French version of Windows 7 to see if I can figure out a way to have the menu shortcuts appear in the proper language, but still work as desired. Leland On Thu, Jun 4, 2009 at 4:01 PM, Christian Brochec < chr...@ac...> wrote: > Hello, > > We - french people - are very proud of our french language ;) > So - even on a keyboard - all is in french. Of course, some hardware don't > translate keys in order to re-use english keys. But most of keyboards are > all in french. And iconic keys are known with french name (upper arrow = > flèche en haut). > So new menus with english shortcuts can't be understood by "standard" > french people. > That's why I tried top translate them (that was a wrong Idea). > > I don't know if it's the same thing with "major" languages (spanish, > german, italian ....) but it's a real problem for Audacity's french users. > > Christian Brochec > > Audacity's french translator > > > Gale Andrews a écrit : > > | From Christian Brochec <chr...@ac...> <chr...@ac...> > | Wed, 03 Jun 2009 19:57:09 +0200 > | Subject: [Audacity-translation] Removed key combinations from translatable strings > > > I think it's a good thing. I did myself the error. > But I think the best thing would to separate the shortcuts that are > displayed in menus from the "real" shorcuts used by code. > So it would be possible to translate the shortcuts without creating > problems. > > When non english speaking people see *Shift *they can't know witch key > they have to hint. > > I can't find a real example because I translated all new strings. > > But this could give something like that : > *Original* > _("Zoom &In"), wxT("Up") > > *Translated* > _("Zoom &avant \tFlèche haut"), wxT("Up") > so french (and other foreigners) people could understand what to do. > > > Hi Christian > > Well I think this depends if we can actually make "dummy" strings for > shortcuts that are visible in the menus, but are not the ones that > activate in the code. I'm Cc'ing to Leland. > > Also I looked on the internet for "French keyboards" and found a > number with AZERTY layout but some still had Home, End, Tab > and so on in English. So I'm a little wary of translating the shortcuts > (even if it were possible) without also giving the English equivalent. > > > Gale > > > > > > > > ga...@au... a écrit : > > > Hi everyone > > In the past our source code displayed menu items with the menu > name followed by its shortcut in one string, for example: > > _("Zoom &In\tUp") > > In the past this has caused problems because if translators > translate the shortcut as well as the menu item, the shortcut > will not work in the translated language. > > So we've now split the menu name and the shortcut into > two strings and made the shortcut string untranslatable. It > appears like this in the code: > > _("Zoom &In"), wxT("Up") > > So the next time you download the .po file for the software you > will now only see the string for the menu item, for example > "Zoom &In" and not the associated shortcut combination. > > > > Gale > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Audacity-translation mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Audacity-translation mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Audacity-translation mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > |
From: Leland <le...@au...> - 2009-06-05 04:37:38
|
Christian, Were you ever been able to use "HAUT" for "UP" or "DEBUT" for "HOME" or anything other than the English version of the names? Is this something that has worked in the past and doesn't anymore? After looking around further, I believe we are artificially limiting the keyboard names to English only. The reason I say this is because the wxWidgets library has its own .po files which include translations for many of the key names like HOME, INSERT, PAGEDOWN, etc. So, if we were to distribute the wxWidgets .mo file along with ours and make some changes to Audacity itself, you should be able to use something like "PAGEPRECEDENTE" for "PAGEUP" or "GAUCHE" for "LEFT". You would be limited to whatever the wxWidgets French translation used for the key names, but it would be better than the English version. And, this would also work for all of the other languanges. Well, at least for the ones that have both a wxWidgets translation and an Audacity one. Leland Christian Brochec wrote: > Hello, > > We - french people - are very proud of our french language ;) > So - even on a keyboard - all is in french. Of course, some hardware > don't translate keys in order to re-use english keys. But most of > keyboards are all in french. And iconic keys are known with french name > (upper arrow = flèche en haut). > So new menus with english shortcuts can't be understood by "standard" > french people. > That's why I tried top translate them (that was a wrong Idea). > > I don't know if it's the same thing with "major" languages (spanish, > german, italian ....) but it's a real problem for Audacity's french users. > > Christian Brochec > > Audacity's french translator > > > Gale Andrews a écrit : >> | From Christian Brochec <chr...@ac...> >> | Wed, 03 Jun 2009 19:57:09 +0200 >> | Subject: [Audacity-translation] Removed key combinations from translatable strings >> >>> I think it's a good thing. I did myself the error. >>> But I think the best thing would to separate the shortcuts that are >>> displayed in menus from the "real" shorcuts used by code. >>> So it would be possible to translate the shortcuts without creating >>> problems. >>> >>> When non english speaking people see *Shift *they can't know witch key >>> they have to hint. >>> >>> I can't find a real example because I translated all new strings. >>> >>> But this could give something like that : >>> *Original* >>> _("Zoom &In"), wxT("Up") >>> >>> *Translated* >>> _("Zoom &avant \tFlèche haut"), wxT("Up") >>> so french (and other foreigners) people could understand what to do. >>> >> >> Hi Christian >> >> Well I think this depends if we can actually make "dummy" strings for >> shortcuts that are visible in the menus, but are not the ones that >> activate in the code. I'm Cc'ing to Leland. >> >> Also I looked on the internet for "French keyboards" and found a >> number with AZERTY layout but some still had Home, End, Tab >> and so on in English. So I'm a little wary of translating the shortcuts >> (even if it were possible) without also giving the English equivalent. >> >> >> Gale >> >> >> >> >> >> >>> ga...@au... a écrit : >>> >>>> Hi everyone >>>> >>>> In the past our source code displayed menu items with the menu >>>> name followed by its shortcut in one string, for example: >>>> >>>> _("Zoom &In\tUp") >>>> >>>> In the past this has caused problems because if translators >>>> translate the shortcut as well as the menu item, the shortcut >>>> will not work in the translated language. >>>> >>>> So we've now split the menu name and the shortcut into >>>> two strings and made the shortcut string untranslatable. It >>>> appears like this in the code: >>>> >>>> _("Zoom &In"), wxT("Up") >>>> >>>> So the next time you download the .po file for the software you >>>> will now only see the string for the menu item, for example >>>> "Zoom &In" and not the associated shortcut combination. >>>> >>>> >>>> >>>> Gale >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >>>> is a gathering of tech-side developers & brand creativity professionals. Meet >>>> the minds behind Google Creative Lab, Visual Complexity, Processing, & >>>> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian >>>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >>>> _______________________________________________ >>>> Audacity-translation mailing list >>>> Aud...@li... >>>> https://lists.sourceforge.net/lists/listinfo/audacity-translation >>>> >>>> >>>> >> >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Audacity-translation mailing list >> Aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-translation >> >> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > > > ------------------------------------------------------------------------ > > _______________________________________________ > Audacity-translation mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-translation |
From: Leland <le...@au...> - 2009-06-05 06:58:52
|
Leland wrote: > Christian, > > Were you ever been able to use "HAUT" for "UP" or "DEBUT" for "HOME" or > anything other than the English version of the names? Is this something > that has worked in the past and doesn't anymore? Looking at some of the older betas and 1.2.x, I suspect your answer is going to be, "Yes, this has worked in the past." Leland |