Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-24 Thread Michał Rogala
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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-24 Thread Steve Ratcliffe
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-24 Thread Michał Rogala
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-24 Thread Steve Ratcliffe
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-19 Thread Tomas Straupis
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-19 Thread Steve Ratcliffe
WanMil wmgc...@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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-19 Thread Johann Gail
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread Maks Vasilev
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread 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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread Rich
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread Felix Hartmann
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread Rich
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-18 Thread Michał Rogala
Hi! Replacing cp1250 with 1250 doesn't work - still the same problem. best regards Michal Rogala ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] broken charset in latest mkgmap

2011-03-15 Thread 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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-15 Thread Rich
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

Re: [mkgmap-dev] broken charset in latest mkgmap

2011-03-15 Thread Henning Scholland
You should try --code-page=1250 aighes ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev