Hi Ticker,

"and then doesn't
like various strings that can't be represented in that code page."

That brings me to the idea to look at "ä ö ü" in my typ file. When i kill this, it works better :)

Now, TYPViewer says only this:
Unbekannte CodePage-Nummer: 0
TYPViewer ersetzte die CodePage mit 1252

When i set the option --latin1 in mkgmap this message is gone. It seems, that mkgmap ignore the codepage line in the typ-file?

No matter, i know now, what to do, even tough i don´t understand why :)

Thank you for helping me!

Greets
Arndt



Ticker Berkin < rwb-mkgmap@jagit.co.uk> hat am 15. Februar 2020 um 12:00 geschrieben:


Hi

Is this using something based on resources/typ-files/mapnik.txt

My guessing of a translation of the error messages you are getting is
that TYPviewer defaults the output code-page to 1252 and then doesn't
like various strings that can't be represented in that code page.
Try uncommenting the line: CodePage=65001

Having this line will cause harmless warnings from mkgmap when you
generate a non-unicode map

Ticker

On Sat, 2020-02-15 at 08:44 +0100, Arndt Röhrig wrote:
Good morning,

i use TYPViewer for my typ files. This program reports some errors,
when i open a type file.

My typs are .txt files. So far they are ok. In a first step i use
mkgmap to create .typ files. It runs without error messages. The map
seems to be OK. But when i open a typ file with TYPViewer the error
messages appear. When i edit an element, TYPViewer pop up an error
message and close.

i guess the changes in r-4437 do that? Is there something wrong in my
typs?
For example the polygone 0x0e:

[_polygon]
Type=0x0e
;GRMN_TYPE: Large Manmade Areas/AIRPORT_RUNWAYS/Airport runway
area/Non NT
String1=0x02,Bürogewerbe
ExtendedLabels=Y
FontStyle=NoLabel (invisible)
CustomColor=No
Xpm="0 0 1 0"
"1 c #F2D9D8"
[end]

Greets

Arndt


P.S. The error message from TYPViewer:



*********************************************************************
*********************************************************************
************
Fehler in der Datei :
C:\ProgramData\GARMIN\Maps\Speiche_Fabrik_Gravel.gmap\Speiche.typ
*********************************************************************
*********************************************************************
************

Unbekannte CodePage-Nummer: 0
TYPViewer ersetzte die CodePage mit 1252
Wenn dies nicht paßt, wähle eine andere CodePage-Nummer in der
Auswahlbox "CodePage"
Problem beim Lesen der Strings des Polygons Type=0x004 SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x00e SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x010 SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x014 SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x01c SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x04e SubTypes =
0x00
Problem beim Lesen der Strings des Polygons Type=0x054 SubTypes =
0x00
Problem beim Lesen der Strings der Polylinie Type=0x015 SubTypes =
0x00
Problem beim Lesen der Strings des POI Type=0x001 SubTypes = 0x00

_______________________________________________
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