Steve,
I guess I was definitely using the wrong version.... I was,
instead of pointing to mkgmap.jar, using hardcoded patched version
with different name in the same directory... sorry for that, was a
bit too quick with the tests.... with the good intention of
providing quick feedback...
Latest Results (with the correct version now):
I was building unicode and cp1252 map and they look both allright
(license and copyright wise) when checking the gmap (created via
jmc_cli, not mkgmap) in Basecamp and gmapsupp (created with
mkgmap) on the device itself (checked Oregon 450t only, right
now).
The gmapsupp version looks also good when connected to the PC and
checked via BaseCamp.
If I install the images directly via Registry it also looks
perfect in BaseCamp.
In short: All looks fine right now, I could not
find/create/produce any strange behaviours...
I have to clean up the map build environment a bit, as few changes
where implemented to prevent problems...
As soon as I have everything in shape again I'll do final tests on
Windows and Linux (just to make sure all is fine there also,
allthough I do not expect any new problems due to calling it
always with UTF-8 env).
As it looks right now: I would guess, that you solved the
issues.... great.
Many thanks...
I'll let you know latest test results in a few days.
Thanks and regards
Patrik
Steve,Thanks.I'm checking at the same location in BaseCamp...Following things can/have to be mentioned:
- I'm calling java with the option file-encoding=utf8 (or similar, can't remember by heart), this means, mkgmap is started also in utf8 environment, independant if it's run on windows or linux (tests are done on windows actually)... and the source file for the license and copyright options are properly utf8 encoded.... all will be confirmed again
- I quite sure I've used the correct version, freshly compiled and moved to the correct directory.... but for sure I'll double check again.... should reflect the correct release number already ? Same as in the svn commit ? How can I else check ?
- I did NOT install the img files via registry, I've used a converted GMAP Archive..... converted by jmc_cli (JaVaWa), not yet converted by mkgmap.
But I will definitely go down this route also and do the Map installation via registry, to prevent any additional potential conversion issuesI will do the additional testing/confirmations latest this evening.CheersPatrikGesendet: Montag, 12. Dezember 2016 um 23:43 Uhr
Von: "Steve Ratcliffe" <steve@parabola.me.uk>
An: "Development list for mkgmap" <mkgmap-dev@lists.mkgmap.org.uk>
Betreff: Re: [mkgmap-dev] mkgmap: problems with encoding file used with option --license-file
Hi
> (c) Map: FZK project ￃﾤￃﾶￃﾼￃﾩￃﾨￃﾪ (free for research and private use)
That looks like the result from an earlier version which kind
of double encoded the licence file. It didn't actually look
like that in BaseCamp to me however.
Just to check I am looking under Maps->Manage map products->copyright
there may be something else I've missed.
Your original problem implied that your system encoding is not utf-8
so maybe that is the problem. I don't know how to change that so
I can't try it.
I am installing the map via the registry, not loading a gmapsupp.
..Steve
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev