OpenCPN Internationalization ( i18n )

[Highlander_et]

Hi

Estonian update for OpenCPN 3.3.1419 wiht Dashboard and Grib

[Gilletarom]

Hello,

Here join updated files for :

French language file for Grib

French language file for Dashbord

Best regards Gilletarom

[bcn]

Translators for your information, there is a specific thread for the S63-Plug-in as Dave has to keep this separated from the main code:

http://www.cruisersforum.com/forums/...ns-123706.html

[CarCode]

German po files for opencpn, dashboard, grib.

Gerhard

[Gilletarom]

Hello Dave,

O331606 : OpenCPN french file language (using pot file version 2014-04-05)

[Highlander_et]

Hi!

New estonian translation in attachment.

Regards

[SamsonovAnton]

Russian translation for OpenCPN, Dashboard and GRIB. Use at your own risk.

[Hakan]

POT-file creation – help needed
The br24radar_pi plugin is close to be ”official” on Opencpn.org but we need some help to create the pot file. For OCPN and plugins the pot file is updated during built when a valid “POTFILES.in” is present. I understand this is controlled by “CMakeLists.txt” and I have compared our “CMakeLists.txt” with these for other plugins and can’t find any significant difference why this is not working.
Please I need help to learn how the initial pot file is created either by descriptions here or point to a wiki.
Our cmakelist is attached (discard the .pdf extension).

Thanks Håkan

[nohal]

Hakan...
I didn't look at the file yet, but to there are 2 conditions:
1) you must have the whole gettext toolchain available
2) You must build the respective build target (POT-update and PO-update) to regenerate the .POT or .PO files.

Let me know if it worked, if not, I will look at your code over the weekend and fix it.

Pavel

[Hakan]

Many thanks for answering. You're as solid as usual.

Originally Posted by nohal

Hakan...
I didn't look at the file yet, but to there are 2 conditions:
1) you must have the whole gettext toolchain available

Since OCPN and the other plugins get there's POT and PO files updated during build I presume the toolchain is correct.

2) You must build the respective build target (POT-update and PO-update) to regenerate the .POT or .PO files.

"..the respective.." That's the part I don't understand. How do I build the POT file? Isn't that in cmakalist, the "pot.dummy" part?


Håkan

[nohal]

Hakan...
there should be a pot-update project generated even for VS, I don't really remember.
Or do it from command line with

cd <your_build_dir>
cmake --build . --target pot-update

and the POT will get regenerated
with

cmake --build . --target po-update

It should look similar to the following even on Windows:

nohal@knut:~/source/opencpn/build$ cmake --build . --target pot-update
Scanning dependencies of target pot-update
[100%] pot-update [opencpn]: Generated pot file.
[100%] pot-update: Done.
[100%] Built target pot-update
nohal@knut:~/source/opencpn/build$ ^C
nohal@knut:~/source/opencpn/build$ cmake --build . --target po-update
Scanning dependencies of target po-update
[  0%] po-update [opencpn_fr_FR]: Updated po file.
[  0%] po-update [opencpn_es_ES]: Updated po file.
[  0%] po-update [opencpn_de_DE]: Updated po file.
[  0%] po-update [opencpn_nb_NO]: Updated po file.
[ 16%] po-update [opencpn_it_IT]: Updated po file.
[ 16%] po-update [opencpn_da_DK]: Updated po file.
[ 16%] po-update [opencpn_fi_FI]: Updated po file.
[ 16%] po-update [opencpn_et_ET]: Updated po file.
[ 33%] po-update [opencpn_tr_TR]: Updated po file.
[ 33%] po-update [opencpn_nl_NL]: Updated po file.
[ 33%] po-update [opencpn_gl_ES]: Updated po file.
[ 33%] po-update [opencpn_hu_HU]: Updated po file.
[ 50%] po-update [opencpn_el_GR]: Updated po file.
[ 50%] po-update [opencpn_ca_ES]: Updated po file.
[ 50%] po-update [opencpn_ru_RU]: Updated po file.
[ 50%] po-update [opencpn_cs_CZ]: Updated po file.
[ 66%] po-update [opencpn_pl_PL]: Updated po file.
[ 66%] po-update [opencpn_zh_TW]: Updated po file.
[ 66%] po-update [opencpn_pt_BR]: Updated po file.
[ 66%] po-update [opencpn_pt_PT]: Updated po file.
[ 83%] po-update [opencpn_sv_SE]: Updated po file.
[100%] po-update: Done.
[100%] Built target po-update

Pavel

[nohal]

Oh..
And I forgot to add one more thing, for plugins built inside the OpenCpn tree, you will need something like

cmake --build . --target grib-pot-update

Of course replace "grib" with the name of the respective plugin.

[Hakan]

Originally Posted by nohal

Oh..
And I forgot to add one more thing, for plugins built inside the OpenCpn tree, you will need something like

cmake --build . --target grib-pot-update

Of course replace "grib" with the name of the respective plugin.

Yes -- and thanks Pavel. There is was. Cmake pot-update works fine.
And your text "there should be a pot-update project generated even for VS" finally kicked in some thinking activity also in by brain. Yes it is done in VC as well, and very clear, it was nothing else then to read a couple of rows up to find: "br24radar pot-update" and build only that project as usual. It was too obvious?
Thanks for your patience, I really appreciate your support.
Håkan

[Hakan]

More basics:
Is there maybe a nice short answer to this as well?
Now I've one mo file,"opencpn-br24radar_pi.mo", in the correct directory but br24radar_pi.dll is not translating anything.
Where is the call to read the files in the "LC_MESSAGES" lib? Is it a function in every plugin that we could have missed? (I've compared with other plugins but didn't find it)

Thanks Håkan

[CarCode]

There should be a line with:

AddLocaleCatalog( _T("opencpn-br24radar_pi") );

in file br24radar_pi.cpp but it is not.
Obviously it was not made for localisations.

So you must do it yourself and prepand all strings for localisation with "_(" instead of "_T(" or "wxT(".

Gerhard