Hi list,
I prepared a diff against r1657 which implements an --output-dir option
for mkgmap. According to the tests I've made, mkmap does not change its
behaviour if this option is left alone.
However, the diff is rather ugly, since file write operations are
scattered over a number of classes.
Hi Clinton!
Hm... with my Geofabrik extract and Mkgmap 1652 I get the following:
Rablstrasse 45
81669, München, DE, DE
Which, aside from the DE, DE part, seems to be correct. I'll try updating
mkgmap and recompiling to see if that makes a difference.
If it does not make a difference,
Hi Markus,
I'm aware that this might be my view on the issue only. I just feel in a
project like this one, where the developer count is low, a solution (or an
approach thereof) in code is way quicker than involving developers
unnecessarily.
I try to contribute in other ways, e.g. I
I do not think so. It is a very strange bug. It changes for example
even, if the osm file, the styles, the mkgmap etc. remain the same and
just the typ file is changed.
That kind of points to the problem being in the TYP file - mkgmap
doesn't really do anything to modify
the TYP file, or
Hi
Thanks this option would be useful.
However, the diff is rather ugly, since file write operations are
scattered over a number of classes. Thus the code prepending the pathname
is equally scattered.
I think it would be better to define a method on CommandArgs called
getOutputPath(String
On Jul 19, 2010, at 20:02, Daniela Duerbeck wrote:
Hi Clinton!
Hm... with my Geofabrik extract and Mkgmap 1652 I get the following:
Rablstrasse 45
81669, München, DE, DE
Which, aside from the DE, DE part, seems to be correct. I'll try updating
mkgmap and recompiling to see if that
Hello
I dont know if this has been raised before but even mkgmap-1655 could
not produce an .IMG with proper Japanese character encoding.
Do you have a Garmin unit that displays Japanese characters? It would
be great to get this working, but I've never had any way of testing it.
I see the
Steve Ratcliffe wrote:
I do not think so. It is a very strange bug. It changes for example
even, if the osm file, the styles, the mkgmap etc. remain the same and
just the typ file is changed.
That kind of points to the problem being in the TYP file - mkgmap
doesn't really do
Sorry I don't have a Japanese Garmin to test with. I was just using GPSMapEdit
on English Windows with Japanese fonts installed.
Maybe we shouldn't check the code in until it's verified to work on Garmin
devices.
Cheers
From: Steve Ratcliffe
