> 1. When a translation has been updated, put it on the web so that peop=
> can download it, along with instructions (in that language) for how to=
> install it.
Could work, but 90% of the users won=B4t be able to understand those=20
instructions and we could end with a lot of users in our Fora (or foruns?=
asking for help, which wuould increase our job in lieu of minimizing it..=
> 2. Release new "language packs" regularly - every month, for example.=20
> The language pack would include a Windows installer that replaces your=
> current translations in an existing Audacity install...
> 3. Have Audacity download the latest translations from the Internet.=20
> Would most users like this, or would it be a pain for most?
I vote for the internet engine. As long as it remains well explained -=20
*really* well, users won't refuse the editor to connect to the internet a=
update installed translations. It would be great if we have an option to=20
disable this function, and would be best if, instead of downloading a ful=
new language file by itself, the engine opens a window saying "there's a =
translation", and the option to the user to download or just ignore it.
> 4. Independent of the other choices, what would people think about=20
> separating the languages by geography?
That's great too. But it would increase our load of work, since we will h=
about 6 "audacitys" to work with.
What about something like that:
You download the program in english only. Than, when you install it in yo=
system, the installer asks you about what language (or languages) would y=
want to use the editor.
After the installation is done, the installer says it will download the=20
selected languages updated from the internet.
That way, the installation file is reduced and we ensure that the users w=
aways have the latest language version.
> 6. How many of you would be willing to help commit new translations to=
> CVS (requires learning CVS and the details of CVS on SourceForge)?
I've tried! And tried again real hard. And again harder. And I *never* co=
make that CVS stuff work. It just doesn't. The authentication method is =
mess, Sourceforge instructions are completely greek to almost any user in=
this world, and the 'easy step by step tutorial' leads you to nowhere.
No way, I gave up CVS.
The only way to make me (and, probably most of us) upload directly to thi=
CVS thing is to build a web interface that let us do it. A lot of work, I=
guess, but if you decide that it is worth...
Basically, my opinion is that we should divide the audacity editor in two=
one part is the program it self and the other is language file(or files).
Making the program download the newest lang file from the internet, we co=
have an 'universal' installation and a localized user interface.