[Panicbutton-translators] Effort of translating Panic Button a three pronged one

[Gerard J. <ger...@a2...>]

Hi,

since we've got the list now, I'll certainly make use of it too. I am=20
currently busy translating Panic Button into German and noticed that the=20
effort is obviously a three pronged one, that might need some additional=20
coordination.

Here are some of my thoughts, obviously for anyone to discuss (why would=20
I post them here otherwise ;-)):


1) Translation of the .po file (the trivial part actually)

That is obviously nicely coordinated through the gettext framework - as=20
long as we work with a single .po file here, there's hardly any reason=20
why filenames should "collide".

As I suggested to Russ though, it may be a good idea to already think=20
about a naming convention for the filenames of the .po files here -=20
while the number of translations is still small and thus the effort to=20
rename the files to match a certain naming convention is not too much.

To be more constructive in my "criticism" here: I would suggest to name=20
the .po files using the ISO 639/3166 codes for country and language (one=20
language may be spoken in different countries with slight variations -=20
think of US-English as to Britisch English) - something like "en_GB.po"=20
or "de_DE.po" for example.


2) Translation of the helpfiles (needs more elbow-grease)

Here things become a bit trickier - obviously the filenames will collide=20
with each other if we just translate the contents of files like=20
"01.html" yet keep the filename and/or location.

Question here: should it be a "feature" that any newly installed=20
translation of a helpfile overwrites the current one, or should one=20
instead be able to choose from a set of languages, perhaps even be=20
allowed to change the languages in the configuration of Panic Button "on=20
the fly"?

In that case I'd think we need a convention for the help file=20
directories - a combination of language and country code immediately=20
springs to mind (like "de_DE" and "de_CH" to distinguish between German=20
German and Swiss German, or "en_GB" and "en_US" for English Englisch and=20
US English). Obviously the ISO 639/3166 codes would apply:=20
http://www.gnu.org/software/gettext/manual/html_chapter/gettext_15.html#S=
EC221=20
and=20
http://www.gnu.org/software/gettext/manual/html_chapter/gettext_16.html#S=
EC222=20
specify those.


3) Translation of the Installer (currently needs some more extra thought)

The PanicButton.aip file can obviously be found in the CVS:

http://panicbutton.cvs.sourceforge.net/panicbutton/panicbutton/MSI/PanicB=
utton.aip?view=3Dlog

One would require the "Advanced Installer"=20
(http://www.advancedinstaller.com/) for this part to be revised=20
according to the language in use - and that's where my "problems" (well=20
perhaps only: perceived problems) start: this tool only allows to create=20
an "English speaking Installer" (at least the Freeware version - the=20
Professional and Enterprise versions come with 15 languages supported),=20
plus it's requiring anyone participating in the translation process of=20
Panic Button to actually purchase (as said, the Freeware version is only=20
available in English) a closed source software in order to take part in=20
an open source project - which raises at least some of my neck-hairs.

I would suggest to think about using an open source installer here -=20
things like InstallJammer (http://www.installjammer.com/) or NSIS=20
(Nullsoft scriptable install system - see=20
http://nsis.sourceforge.net/Main_Page) seem to fit the bill a bit better.

NSIS supports at least 40 interface languages (plus you can create your=20
own, so if you need a Klingon speaking one, that shouldn't be much of a=20
problem either ;-)), InstallJammer currently only boasts Spanish and=20
French as alterantives to English, yet supports multiple platforms too=20
(not yet relevant - but why should Panic Button be locked into Windows=20
only in future too?)

Since the possible migration to an alternative installer may quickly=20
develop into a "project within a project", perhaps a "roadmap" of where=20
to put which file should be charted, so that whoever wants to start work=20
on an alternative installer.

Currently that exercise looks fairly simple: as far as I can see,=20
currently the installation stuffs all the files into the usual Windows=20
programs directory, and creates shortcuts in the Start-menu (a) creating=20
a folder for PanicButton and b) adding a shortcut to the PanicButton.exe=20
in the Autostart folder).

If that's really all there is to it, any installer should do the trick -=20
what about new file locations for the internationalised version though?

What sounds obvious here probably results in a "staged translation"=20
effort as a consequence:

a) first translate the .po file (trivial, as I said - poEdit seems to do=20
a pretty good job in providing a comfortable environment for this)
b) create screenshots of the new user interface, to be used in the helpfi=
le
c) translate the helpfile
d) create an installer - best choice here would obviously be one where=20
(as a user) you select the installation language and then automatically=20
end up with an installation of Panic Button in your chosen language.

Obviously this repeats with each new release as the features of Panic=20
Button become more - sounds like an ever increasing amount of work just=20
to manage that, never mind working on Panic Button itself.

Should we really coordinate that in a centralised spot (e.g. the Panic=20
Button website that Russ provides) or should we decentralise that effort=20
and make the maintainer of each translation responsible for the=20
provision of both the zip file and installer version of PanicButton,=20
even if this means that not every new version may not immediately be=20
available in every language of the previous version?

As I said - just some thoughts...

Kind regards

Gerard

--=20
 From a2b Consulting GmbH     Gerard Jensen
R=F6dingsmarkt 39              mailto:ger...@a2...
20459 Hamburg                http://www.a2b-consulting.com/
-----------------------------------------------------------------------
Tel: 040-657934-60           Fax: 040-657934-62     Handy: 0160-8050313
-----------------------------------------------------------------------