I agree with idpnd.
I have tagged almost all of the screen-visible messages in opencpn
for potential translation. If the en_US words look right to you in your native language, then you may skip the translation of that message. Opencpn
will use the en_US message by default if no translation is supplied, on a per-message basis.
I will be adding more messages for the next Beta, and probably removing some which are clearly non-sense, like "". It is an interative process, but any work you do now will not be lost
, as it will be merged for later improvement.
Getting the opencpn.pot from sourceforge cvs browser, or even cut-and-paste, is just fine. Whatever works best for you is OK. There is only one current
.pot file at any one time.
Looking ahead, the next Beta will have idpnd's German translation available for general use. opencpn_de_DE.po will be in the CVS source tree, with some new untranslated strings added. idpnd's job is to download the new .po file, complete the new translations, test if desired, and send the result to me to be rolled forward. Same for other translations. I am updating the Makefiles so that this happens semi-automatically.
I think this process will work, understanding that the current
Beta at any point will usually contain untranslated strings waiting to be updated for the next Beta, and so one level out of date, so to speak.
Question for all: Has anyone successfully created a .po/.mo for Windows platform, copied the .mo to opencpn/lang and gotten it to work? I've played around with it, but cannot get my VirtualBox XP setup to recognize locales other than my default. This stuff has a high fussy factor.....