Ocpn-Draw and Boundary

[jongough]

Hi,
Here is a newer POT file based on feedback from the last one.

Regards
Jon

[Gilletarom]

Hello Jongough,

Originally Posted by jongough

Hi,
Here is a newer POT file based on feedback from the last one. ...
Jon

Thank you. But even if we can bring with us using PoEdit, as we do not have a compiled version of the plugin using the new language file, this is not used much.
It is imperative to send the crowdin, giving us time to translate and integrate it into a compiled version of the plugin to make it operational.

Nota bene :
However, you can compile a new version of your plugin, taking into account your new language file, even if you do not have translation yet. Meanwhile, you can provide us the potfile that we can bring home. We can then integrate the French version in the PC.
Theoretically, we can also send by upload the translated version crowdin. BUT it must be done when the language file is up to date on the crowdin. In my opinion it should be avoided as the risk that we may not be synchronous is too big.

Best regards. Gilletarom.

[NAV]

Originally Posted by jongough

Hi,
Here is a newer POT file based on feedback from the last one.

Jon,

Using the latest versions of Draw and the pot-file, I still miss the following strings in the pot-file:

• 'OCPN Points' (tab in the OCPN Draw Manager);
• 'Boundary' (first word in pop up window when pointing to a boundary on screen; word is repeated 3x in other lines in this window as part of a longer string; also first word in rollover info text);
• same as at second bullet applies to 'Boundary Point'
• when clicking on Properties for both a Boundary and a Boundary Point, the title bars of the properties windows still display the word Boundary or Boundary Point in the strings 'Boundary Properties' or 'Boundary Point Properties';
• all icon names of the Draw Toolbar are still displayed in English, although I translated these in the language file.;
• the title words of the title bar ('Draw Toolbar') are also still in English.

I want all these terms to be displayed in Dutch .... Especially because the English terminology can be very confusing for Dutchmen (and for the French, so I understood from Gilletarom).

[NAV]

Originally Posted by bcn

Projected Position would describe it more correctly?

It's a possibility, but I can live with DR. Most people will understand what it indicates. And in Dutch I can use a 'free' translation.

[bcn]

NAV...

if it is not correct (or just sluggish) then we shall put the right wording - not just in one language.
Had a look into Tom Cunliffe's book and that convinced me that your worries will be shared most probably by more people.

Jon...
what do you think?

Hubert

[NAV]

Originally Posted by jongough

Nav,
OD has two basic objects, a Point, known now as an ODPoint, which are the same as waypoints/marks in OCPN, and a Path. You place Points on the chart and these are georeferenced, i.e. they stay in the same spot (Lat/Lon) when you move or scale the chart. You can join points together with a path, i.e. a path between two or more points, which you will see called Boundaries, EBL's (Electronic Bearing Lines), DR's (Dead Reckoning lines). ODPoints are currently represented by Boundary Points, Text Points, EBL Points and DR Points.

At the moment Paths are constrained to be straight lines between two points, even ones using Great Circle plotting. It is quite possible to extend this to curved lines, i.e. splines, if it is needed, but, as of yet, I have not had to.

Hope this helps.
Jon

Jon,

I think I fully understand your explanation. What I don't understand yet, is the functionality of the Path tab in the Preferences section. You can apply properties to rectangular boundaries, circle boundaries, EBL and DR, and each has his own preference tab. What functionality is added by the properties you can enter under the Path tab?

[Hakan]

NAV..
Have you seen patch 619?
I couldn't attache the file due to its size but get it here if you like:
https://dl.dropboxusercontent.com/u/....619-win32.exe
Håkan

[NAV]

Originally Posted by Hakan

NAV..
Have you seen patch 619?
I couldn't attache the file due to its size but get it here if you like:
https://dl.dropboxusercontent.com/u/....619-win32.exe
Håkan

I hadn't. Now installed and several 'translation problems' seem to be solved now ...Will further investigate .
Thanks Håkan!

[jongough]

Hi,
I have put a windows install exe for patch 619 up on dropbox, you will find it here:
https://www.dropbox.com/s/chiu4scrug...win32.exe?dl=0

This has all the latest changes to match the new POT file. I fixed up many of the strings that had not been translated so that they would be. I have included the latest language files for french and dutch (I have only tried the french one an this showed me what was missing).

Regards
Jon

[NAV]

Originally Posted by bcn

NAV...

if it is not correct (or just sluggish) then we shall put the right wording - not just in one language.
Had a look into Tom Cunliffe's book and that convinced me that your worries will be shared most probably by more people.

Jon...
what do you think?

Hubert

The expression I presently use in Dutch (translated into English) is something like 'track-prediction' or 'guessed track', and 'predicted track-points'. But I'm still working on the translation of the plugin so things might change again.

[NAV]

I still see some strings that are not or not correctly translated:

• 'Arrival radius' (shows old translation instead of last one)
• Persistent (no translation shown at all)
• 'Never', 'Always' and 'Distance' (show old translations instead of last ones; might be caused by same string in core OpenCPN, I still have to check that)

[NAV]

I don't see the single word 'Path' in the pot-file.

[jongough]

Hi,
For those of you who don't have a latest OCPN you will find it here:
https://www.dropbox.com/s/q4x7afjfua...setup.exe?dl=0

This is needed as it has SVG in it and the version of OD I put up requires it.

Regards
Jon

[bcn]

later than 4.3.1317 from today?

http://www.cruisersforum.com/forums/...ml#post2019597

[jongough]

No, 1317 is fine. If you were using 1301 you would need the latest from git as there were new API's added which OD uses. BUT you do need to use the SVG version of OD with the SVG version of OCPN. If you build it clean with a new cmake it should be OK, however, if you have been building before you need to make sure -DOCPN_USE_SVG is specified for OCPN and -DOD_USE_SVG is specified for OD on the cmake command line.

Jon