Steve, This means that everyone needs to make everywhere sure that the correct stuff is written inside the source file... I really think it's the more convenient way to have: 1. The CP taken from the source file is the the one 'normally' used 2. CLI Argument 'overrules' the content of the TYP source file. This is the way most of other products work: you're able to define something inside a config file (or similar) CLI argument overrules it. I have to admit that I didn't really go too deep into Henning's problem, so may I missed something important... then I have to apologize. Cheers Patrik On 17.12.2013 23:26, Steve Ratcliffe wrote:
Hi Henning
OK, I will stop the command line overriding the declared CodePage in the .txt file.
It seems like it is likely more often the wrong thing to do. If anyone believes that there is a remaining problem then we will have to find another way to fix that problem.
..Steve
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Steve,
I don't want to bother you. Is there any news about this?
Henning
Am 25.11.2013 00:17, schrieb Steve Ratcliffe:
Hi Henning
in the end of August it worked without any problems. I've just read here that something was changed with TYP-files and code-page.
The change was that the --code-page parameter overrides the CodePage that is in the typ txt file. That may well have been a bad idea. It certainly is in this case.
Previously you would have had a cp1252 TYP file with the tiles being in a different code page (unless you changed the CodePage in the typ txt file too).
You should be able to work around the problem by using --code-page=1252 just before the .txt file and then setting it back to what it should be just after.
I am tempted to revert that part of the change, but will have to look at why I made it in the first place.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32)
iQEcBAEBAgAGBQJSsJ2XAAoJEPFgsWC7jOeTg3QIAJWqJCMiGWA86DokRgGBnyWb SIexcvljpJkBitRpZ3uMauijs9vOUOvLIBZanB6dofSh0ef8kU9LUkrkBWx0ctqg zd/534wZq7w3piKBp8m+1MBlp5zRWoOdZArnov8dleShn2ol5Gj9bOdm0rA45Pn+ At5vQOevMpdW3VvXYjw1wmFpBbrgwaYvS3P6DvY/7osJkNjPp9IqQbU9rY3qlqB2 Cmv0oc+i0Juzki+j/L198UZNEd83SaYbHcydeB4fpvqZU4uqhgZbjjb8C7IH0skC nu8YwEeSmQ20no+b4Nu0Pse5u3eLM8J+gIKiFLAtPOidNh11UxLw2hYIzQYlrBY= =eEK3 -----END PGP SIGNATURE-----
_______________________________________________ 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