Re: [mkgmap-dev] errors in typ file
Hi Arndt There should be no need to delete äöü if you use the --latin1 or --code-page=1252 option to mkgmap Ticker On Sat, 2020-02-15 at 14:31 +0100, Arndt Röhrig wrote: > Hi Ticker, > > now all is OK. I delete äöü in the typ/txt files and give mkgmap the > option --latin1. > > Thank you! > > > Greets > > Arndt > > Ticker Berkin < rwb-mkg...@jagit.co.uk> hat am 15. Februar 2020 um > > 14:03 geschrieben: > > > > > > Hi Arndt > > > > Looking back at the first posting, the messages seem to be from > > TYPViewer on the .typ file rather than the .txt file. > > > > What codepage are your TYP .txt files written in? It looks like > > 1252. > > How did you generate the .typ from the .txt? If mkgmap, what > > command > > line --code-page did you have? (or --charset). When using mkgmap to > > convert .txt to .typ, the --code-page overrides any CodePage= line > > in > > the .txt file. > > > > It is possible that this is where there has been a change. No - > > -code > > -page specified to mkgmap defaults the map.img to ascii/cp0 I > > think, > > but maybe the typ file used to default to its value of 'CodePage', > > but > > now uses the mkgmap value. > > > > The messages TYPview is giving could be because it considers the > > code > > -page to be 7-bit ASCII but it is finding strings with the top bit > > set. > > > > This all seems to fit when what you've just said. When using mkgmap > > to > > convert your .txt, use the same --code-page as you will for your > > final > > maps. > > > > Ticker > > > > On Sat, 2020-02-15 at 13:10 +0100, Arndt Röhrig wrote: > > > 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-mkg...@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
Re: [mkgmap-dev] errors in typ file
Hi Ticker, now all is OK. I delete äöü in the typ/txt files and give mkgmap the option --latin1. Thank you! Greets Arndt Ticker Berkin < rwb-mkg...@jagit.co.uk> hat am 15. Februar 2020 um 14:03 geschrieben: Hi Arndt Looking back at the first posting, the messages seem to be from TYPViewer on the .typ file rather than the .txt file. What codepage are your TYP .txt files written in? It looks like 1252. How did you generate the .typ from the .txt? If mkgmap, what command line --code-page did you have? (or --charset). When using mkgmap to convert .txt to .typ, the --code-page overrides any CodePage= line in the .txt file. It is possible that this is where there has been a change. No --code -page specified to mkgmap defaults the map.img to ascii/cp0 I think, but maybe the typ file used to default to its value of 'CodePage', but now uses the mkgmap value. The messages TYPview is giving could be because it considers the code -page to be 7-bit ASCII but it is finding strings with the top bit set. This all seems to fit when what you've just said. When using mkgmap to convert your .txt, use the same --code-page as you will for your final maps. Ticker On Sat, 2020-02-15 at 13:10 +0100, Arndt Röhrig wrote: 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-mkg...@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
Re: [mkgmap-dev] errors in typ file
Hi Arndt Looking back at the first posting, the messages seem to be from TYPViewer on the .typ file rather than the .txt file. What codepage are your TYP .txt files written in? It looks like 1252. How did you generate the .typ from the .txt? If mkgmap, what command line --code-page did you have? (or --charset). When using mkgmap to convert .txt to .typ, the --code-page overrides any CodePage= line in the .txt file. It is possible that this is where there has been a change. No --code -page specified to mkgmap defaults the map.img to ascii/cp0 I think, but maybe the typ file used to default to its value of 'CodePage', but now uses the mkgmap value. The messages TYPview is giving could be because it considers the code -page to be 7-bit ASCII but it is finding strings with the top bit set. This all seems to fit when what you've just said. When using mkgmap to convert your .txt, use the same --code-page as you will for your final maps. Ticker On Sat, 2020-02-15 at 13:10 +0100, Arndt Röhrig wrote: > 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-mkg...@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 > >
Re: [mkgmap-dev] errors in typ file
Hi I have the same values in my stylefile ;generated by TYPWiz 5,971 ;created : 02-28-2019 ;-- [_id] ... [_polygon] Type=0x3d ExtendedLabels=N String1=0x02,Bucht String2=0x04,Bay FontStyle=NoLabel (invisible) Xpm="32 32 2 1" "0 c none" "1 c #B4" ... Bernd Am Samstag, 15. Februar 2020, 09:50:46 CET schrieb Arndt Röhrig: > Hi Nick, > > > TYPViewer write this, when i choose "NoLabel". It was ok until r-4437. > > > Greets > Arndt > Pinns UK < o...@pinns.co.uk> hat am 15. Februar 2020 um 09:34 geschrieben: > > > > > Hi Arndt > > > I suspect it's > > > FontStyle=NoLabel (invisible) > > > which should be > > > FontStyle=NoLabel > > > Regards > > > Nick > > > On 15/02/2020 07:44, Arndt Röhrig wrote: > FontStyle=NoLabel (invisible) > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev signature.asc Description: This is a digitally signed message part. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in typ file
Hi all but we shouldn't blame TypWiz I made some changes with a text editor on waterpolygons a few weeks ago after my last changes with TypWiz There was a discussion in this ML with waterpolygons in bays, maybe i/we made a C error? Bernd Am Samstag, 15. Februar 2020, 09:50:46 CET schrieb Arndt Röhrig: > Hi Nick, > > > TYPViewer write this, when i choose "NoLabel". It was ok until r-4437. > > > Greets > Arndt > Pinns UK < o...@pinns.co.uk> hat am 15. Februar 2020 um 09:34 geschrieben: > > > > > Hi Arndt > > > I suspect it's > > > FontStyle=NoLabel (invisible) > > > which should be > > > FontStyle=NoLabel > > > Regards > > > Nick > > > On 15/02/2020 07:44, Arndt Röhrig wrote: > FontStyle=NoLabel (invisible) > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev signature.asc Description: This is a digitally signed message part. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in typ file
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-mkg...@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 ___
Re: [mkgmap-dev] errors in typ file
Hi Ticker, with CodePage=65001 mkgmap will not build a typ file. SCHWERWIEGEND (MapFailedException): .\Daten\Speiche_schmal.txt: (thrown in TypCompiler.makeMap()) Compiling TYP txt file: Error: (.\Daten\Speiche_schmal.txt:3): Bad character in input, file probably not in UTF-8 When i convert the .txt file to UTF-8 it works, but when i open the typfile with TYPViewer, codepage is set to 1252 and the same error messages appaer. I try --code-page=65001 as a option with mkgmap and as a line in the typfile. I can open the .txt wit TYPViewer without errors. When i convert the .txt to .typ with TYPViewer all is OK. Converting the .txt to .typ with mkgmap r-4428 its OK too. Something happend since r-4437, so that the TYP is incompatible to TYPViewer. BaseCamp and my Oregon600 have no problems with the typ. Greets Arndt Ticker Berkin < rwb-mkg...@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 ___
Re: [mkgmap-dev] errors in typ file
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
Re: [mkgmap-dev] errors in typ file
Hi Nick, TYPViewer write this, when i choose "NoLabel". It was ok until r-4437. Greets Arndt Pinns UK < o...@pinns.co.uk> hat am 15. Februar 2020 um 09:34 geschrieben: Hi Arndt I suspect it's FontStyle=NoLabel (invisible) which should be FontStyle=NoLabel Regards Nick On 15/02/2020 07:44, Arndt Röhrig wrote: FontStyle=NoLabel (invisible) ___ 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
Re: [mkgmap-dev] errors in typ file
Hi Arndt I suspect it's FontStyle=NoLabel (invisible) which should be FontStyle=NoLabel Regards Nick On 15/02/2020 07:44, Arndt Röhrig wrote: FontStyle=NoLabel (invisible) ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] errors in typ file
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
