OpenCPN Internationalization ( i18n )

[Gilletarom]

Hello,

French Done. I hope that my translations are Ok.

[Rasbats]

Håkan has added the .pot file for VFKaps to Crowdin. Would appreciate help from translators to get translations ready for any future update.

Mike

[AISEAG]

Originally Posted by Rasbats

Håkan has added the .pot file for VFKaps to Crowdin. Would appreciate help from translators to get translations ready for any future update.

Mike

Done for French language

Serge

[stelian]

I have a question about translation priority between core and plugins, hope this is the right place.

In OpenCPN's code (OCPNPlatform.cpp, around line 765) it is explicitly stated that core translations are of highest priority, overriding the ones in the plugins. This makes sense for OpenCPN core.

But this also causes problems in some plugins, where some translated strings are taken from the core translation file instead of the plugin translation file (there are quite a few examples of this in French, for example see https://github.com/seandepagnier/wea...g_pi/issues/61 for one of them).

How can this be dealt with ?

[Gilletarom]

Originally Posted by stelian

I have a question about translation priority between core and plugins, ....

How can this be dealt with ?

It's simple. The language files of the plugins are loaded first. Then, the core language file is loaded. the whole thing is a single language file.
If an item appears in a language file of a plugin and also, strictly identical, in the file of the core, this constitutes a single item. So the translation of the core takes the place of the translation of the plugin.

The solution, to avoid translation conflicts, is that plugin developers must ensure that the items they use are different from those of the core.

It is not necessary that the difference be very great. Only one different character is enough.

[jongough]

Hi,
ODraw uses a process to make sure its translations for are used for all its items. It does not affect the mainline translations, just the translation catalogue used by ODraw is its own. All plugins can use this method without impacting any other. The one downside is that you need to have translations for all words as the cascade back through the different catalogues may not give you the answer you expect. This is achieved by redefining the translation macro (done by cmake and compiler) such that the source code looks the same, but the catalogue being used is different.

This process is currently used in the ODraw and Watchdog plugins. It is a simple change to a couple of files to implement.

Jon

Originally Posted by stelian

I have a question about translation priority between core and plugins, hope this is the right place.

In OpenCPN's code (OCPNPlatform.cpp, around line 765) it is explicitly stated that core translations are of highest priority, overriding the ones in the plugins. This makes sense for OpenCPN core.

But this also causes problems in some plugins, where some translated strings are taken from the core translation file instead of the plugin translation file (there are quite a few examples of this in French, for example see https://github.com/seandepagnier/wea...g_pi/issues/61 for one of them).

How can this be dealt with ?

[stelian]

Originally Posted by jongough

This process is currently used in the ODraw and Watchdog plugins. It is a simple change to a couple of files to implement.

Thanks, this is what I was looking for. I'm not sure yet if I want to do this globally for all the plugin or just overwrite a few translations.

[rgleason]

I've added an FAQ section in the Wiki. Thank you Stelian and Gille for the clear answer.

Are there any other items of concern that should be added to help others starting out?

Thanks.

https://opencpn.org/wiki/dokuwiki/do...nalization#faq

[rgleason]

Updated again
https://opencpn.org/wiki/dokuwiki/do...ationalization

[rgleason]

Are there additional notes required which will augment Stelian, Gille and Jon's input?
Perhaps regarding the translator's use and the process?

Can Hakan explain what he does?
Found it.
https://opencpn.org/wiki/dokuwiki/do...ugin_languages

Any other additions?
Thanks.

[rgleason]

We need to update weather_routing crowdin files.

This is what I've determined so far:
We need to know more about the process that Pavel set up. 3 managers, jongough, hakan, bdbcat.
https://crowdin.com/project/opencpn
You can register for free as opensource, to the OpenCPN account.
https://crowdin.com/project/opencpn/activity_stream
there is a French translation https://crowdin.com/project/opencpn/fr#
Down toward the bottom is weather_routing, click
https://crowdin.com/translate/opencpn/126/en-fr
There are currently 9 pages of terms/phrases in the pot file for wxrte against which there are many language translations.


We now have new files for weather_routing translations. How do we upload these without screwing up the base english terms/phrases and other translations?
I think they've been working on French using the raw file.


How are these files updated to Opencpn Crowdin?
Perhaps there is a problem of database divergence here?
Shouldn't we be using the Crowdin interface and someone should update the base terms?

[Hakan]

All.
Weather_routing_pi is already in Crowdin. I could make a new pot file and update if you like?
I haven't been focused on this pi for a while. Core code is still From https://github.com/seandepagnier/weather_routing_pi master I suppose?

Håkan

[Gilletarom]

Originally Posted by rgleason

We need to update weather_routing crowdin files.
.......
We now have new files for weather_routing translations. How do we upload these without screwing up the base english terms/phrases and other translations?
I think they've been working on French using the raw file.

How are these files updated to Opencpn Crowdin?
Perhaps there is a problem of database divergence here?
Shouldn't we be using the Crowdin interface and someone should update the base terms?

I do not quite understand what it is.

1 ° Has the language file in English been modified?
If so, only bdbcat, Jon and hakan know how to load the new English language file into the crowdin.
Translators can then update the translation in their own language.

2 ° The language file in English has not been modified. That is, no items deleted, no items added, and probably also no changes in the links of each item with the location in the code where it is used. (Pavel, am I wrong ?)

In this second case, using poedit, for example, a new version of the language file in a language other than English, for example French was created.
You want to send all the new French translations to the crowdin, so that the new translations of the French language file take the place of the old translations.
This is very easy, it is not necessary for bdbcat, Jon or Hakkan to intervene. Just upload the new French ".po" file using the ad-hoc icon in the WR plugin file line.This icon is at the end of the line, on the right, in the line of the French language file. WR.

Am I understanding?

Gilletarom.

[Hakan]

1.
All.
I've made a new .pot just now. It's ready for upload to Crowdin if you like.

2.
Gilletarom.
There's not a French .pot file. Our .pot file is a list of English phrases to be translated, i.e. the "base" in Crowdin. The translations are collected in .po file for each language later passed to the plugin's core code.
It may be you can copy your own .po file to Crowdin för further work but if your .po file is based on a old .pot file there may be mismatches. I've never tried.

[rgleason]

Ok I think I understand most of it now. Thanks guys.

1. Weather_routing.pot is the file for the English Language. Gille does not think it has changed at all. This needs to be confirmed somehow. I will get the files from Stelian and check manally using Crowdin. Also Hakan has made a place for a new pot file in Crowdin -Opencpn.

2. The FR.po (French.Po) file has been modified and does need to be uploaded. It can be uploaded by anyone logged in. Stelian's repos has that. Before uploading it, (Upload is in the dropdown menu) we need to confirm that POT has not changed from what is on Crowdin.

Is this correct?