broken charset in latest mkgmap
Hello! I've just downloaded r1894 ( I've used some older release until today - i don't know which one). Recent changes in charsets broke CP1250 - instead of diacritic letters from polish language i get characters like dashes, pound symbols, etc. best regards Michal Rogala
On 03/15/11 18:56, Michał Rogala wrote:
Hello!
I've just downloaded r1894 ( I've used some older release until today - i don't know which one). Recent changes in charsets broke CP1250 - instead of diacritic letters from polish language i get characters like dashes, pound symbols, etc.
as was noted on the list, in latest versions of mkgmap codepage options should be used (probably :) ) have you tried that ?
best regards Michal Rogala -- Rich
2011/3/15 Rich <richlv@nakts.net>:
On 03/15/11 18:56, Michał Rogala wrote:
as was noted on the list, in latest versions of mkgmap codepage options should be used (probably :) ) have you tried that ?
I use: --charset=cp1250 --code-page=cp1250 r1867 works properly, r1893 doesn't best regards Michal Rogala
Hi! r1894 mkgmap parametrs: http://code.google.com/p/velo100mapper/source/browse/trunk/makemap.basic All text in map have broken charset. wbr, Maks В сообщении от 15 марта 2011 19:56:44 автор Michał Rogala написал:
Hello!
I've just downloaded r1894 ( I've used some older release until today - i don't know which one). Recent changes in charsets broke CP1250 - instead of diacritic letters from polish language i get characters like dashes, pound symbols, etc.
best regards Michal Rogala _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 18.03.2011 16:28, schrieb Maks Vasilev:
Hi!
r1894
mkgmap parametrs: http://code.google.com/p/velo100mapper/source/browse/trunk/makemap.basic
All text in map have broken charset. As written above: You should use --code-page=1250 instead of --charset=cp1250. As I remember also --lower-case shouldn't be used.
Henning
Should we print out a warning if someone still uses the options charset and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged. WanMil Am 18.03.2011 16:47, schrieb Henning Scholland:
Am 18.03.2011 16:28, schrieb Maks Vasilev:
Hi!
r1894
mkgmap parametrs: http://code.google.com/p/velo100mapper/source/browse/trunk/makemap.basic
All text in map have broken charset. As written above: You should use --code-page=1250 instead of --charset=cp1250. As I remember also --lower-case shouldn't be used.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 18.03.2011 19:29, WanMil wrote:
Should we print out a warning if someone still uses the options charset and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
WanMil
Am 18.03.2011 16:47, schrieb Henning Scholland:
that would probably be good. As well as removing lower-case as it does not work anyhow... (or noone could yet report it working).
On 03/18/11 20:42, Felix Hartmann wrote:
On 18.03.2011 19:29, WanMil wrote:
Should we print out a warning if someone still uses the options charset and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
WanMil
Am 18.03.2011 16:47, schrieb Henning Scholland:
that would probably be good. As well as removing lower-case as it does not work anyhow... (or noone could yet report it working).
lowercase works on etrex vista hcx for non-rotated text (so most labels and popups), doesn't work in rotated text) street labels note that it's just lowercase, not lowercase+diacritic (still haven't coerced the unit to display them properly. got a seriously messed up answer from garmin. considering writing a rant for /. ) -- Rich
On 18.03.2011 20:15, Rich wrote:
On 03/18/11 20:42, Felix Hartmann wrote:
On 18.03.2011 19:29, WanMil wrote:
Should we print out a warning if someone still uses the options charset and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
WanMil
Am 18.03.2011 16:47, schrieb Henning Scholland:
that would probably be good. As well as removing lower-case as it does not work anyhow... (or noone could yet report it working).
lowercase works on etrex vista hcx for non-rotated text (so most labels and popups), doesn't work in rotated text) street labels
note that it's just lowercase, not lowercase+diacritic (still haven't coerced the unit to display them properly. got a seriously messed up answer from garmin. considering writing a rant for /. ) Well then maybe it should be changed to not be used for street labels - not seen a single gps that supports it for street labels.
On 03/18/11 21:21, Felix Hartmann wrote:
On 18.03.2011 20:15, Rich wrote:
On 03/18/11 20:42, Felix Hartmann wrote:
On 18.03.2011 19:29, WanMil wrote:
Should we print out a warning if someone still uses the options charset and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
WanMil
Am 18.03.2011 16:47, schrieb Henning Scholland:
that would probably be good. As well as removing lower-case as it does not work anyhow... (or noone could yet report it working).
lowercase works on etrex vista hcx for non-rotated text (so most labels and popups), doesn't work in rotated text) street labels
note that it's just lowercase, not lowercase+diacritic (still haven't coerced the unit to display them properly. got a seriously messed up answer from garmin. considering writing a rant for /. ) Well then maybe it should be changed to not be used for street labels - not seen a single gps that supports it for street labels.
i'd suggest either leaving as is, or adding another option to skip it for street labels - when new units/firmware comes out, it might be useful to try whether they finally have decided to fix it -- Rich
Hi! Replacing cp1250 with 1250 doesn't work - still the same problem. best regards Michal Rogala
note that it's just lowercase, not lowercase+diacritic (still haven't coerced the unit to display them properly. got a seriously messed up answer from garmin. considering writing a rant for /. ) Well then maybe it should be changed to not be used for street labels - not seen a single gps that supports it for street labels.
Lower-case letters with Lithuanian characters do work on streets on Colorado. -- Tomas Straupis
WanMil <wmgcnfg@web.de> wrote:
Should we print out a warning if someone still uses the options charset
and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
I agree, and go further, I would like to through every option including the ones that Felix mentions from time and ask if it should exist, if the default should change or if it should be combined with others. Running mkgmap without any options at all should produce a reasonable map in most cases with options being for tweeks, adding information or dealing with difficult data ..Steve
Am 19.03.2011 13:36, schrieb Steve Ratcliffe:
Should we print out a warning if someone still uses the options charset
and/or lower-case? Or should we remove these options? This seems to be a common pitfall since the index branch has been merged.
I agree, and go further, I would like to through every option including the ones that Felix mentions from time and ask if it should exist, if the default should change or if it should be combined with others.
Running mkgmap without any options at all should produce a reasonable map in most cases with options being for tweeks, adding information or dealing with difficult data
As this themes are discussed now at the mailing list, I have another suggestion with the options. I would like the options beeing embedded in the options file in the styles. There they belongs to. Then it would be possible to set e.g. the dpfilter settings and the min polygon size for a cycle map to other values than for a street map. In the default style could reasonable default settings be set. Regards, Johann
Hi! Do you have any clue what has changed between latest versions that 1250 code-page doesn't work? I've tried the latest release and still the same problem. best regards Michal Rogala
Hello
Do you have any clue what has changed between latest versions that 1250 code-page doesn't work? I've tried the latest release and still the same problem.
Are you using --code-page=1250 ? Do not use --charset at all. If you are doing that, then please upload a tile that doesn't work (you can use http://files.mkgmap.org.uk/) I don't see any difference in the label encoding between the two versions. I don't have the 1250 character set, so I don't see the proper characters, but that's what I would expect. Thanks ..Steve
Thanks, without --charset everything works great!. I have just one more question - without --charset parameter - default is latin1. With latin1 all street names are lowercase but with --code-page=1250 all names are uppercase (in MapSource). Why there is such difference? best regards Michal Rogala 2011/3/24 Steve Ratcliffe <steve@parabola.me.uk>:
Hello
Do you have any clue what has changed between latest versions that 1250 code-page doesn't work? I've tried the latest release and still the same problem.
Are you using --code-page=1250 ?
Do not use --charset at all.
If you are doing that, then please upload a tile that doesn't work (you can use http://files.mkgmap.org.uk/)
I don't see any difference in the label encoding between the two versions. I don't have the 1250 character set, so I don't see the proper characters, but that's what I would expect.
Thanks
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi
I have just one more question - without --charset parameter - default is latin1. With latin1 all street names are lowercase but with --code-page=1250 all names are uppercase (in MapSource). Why there is such difference?
I don't know. Are you using --lower-case? If so, don't :) If you are not, then it must be something to do with mapsource unless I'm missing something. The --lower-case option was added just to show that it doesn't work! As such no work has been done on it to deal with different character sets and I have no idea what will happen in any particular case without looking at the code. ..Steve
participants (9)
-
Felix Hartmann -
Henning Scholland -
Johann Gail -
Maks Vasilev -
Michał Rogala -
Rich -
Steve Ratcliffe -
Tomas Straupis -
WanMil