SaltyPaws Plug-in SAR

[Gilletarom]

I create some route and I see that :
- for the first route the name was .gpx.gpx
- for the second route .gpx.gpx.gpx (because I click on the first file name of route and I change only the 1 in 2 then your plug-in add automatically ".gpx"
- Then ... for the third route .gpx.gpx.gpx.gpx

.....

Gilletarom.

[Gilletarom]

Hello Salty Paws,

You now certainly that I work around OpenCPN and all the plug-ins. My work is only : Translate all file language in french.

So, I see that in your 3 plug-ins (Route, SAR, Calculator) there is many items.

So, I thing that it is necessary to translate all these 3 plugins.

Have you create the po file and the pot file for each plug-in ? If "yes", where are they ?

Best regards

Gilletarom.

[SaltyPaws]

Hello Gilletarom,

Thank you for the bug-report, I thought this was fixed, but it looks like a regression . Will look into this for the next version.

Also, much obliged for your translation efforts . PO files are here:

https://github.com/SaltyPaws/calcula...tree/master/po
https://github.com/SaltyPaws/SAR_pi/tree/master/po
https://github.com/SaltyPaws/route_pi/tree/master/po

I haven't worked with these files before, so please have a look whether they are the right format and have the right input. If not, please let me know the best way to fix this.

Are you planning to branch the plugins, so that I can integrate the translations through pull requests on github?

How do I incorporate the language files in the binaries? Do I need to recompile or is it sufficient for the user to download the translation file.

[Gilletarom]

Originally Posted by SaltyPaws

Hello Gilletarom,
....
How do I incorporate the language files in the binaries? Do I need to recompile or is it sufficient for the user to download the translation file.

I usually take the last ".po" file. I load the last file ".pot". Using poEdit, I proceeded to update the ".po" file. This eliminates obsolete items and incorporates new items.
It is sufficient to make the translation of these items in poEdit. It then saves the file in. This creates a file ".mo".

In normal times, just put the file ".mo" in the folder share so that everything works normally.

But I do not know what developers need to do to make it work. The easiest way is to ask Dave, JesperWe or Pavel Nohal.



B.R.

Gilletarom.

[SethDart]

Originally Posted by SaltyPaws

How do I incorporate the language files in the binaries? Do I need to recompile or is it sufficient for the user to download the translation file.

Hi,

Here's the process created for all plugins:

- Do this when your codebase is set or when you add some source files to your plugin. This will create/update the list of files that must be searched for strings to be translated.

cd plugins/{$plugin}/
find src/ -name \*.cpp -or -name \*.h -or -name \*.hpp >po/POTFILES.in

- When you are ready to release your plugin (string freeze) create/update the default .pot file

cd build/
make {$plugin}-pot-update

- You can also re-sync existing .po files with the new .pot strings created/updated above. Then translators can take these updated files and rework them if needed.

cd build/
make {$plugin}-po-update

- When you receive a .po drop it to plugins/{$plugin}/po/{$lang}.po
You may need to re-run cmake so this new file is processed.

cd build/
cmake ../
make

You should see something like that:
[ xx%] {$plugin}-i18n [{$lang}]: Created mo file.
[ xx%] {$plugin}-i18n: Done.

- In your plugin Init() you should call

AddLocaleCatalog( _T("opencpn-{$plugin}_pi") );

to load appropriate translation file.

- When you run make install, the files will be installed and renamed for all this to work. Unfortunately, we don't have any tool to package plugins with language files. If you create a package with your plugin, they will be correctly included. When we switched to cmake, there's no way to create sub-packages. I don't know if it has changed since but will have a look.

Hope this helps ;-)

You can ask question if it's not clear, I did big parts of the cmake build process in the last few years so I should be able to reply...

Warning: make {$plugin}-pot-update and make {$plugin}-po-update depends on how you called them in plugins/{$plugin}/CMakeLists.txt It should match you plugin name.

[Gilletarom]

Hello Salty Paw

Originally Posted by SaltyPaws

Hello Gilletarom,

.....

PO files are here:

https://github.com/SaltyPaws/calcula...tree/master/po
https://github.com/SaltyPaws/SAR_pi/tree/master/po
https://github.com/SaltyPaws/route_pi/tree/master/po

I haven't worked with these files before, so please have a look whether they are the right format and have the right input. If not, please let me know the best way to fix this.

....

In the current state of things:
1 I found versions with different ages in the same pot file in your links.
2 Your pot files do not contain any items.

Files are currently unusable for translators.

You must follow the instructions given by the SethDart friend.

Best regards

Gilletarom

[SaltyPaws]

find src/ -name \*.cpp -or -name \*.h -or -name \*.hpp >po/POTFILES.in

