Visit our Popular Forums

Totobeloeil · 01-04-2010, 13:16

Quote:

Originally Posted by champ8242

my .po file (_nl_NL) is now filled with a reference to the source code on MY system and line numbers.

Line numbers are only comments (character # in first position if I remember). So it could be considered as not really important. If I remember, the comment lines disappeared from v1.3.6 po-files.

Quote:

I think it’s better if Dave will supply us with a new base .po file NOT?

I can't answer for Dave. Maybe it could be an occasion for somebody else to make a little bit of the work.

Quote:

Originally Posted by idpnd

I am either waiting for someone to tell me how to place the i18n hooks within the code to extract the missing strings OR hope more extensive .pot files materialise in the future - although the development priority is 2.1.0 beta testing at the moment so no rush really

From what I understood :
POedit calls a program (gettext) which searches for some function-calls inside the source-code (like function "_()", for example) to get the strings to be extracted.
The function-calls to take in account may be listed in POedit catalog-config but there are some default function-calls if nothing appears into the list.

For me, there is nothing to update inside OCPN code to get the missing strings to be translated, because the strings are already "tagged". Just executing POedit on OCPN new version should be sufficient.

Quote:

Originally Posted by idpnd

The strings for translation (.pot) was provided by Dave, and there were still a few missing from 1.3.6. There is an updated file for 2.1.0 containing new strings since 1.3.6 (but still not all of them) available at sf.net

Now, I believe the work to do is :
(1) wait for "a certain degree of stability" in user-interfaces (dialogs, etc ...).
(2) take in account all the translations made recently
(3) re-execute POedit on the whole source-code to get all the missing strings.
Maybe we need to execute POedit for each language (+ the .pot file). But it might be automatized.
(4) complete the translations before the distribution-package is made (if possible).
(5) There will always exist some translations not available inside the distribution-package.
So we need to :
(5.1) make the translation-files available on some server
(5.2) determine how to upload the updated translation-files
(5.3) let everybody know where to find these files and how to proceed (to use and to update them).

POedit is good for us. Try it !

Jean-Pascal

champ8242 · 01-04-2010, 13:48

Quote:

I can't answer for Dave. Maybe it could be an occasion for somebody else to make a little bit of the work.

No problem with this thought. We (I) must know what we're doing and not causing a lot of extra work for the increasing number of translators.

I will test your 5+ steps (most I did already) and see how it works. If there are more pointers, please don't hesitate.

Bart

Totobeloeil · 02-04-2010, 00:13

Quote:

Originally Posted by champ8242

No problem with this thought. We (I) must know what we're doing and not causing a lot of extra work for the increasing number of translators.

Take care not to generate extra work for you as well.
While we were talking about it, Dave has updated CVS source-code (here).
So, it seems there is nothing let to be done for now.
Jean-Pascal

champ8242 · 02-04-2010, 00:33

Quote:

Take care not to generate extra work for you as well.

the extra work a was talking about if I initiate something and not doing it right causing extra work for others

Gilletarom · 02-04-2010, 01:32

Hello

I am part of the Marine group that put up the tutorial in French. We continue our work on OpenCPN.

I suggest it joins a new language file for the French version to version 2.1.331.

Best regards

Gilletarom.

--------

Bonjour,

Je fais parti du groupe de marin qui a mis en place le tutoriel en Français. Nous continuons notre travail sur OpenCPN.

Je vous propose ci joint, un nouveau fichier de langue pour la version Française pour la version 2.1.331.