TYP-file can't be written
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, just another problem: I got the message from mkgmap, that the TYP-file can't be written in CP1251 and CP1256. In the header of my txt-TYP-source I have written CP1252. Converting this to CP1250 and CP1254 is done without problems. So I don't understand, why it's a problem for CP1251 and CP1256. Any guesses? Henning -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBAgAGBQJSkShZAAoJEPFgsWC7jOeT/iwIAJM9g29e/69wwIer17x54nC6 u5zwjnZzIEV7vRIfmTHCe6ucFCLHjG+MDtTAq5vZVtDOQUTcvmXUYbF6AAkiXpsd tHp1UXyqcbKy6mQSY0HQkRRzRWqOyJpnQxKe76S4PI6BrARCXm4Rr+UpXLlkXQKe 2F1VELgTZoQ4MR1k4CwNdvuvxeTtMbCLloPBUIoIktutyOLKI+8gonQkiniuSSM0 7cDESCwXiJlS1SGNg7I3rGoHsBpmbceqd+8DZaFnpxnez2bHrnirp0c2hIo3x27N bSLnPSSaJO5ES7mEQkMHcXOFFNHQDee6znHuJmpyCwhzRXSdyUDVSYrsGesjxJg= =v9L8 -----END PGP SIGNATURE-----
On 23/11/13 22:12, Henning Scholland wrote:
In the header of my txt-TYP-source I have written CP1252. Converting this to CP1250 and CP1254 is done without problems. So I don't understand, why it's a problem for CP1251 and CP1256. Any guesses?
I will need a few more details if you think there is a bug and you think that the labels could be written in CP1251 and 56. But in general there is no transliteration, so the characters you use must be in the target character set. cp1250 and cp1254 share many of the common characters from cp1252 that you are likely to be using and so might work, whereas 1251 and 1256 are very different and may not contain the characters you are using. ..Steve
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Steve, 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. My TYP-file you'll find here: https://github.com/aighes/RadReiseKarte/blob/master/resources/rrk_typ.txt It's containing ö,ü,ä and ß. Henning Am 24.11.2013 15:01, schrieb Steve Ratcliffe:
On 23/11/13 22:12, Henning Scholland wrote:
In the header of my txt-TYP-source I have written CP1252. Converting this to CP1250 and CP1254 is done without problems. So I don't understand, why it's a problem for CP1251 and CP1256. Any guesses?
I will need a few more details if you think there is a bug and you think that the labels could be written in CP1251 and 56.
But in general there is no transliteration, so the characters you use must be in the target character set.
cp1250 and cp1254 share many of the common characters from cp1252 that you are likely to be using and so might work, whereas 1251 and 1256 are very different and may not contain the characters you are using.
..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 v1.4.14 (GNU/Linux) iQEcBAEBAgAGBQJSkg7qAAoJEPFgsWC7jOeTCDoH/RY05Dukbx2/JCLCPpg57Zph wReqNpeJPTnd5doboxmIOa6NJGtlS7AkMKA/2pmM6Rl5CbFcYQQQ9ZEl3eZ5uWLh pKm33R3yGZE6xGvbX3BKnPQ1Map2o79chzwNj6pgu8a/admXtm/z1umyuRJu5jvz C7V5606ffLOxp0/OH37eZYdUoUVgeT2iry8Vmm9E3Skr+hNTi08QZPRA6t3w++fz U/W9NWc9EEU7foWiCoyWZtI5wprUI6CYbnXk699SEjzMhUvyyxPtxjfC2E9pmFZd 36L99tLUPEdOo8TyEFQt9Xe8yNMnzyUyqmbWetUQDihYLvMF0oy0XyOS7ACx3iw= =yB0C -----END PGP SIGNATURE-----
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
-----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-----
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
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
Hi This was the thinking that lead to the previous change (in the example I was woring with the CodePage was actually wrong). But it doesn't really work except in a few cases. For example if you are Greek and have a greek typ file which is written in code-page 1253, then it must be written in that code page. If you are compiling a map of Russia in code-page 1251, and that setting is applied to the TYP file, then compiling the typ file will fail. And this is normal, the typ file is meant to be in your own language, not the language of the map that you are viewing. So you either have to get the CodePage correct, or leave it out altogether and then it will be taken from the command line. But if it is taken from the command line then it will still fail if you specify a code-page that is not compatible with the code page that the typ is actually in. ..Steve On 17/12/13 22:31, Patrik Brunner wrote:
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.
ok, thanks Steve .... got the point (more or less, I think)... The problem is, I think, that we're using mkgmap for different things. * Map Creation (where as you describe, the map language is important) * TYP file compilation (where in my opinion the overruling possibility via option would make sense) In addition to that we're able to run both tasks in one go.... which then may lead into troubles... The initial change was focusing on the TYP file compilation... and therefore raises some issues 'at the other end' Cheers Patrik On 18.12.2013 11:48, Steve Ratcliffe wrote:
Hi
This was the thinking that lead to the previous change (in the example I was woring with the CodePage was actually wrong).
But it doesn't really work except in a few cases. For example if you are Greek and have a greek typ file which is written in code-page 1253, then it must be written in that code page. If you are compiling a map of Russia in code-page 1251, and that setting is applied to the TYP file, then compiling the typ file will fail.
And this is normal, the typ file is meant to be in your own language, not the language of the map that you are viewing.
So you either have to get the CodePage correct, or leave it out altogether and then it will be taken from the command line. But if it is taken from the command line then it will still fail if you specify a code-page that is not compatible with the code page that the typ is actually in.
..Steve
On 17/12/13 22:31, Patrik Brunner wrote:
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.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Patrik, the problem is, that we could have two code_pages in one map. In TYP-File we have the default names of objects (which should be in the language of the user/map creator) and the maptiles which should display the names used on the ground. There we'll need the posibility to set these to code pages separatly. How this is done we could think about. Henning
Henning, think it's clear now.... my perspective (and the one the initial 'fix' was based on) was mainly TYP file compiler biased.... obviously the other aspect about different codepages in map was overlooked. It would be a possibility to handle the map CP and the TYP CP with different arguments.... but I'm not sure if the effort is worth it and I'm even less sure if we miss again something... ;-) Thanks for the additional explications. Patrik On 18.12.2013 12:43, osm@aighes.de wrote:
Hi Patrik,
the problem is, that we could have two code_pages in one map. In TYP-File we have the default names of objects (which should be in the language of the user/map creator) and the maptiles which should display the names used on the ground.
There we'll need the posibility to set these to code pages separatly. How this is done we could think about.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Henning Scholland -
osm＠aighes.de
-
Patrik Brunner -
Steve Ratcliffe