Works like a treat and I obtain my POTFILES.in files in the po dir

Originally Posted by SethDart

cd build/
make {$plugin}-pot-update

- You can also re-sync existing .po files with the new .pot strings created/updated above. Then translators can take these updated files and rework them if needed.

make route_pi-pot-update

This gives me the error: make: *** No rule to ../build/make target `route_pi-pot-update'. Stop.
(I have also tried this command from the subdirectories)

Originally Posted by SethDart

Warning: make {$plugin}-pot-update and make {$plugin}-po-update depends on how you called them in plugins/{$plugin}/CMakeLists.txt It should match you plugin name.

I have checked my CMakeLists.txt and the packagename is the same as the directory name and matches the name called in the init section (all the same case)

Please let me know how I can fix this Thank you!

p.s. for the .gpx.gpx error, I checked the 0.7 version and it was ok on linux. What is the version of the plugin where you spotted the bug? Did you use it on windows or linux?

[SethDart]

Originally Posted by SaltyPaws

make route_pi-pot-update

This gives me the error: make: *** No rule to ../build/make target `route_pi-pot-update'. Stop.

According to
https://github.com/SaltyPaws/route_p...Lists.txt#L153

you named that rule "ROUTE-pot-update"

So you should run

make ROUTE-pot-update

(same for -po-update, see line 176)

[SaltyPaws]

Thanks to SethDarth's advice, all three pot files are ready for translation. For the command to work, an empty .pot file is required in the po folder.

[Gilletarom]

Hello Salty Paws

Here I join three french language files for your three plug-ins. I can use the threes files with Route, SAR and Calculator without problem under W XP SP3, OpenCPN 3.1.1919.

These files are beta files but they are usable. You can place these files for download.

Below I speak about Route plug-in :

1 The name of the language file should be: "OpenCPN-route_pi.po" and therefore "OpenCPN-route_pi.mo." Same system with the two other plug-ins

With this constraint, the French language file in the enclosed works very well.

2 It is reasonable that the file name. "Pot" was "OpenCPN-route_pi.pot."

3 The first tab is called "Great circle" but he treats both "Great circle" that "Rhumbline". The name of this tab is inadequate.
In French I hesitate between "direct routes" and "naturals routes".

4 ° In the tab title "Route limited", I put "Route Limited \ n (in latitude N or S)." the second part of the text does not have to be written in character as big as the first part.

5 ° In fact, the titles of two tabs are already in the tab name. he must keep ... I propose to remove except for the tab "Route limited." In this tab I'll just put "Limitation latitude N or S".

6 In the "Route limited" in front of the area to the maximum or minimum latitude, there is "NM" ... This is not a distance. ....

7 ° South latitude How to enter? with a "-" or "S"? It is not obvious. A better.

8 To calculate a route limited, it would be good in the right area, there is an additional input to set the latitude limit. So this latitude would directly get into the left area of ​​the tab.

9 When you save a route, the name is always twice the extension ". Gpx.gpx." This is true for all types of roads. This bug is not yet resolved.


10 ° can be saved in two different roads "Route limtées" under the same name, but be warned ... Adaptation is necessary


Below I speak about calculator plug-in :

1° It is necessary to add a vertical slider on the help window (for little screen)

2° The calculous window do not run correctly ...

B.R.

Gilletarom

[yoruk]

Bonjour
What means these two numbers in the RNG window ???
0.36 is the distance between the boat and the active WP
But… what is 0,12 ???

Michel

[Gilletarom]

Originally Posted by yoruk

Bonjour
What means these two numbers in the RNG window ???
0.36 is the distance between the boat and the active WP
But… what is 0,12 ???

Michel

C'est parce que OpenCPN regarde à la fois la distance par rapport au waypoint actif et par rapport à un autre waypoint. Mais cette valeur n'apparait pas toujours. OpenCPN est en difficulté dans ce domaine.

[yoruk]

Merci Gérard

It is also possible that this is related to the problem of instability of GPS receiver ???

[yoruk]

Merci Gérard
It is also possible that this is related to the problem of instability of GPS receiver

[Gilletarom]

Originally Posted by yoruk

Merci Gérard

It is also possible that this is related to the problem of instability of GPS receiver ???

No, it is impossible that the problem of instability of GPS was concerned.

I am convinced that the instability of GPS is closely linked to the quality of those receiving it. And sometimes, for those who use VHF RT 650 (RO 4800), to update these VHF in terms of firmware version


In french :
Je suis persuadé que le problème d'instabilité des GPS est intimement lié à la qualité de la réception de ceux ci. Et parfois, pour ceux qui utilisent les VHF RT 650 (RO 4800), à la mise à jour de ces VHF au plan de la version du logiciel interne.

Gilletarom.