OpenCPN 5.6.2 Released

[nohal]

The error in the french translation (https://github.com/OpenCPN/OpenCPN/b...po#L4533-L4535) is already fixed in Crowdin and the correct translation will be included in the next release.

[houlejm]

Originally Posted by nohal

The error in the french translation (https://github.com/OpenCPN/OpenCPN/b...po#L4533-L4535) is already fixed in Crowdin and the correct translation will be included in the next release.

Thanks nohal
That is what i expected
JM

[Gilletarom]

Originally Posted by houlejm

There is also an error on the scale label on the lower left corner of the chart.
I made a change and comments in crowdin.
JM

If it's a programming error, maybe you shouldn't change anything in the translations. To understand ???.

JM, I guess the "Nds" item is still in question.

Probably the same small programming error is involved.

[Gilletarom]

Originally Posted by nohal

The error in the french translation (https://github.com/OpenCPN/OpenCPN/b...po#L4533-L4535) is already fixed in Crowdin and the correct translation will be included in the next release.

Hello Nohal,

I read what is in the screenshot. below.

I guess you will change by replacing Nds by NM? If so, that's fine.

The change is not yet visible in the Crowdin, but I assume it will appear.

[nohal]

I don't know where you are looking, but to me it seems quite visible in Crowdin. As you can see it was already corrected 3 days ago by @houlejm, I just didn't like the long translation as it occupies too much space in some of the places where this unit it used.

[Gilletarom]

Originally Posted by nohal

I don't know where you are looking, but to me it seems quite visible in Crowdin. As you can see it was already corrected 3 days ago by @houlejm, I just didn't like the long translation as it occupies too much space in some of the places where this unit it used.

I look this link: https://github.com/OpenCPN/OpenCPN/b...po#L4533-L4535

I understood your correction yesterday, in the Crowdin, which concerned the translation of the English item "NMi". And you replaced with "NM". Okay.

But, in the link we observe that the translation of "NMi" is "Kts" instead of "NM". This is the anomaly.

[nohal]

Originally Posted by Gilletarom

But, in the link we observe that the translation of "NMi" is "Kts" instead of "NM". This is the anomaly.

There is no anomaly, translations are synchronized from Crowdin only before the releases.
You may perhaps suggest to the french users on HeO to help test the betas before the release.
If they invested 10% of the energy they waste complaining now to doing that trivial job, this "terrible mistake" would never happen...

[Gilletarom]

[QUOTE=nohal;3613501]There is no anomaly, translations are synchronized from Crowdin only before the releases.[/COTE]

Thank you. And sorry for insisting unnecessarily.

[COTE]You may perhaps suggest to the french users on HeO to help test the betas before the release.
If they invested 10% of the energy they waste complaining now to doing that trivial job, this "terrible mistake" would never happen...[/COTE]

You are attacking a typically French defect... I often think that we French people do not deserve the efforts made to improve "OpenCPN".

We have what we call "Une mentalité de consommateur". It's as if everything was due to us in advance.

"Une mentalité de consommateur" = "A consumer mentality" = "A consumer mindset"

[kevinvh]

Hi Dave,

Great job by you and the development team to get OpenCPN 5.6.2 out. I will put it through its paces over the next couple of days and let you know if I have any issues.

I am now in Fiji having sailed from Tahiti a few weeks ago. Fiji straddles the International Date Line or the Antimeridian and there is a definite problem with using the Weather Routing PI and Boundaries with WRs that cross the Antimeridian. I have 'Detect Boundary' turned on and 'Detect Land' turned off and the WR fails 'Invalid Start/End inside exclusion boundary' - the Start and End points are nowhere near a Boundary. Turning 'Detect Boundary' off and 'Detect Land' on, the WR computes but passes through land because of the poor mapping of the land profile.

This issue also occurred with OpenCPN 5.6.0 and 5.6.1, and it renders WR in Fiji as unusable and at best highly unreliable. A related issue which I reported on Flyspray #FS2615 back on 17/09/2019 has never been addressed - it still does not work across the Antimeridian.

MacBook Pro (15-inch, 2018)
2.6 GHz 6-Core Intel Core i7
16 GB 2400 MHz DDR4
Intel UHD Graphics 630 1536 MB
MacOS Monterey V12.3.1

[rgleason]

Originally Posted by kevinvh

Hi Dave,

Great job by you and the development team to get OpenCPN 5.6.2 out. I will put it through its paces over the next couple of days and let you know if I have any issues.

I am now in Fiji having sailed from Tahiti a few weeks ago. Fiji straddles the International Date Line or the Antimeridian and there is a definite problem with using the Weather Routing PI and Boundaries with WRs that cross the Antimeridian. I have 'Detect Boundary' turned on and 'Detect Land' turned off and the WR fails 'Invalid Start/End inside exclusion boundary' - the Start and End points are nowhere near a Boundary. Turning 'Detect Boundary' off and 'Detect Land' on, the WR computes but passes through land because of the poor mapping of the land profile.

This issue also occurred with OpenCPN 5.6.0 and 5.6.1, and it renders WR in Fiji as unusable and at best highly unreliable. A related issue which I reported on Flyspray #FS2615 back on 17/09/2019 has never been addressed - it still does not work across the Antimeridian.

MacBook Pro (15-inch, 2018)
2.6 GHz 6-Core Intel Core i7
16 GB 2400 MHz DDR4
Intel UHD Graphics 630 1536 MB
MacOS Monterey V12.3.1

Yes, Kevin is correct about this long term bug which he reported, and is reported in several other places:
https://github.com/rgleason/weather_...g_pi/issues/79
https://github.com/seandepagnier/wea..._pi/issues/256

Kevin, Sean does not seem to be inclined to fix this problem which has been identified and is repeatable. Bdbcat is very busy with OpenCPN main program and plugins are considered an incidental convenience. His efforts are primarily devoted to OpenCPN rather than 3rd party software.

What we really need, of course, is a small army of skillful C++ Plugin Programmers to help us with these PI problems. So please, if anyone is willing to help us, raise your hand. We would be most grateful.

[kevinvh]

Only wish I had some capability in C++ programming so I could help.

Here is a new problem with OpenCPN 5.6.2. Zooming in on a Boundary Point (or a Boundary), I am getting a strange video effect. See the screen shots.

Don't recall this happening with previous versions of OpenCPN.

[rgleason]

Originally Posted by kevinvh

Only wish I had some capability in C++ programming so I could help.

Here is a new problem with OpenCPN 5.6.2. Zooming in on a Boundary Point (or a Boundary), I am getting a strange video effect. See the screen shots.

Don't recall this happening with previous versions of OpenCPN.

Navionics? in grey background text? That is really strange. Are you using OpenGL? Thanks for reporting!

[kevinvh]

Originally Posted by rgleason

Navionics? in grey background text? That is really strange. Are you using OpenGL? Thanks for reporting!

Yes, using OpenGL. The Navionics charts are from SASPlanet, hence the Navionics watermark. But, it is the same result whether using CM93 or GE. Something has gone funny with OPCN Draw, I think.

[Ivanm]

Originally Posted by kevinvh

Only wish I had some capability in C++ programming so I could help.



Here is a new problem with OpenCPN 5.6.2. Zooming in on a Boundary Point (or a Boundary), I am getting a strange video effect. See the screen shots.



Don't recall this happening with previous versions of OpenCPN.

I also noticed that when zooming in on a boundry I get a strange colour which goes away when I zoom in even further it also removed the fill colour within the draw boundry points.

Ivan

[yachtvalhalla]

Unlike previously it is now not possible to select charts that are within a portable version of 5.6.2.

The selection directory only points to the chart located on the computer, not to the charts within the portable configuration.

The first image shows the selection possible in version 5.6.0.

The second image shows the selection possible in version 5.6.2.


Terry