If I read this -> GNU `gettext' utilities, right there ought to be a way to solve this with gettext.
Other languages may have similar problems, but with different words, so it could come in handy.
...um yeah, but we use wxW, not really sure how that applies to our code??
...um yeah, but we use wxW, not really sure how that applies to our code??
It seems that wx is compatible with gettext in many respects, hence my suggestion to look into if it was possible to include context sensitive strings.
After some digging, I have to conclude that it's not possible - for the moment.
From the wxwidgets Roadmap for V 3.0:
Quote:
Nice To Have
It would be nice to have a lot of other things for this release but we don't have currently any possibility to work on the following. Please let us know if you can help with any of these:
Support for context-sensitive translations in wxLocale
I am using OpenCpn 3.1.1105 in Windows 7 , Charts S-57 and CM93 as well. Unfortunately I am having regular crashes upon moving the screen with the mouse. Could you tell me what cause this, it does not crashes with other programs.
Best Regards.
Did anyoe had a look at the tidal curves for Dec 31st? Check the peculiar things between 19 an 21 hundred hours. I have an error of 2 hours for the tide predictions, leading to all erroneous predictions. What cause this in OpeCpn? The same file use in Wtides give the correct results. I am i zone EST (5h).
Regards
P_Dub
Did anyoe had a look at the tidal curves for Dec 31st? Check the peculiar things between 19 an 21 hundred hours. I have an error of 2 hours for the tide predictions, leading to all erroneous predictions. What cause this in OpeCpn? The same file use in Wtides give the correct results. I am i zone EST (5h).
Regards
P_Dub
Yes, there is something fishy going on at the end of Dec 31st '12
Also, the tides are shifted back on time on Jan 1st '13 relative to Dec 31st '12 which cannot be correct, as High and Low tides occur later every day.
It seems to me that you are jumping from 2012 to 2014. Please check if that is correct. ( Time errors between 18:00 and 21:00 EST or 23:00 and
01:00 GMT december 31st).
Bye
Curiouser and curiouser...using the Wxtides tcd file in O screws up but Wxtide does fine (per the official Canadian tidebook) so what could O be doing?
(compare to lower right for December 31 in tidebook)
O does a blending of tide/current coefficients at the new year transition. This is required due to the organization of the constituent data as by epoch (year).
Obviously not well tested until now. I'll have a look at it, at low priority.
Dave Good Morning.
May I suggest you to make it a high priority for your next beta version as the end of the month is coming faster than one may think!
There seems to be 17 days of difference or a year or somethig like it and it is in the coding for what a programmer told me.
Bye
Sorry to disagree, Dave... Imagine how the annoucement that the tidal data is known to be incorrect in a stable release, and that this is a minor issue, would be received in some areas...
I'd have to recommend in conscience NOT to download it !
The error does propagate all year long
Look at the difference one month later !!!
First pic is 3.0.2, data agrees with all predictions I could find (e.g. pic 3)
Second pic is 3.1.1105 and is way off
SailorF54
If this was a stable release I would support you 110%.
But ... we are talking about a beta test release, with a handful of other issues, that is certainly not ready for prime time.
The way things are, I would not recommend anyone, except perhaps a seasoned beta tester , to use this or, even the next beta, for actual navigation.
Or ... have I totally misunderstood you?
So now you know that only the last 3.1.1105 has a problem. It should not be too difficult to locate the problem and correct it. I brought this as a positive comment observe in lookig ahead of times.
Best Regards
P_Dub
, to use this or, even the next beta, for actual 
Linear Mode
Recent Discussions