неділя, 24 березня 2019 р. 16:11:23 EET scootergrisen написано: > Den 24-03-2019 kl. 13:57 skrev James Crook: > > Hi Scooter, and thank you for your Danish translations. > > > > This is a good idea. However, it does need some developer to > > write/modify a script if it is to happen. > > This is where open source projects often say "Patches Welcome!". (i.e. > > no one is writing such a script, > > but we will review one if one is offered). We're short of developers. > > > > Realistically I don't think it will get looked at by a developer any > > time soon. The most likely way > > anything will happen is if a developer is persuaded to work specifically > > on translation for a while, > > e.g. clearing some of the translation bug list > > https://bugzilla.audacityteam.org/buglist.cgi?action=wrap&bug_severity=Loc > > ale&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=inclu > > de&list_id=16949 > > > > Then they might also look at making the translation cover this too. > > > > --James. > > > > On 24/03/2019 11:21, scootergrisen wrote: > >> If i compare the *.po files on > >> https://github.com/audacity/audacity/tree/master/locale with the lines > >> in > >> https://github.com/audacity/audacity/blob/master/src/audacity.desktop.in > >> the following languages are missing translations i the .desktop file: > >> > >> af > >> be > >> bg > >> bn > >> bs > >> ca_ES@valencia > >> cs > >> cy > >> es > >> eu > >> eu_ES > >> fa > >> fi > >> ga > >> gl > >> he > >> hr > >> hu > >> hy > >> id > >> it > >> ka > >> km > >> ko > >> mk > >> my > >> nb > >> oc > >> pl > >> ro > >> sk > >> sl > >> sr_RS > >> sr_RS@latin > >> sv > >> ta > >> tg > >> vi > >> > >> Some time ago i suggested to add the .desktop strings to the .po files > >> so translators can easily translate them and not miss them because > >> they are no aware of them. > >> > >> Surely the languages with fully translated .po files would have also > >> translate the strings for the .desktop file if only they where aware > >> of them. > >> > >> I still think it would be a good idea and logical to have the strings > >> with the other strings in the po files. > > Ok i dont know how to make such a script. > I think some software use gettext to get the strings and some use > intltool/itstool/internatilsation tool or what ever its called and they > put a "_" in front of the lines that needs translation. But dont know > the details. I guess we can look at how other software does it. > > Does Audacity use gettext? > > From a users point of view i think the strings are important/high > prioritet because it might be the first thing the users sees if Audacity > is preinstalled and they look for it in the menu.
Hi, This does not need intltool/itstool/internatilsation tool, just a pure gettext. Extraction: xgettext src/audacity.desktop.in -k -kName -kComment -kGenericName -o locale/ desktop.pot Merge with the main file: msgcat locale/*.pot > locale/audacity.pot Cleanup: rm locale/desktop.pot Merging back the translations: msgfmt --desktop --template=src/audacity.desktop.in -d locale -o src/ audacity.desktop But before patching the build system... Will such a patch be considered at all? Thanks in advance for your answers. Best regards, Yuri _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
