Commit: r832: Use the cp1252 code page for reading .mp files.
Version 832 was commited by steve on 2009-01-11 14:54:38 +0000 (Sun, 11 Jan 2009) Use the cp1252 code page for reading .mp files. Recognise the CodePage option in a .mp file. This doesn't currently work as the file is already open with the default charset.
Today I've found a comment on http://wiki.openstreetmap.org/wiki/Talk:Mkgmap/routing#.C3.A4.C3.B6.C3.BC.C3... If I understand it correctly, then osm2mp can output utf8-coded mp-files. So I would suggest to change the standard codepage for opening a mp file to utf8, as this includes all possible unicode characters. At least should mkgmap print out a warning to the console, if the assumed codepage differs from the codepage option given at the keyword inside the mp file.
Version 832 was commited by steve on 2009-01-11 14:54:38 +0000 (Sun, 11 Jan 2009)
Use the cp1252 code page for reading .mp files. Recognise the CodePage option in a .mp file. This doesn't currently work as the file is already open with the default charset. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev .
On Thu, Jan 22, 2009 at 10:45:11PM +0100, Johann Gail wrote:
If I understand it correctly, then osm2mp can output utf8-coded mp-files. So I would suggest to change the standard codepage for opening a mp file to utf8, as this includes all possible unicode characters.
When it does that it leaves a confusing CodePage=1251 directive in. It might be useable if that could be changed. I believe that I have now fixed mkgmap to deal with the CodePage directive properly. ..Steve
participants (3)
-
Johann Gail -
Steve Ratcliffe -
svn commit