[mkgmap-dev] The x prepended to the *.typ file

Sun Sep 19 12:30:10 BST 2021

Hi Ticker,

please explain why mkgmap is "stuck" with the fixed version. What's the difference between a fixed *.typ file and one that is freshly compiled from *.txt?

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Sonntag, 19. September 2021 13:25
An: Development list for mkgmap; Steve Ratcliffe
Betreff: Re: [mkgmap-dev] The x prepended to the *.typ file

Hi

If you don't use --output_dir but have map sources (.osm.pbf) and
results (.img) all in the same place, and you specify a pre-built
TYPfile with extension .typ, but it has the wrong family/product,
mkgmap can adjust these, but is then stuck as to what to do with the
fixed version, hence the "x" prefix to deal with this case.

If --output-dir is specified and the .typ file wasn't in that when
specified as an input parameter, then could avoid the rename.

This doesn't effect me as I always use mkgmap to generate the .typ from
the .txt as part of the final map generation process.

Ticker

On Sun, 2021-09-19 at 10:22 +0000, Gerd Petermann wrote:
> Hi all,
>
> I think there is an old rather confusing glitch in mkgmap class
> TypSaver which it is used with a *.typ file as input, as in
> java -jar mkgmap.jar --output-dir=<map-folder> --family-id=4711 ...
> -c splitter-dir\template.args ..\typfiles\existing.typ
> to make sure that family-id and product-id are correctly updated in
> the *.typ file.
> Since 2012 the program creates / overwrites a copy of file
> existing.typ in the source(!) directory ..\typfiles with the prefix
> "x", so ..\typfiles\xexisting.typ is written instead of
> <map-folder>\existing.typ. I can't find it now but I think there were
> complains that this name doesn't fit the 8+3 rule for old file
> systems and causes trouble on some devices.
>
> I think when Steve coded this he expected that the *.typ file is in
> the output directory, not somewhere else. My conclusions:
> - I think it is an error to create the copy in the source directory.
> - I see no reason to create a copy with the prepended "x", I would
> just create or alter the file in the given output directory.
>
> @Steve: What case am I missing? What's the reason for the different
> name in the copy?
> @all: Does anybody rely on this behaviour?
>
> Gerd
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev