On 11/29/2017 1:09 AM, Paul Licameli wrote:
I thought it over and now it think it would be easier to maintain a small
text file of all the language self-names in legible Unicode text, then just
have the program read it at run-time, rather than maintain less readable
source code.
Then it would not be too hard to research all the correct names and cut and
paste them.
Not a large project, but not small enough for this limitied release.
PRL
A detail...
Slightly better might be if Audacity.pot contained the English names of
the languages.
German, French, Dutch .... etc.
Translators would then translate these.
We would also add the few miscellaneous strings that come from the
'desktop' file and the Audacity setup program that we currently put in
the right place by hand. Then we would run a script to automatically
create a suitable source code file, just as we already run a script to
create the 'git identity' source code file (that is a file the lets
users know exactly what version of the source code was used).
There are two advantages of this:
1) Translators are each maintaining a single .po file.
2) Audacity does not have to load an extra file at run time.
Anyway I agree with Paul, NOT for 2.2.1.
--James.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
