[mkgmap-dev] mapnik TYP file changes

Wed Jan 22 19:21:47 GMT 2020

Hi Gerd

I haven't found anything that would do this, but, if someone does, it
would be very easy to change the default strings back to 0x04/English

Ticker

On Wed, 2020-01-22 at 13:41 +0000, Gerd Petermann wrote:
> Hi Ticker,
> 
> OK, I thought it would be possible to define something like "use
> build-in label" in the TYP file.
> If that is not the case the patch is an improvement.
> 
> Gerd
> 
> 
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
> Gesendet: Dienstag, 21. Januar 2020 11:43
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] mapnik TYP file changes
> 
> Hi Gerd
> 
> From experimenting with one of my Garmins (can't remember which one),
> if it couldn't find a label for the correct language, it just picked
> the first one in the label area for the object, regardless of the
> language. This seemed to be the first one textually in the file from
> the couple of cases I looked at.
> 
> If the object doesn't have any TYP labels, then my eTrex HCx shows
> the
> in-build English label, but the eTrex 30x doesn't show anything.
> 
> Ticker
> 
> On Tue, 2020-01-21 at 10:23 +0000, Gerd Petermann wrote:
> > Hi Ticker,
> > 
> > not sure if I like the idea of a default language using English.
> > What
> > happens when the device is set to e.g. Turkish? Doesn't Garmin
> > provide a good default string for "Lake" in Turkish?
> > 
> > Gerd
> > 
> > ________________________________________
> > Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> > von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
> > Gesendet: Dienstag, 21. Januar 2020 10:31
> > An: mkgmap development
> > Betreff: [mkgmap-dev] mapnik TYP file changes
> > 
> > Hi all
> > 
> > Patch attached that makes the following changes to mapnik.txt. This
> > is
> > held in resources/typ-files and distributed in examples/typ-files.
> > 
> > - Add UTF-8 BOM at the start of the file, so that many text editors
> > and
> > mkgmap will recognise the encoding.
> > 
> > - Add following line near start of file, for the same reasons:
> > ; -*- coding: UTF-8 -*-
> > 
> > - comment out lines in the [_id] section; these are supplied /
> > overridden by mkgmap -- options
> > 
> > - Change polygon 0x3d / "Bay" to be transparent, with a low
> > _drawOrder
> > 
> > - Add a default language label string to every entry. This is used
> > by
> > the Garmin device when there is no label for the language the
> > device
> > is
> > set to.
> > 
> > The basis on which I've set the default labels is roughly as
> > follows:
> > 
> > - Where my old Garmin device, without TYP file and for an unlabeled
> > object, gave a specific and unique label, used that.
> > 
> > - For other cases, eg where the standard Garmin label is something
> > like
> > Road, Line, Area or Unnamed, used wording relevant to the OSM tags
> > that
> > are being mapped.
> > 
> > - For some of the many Garmin Rivers and Lakes codes that we use
> > for
> > other water areas, again used wording related to the OSM tag.
> > 
> > - Where the English translation (language code 0x04) is close
> > enough
> > to
> > the default label, I've deleted the English. I've also deleted the
> > English where I think the label (probably in all languages) doesn't
> > reflect the tag for which it is being used, but the default label
> > does.
> > 
> > I've avoided making any changes to the visuals this TYP file
> > produces
> > (apart from Bay), or to any language other than English.
> > 
> > Ticker
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev