<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
ok, thanks Steve<br>
.... got the point (more or less, I think)...<br>
<br>
The problem is, I think, that we're using mkgmap for different
things.<br>
<ul>
<li>Map Creation (where as you describe, the map language is
important)</li>
<li>TYP file compilation (where in my opinion the overruling
possibility via option would make sense)</li>
</ul>
In addition to that we're able to run both tasks in one go.... which
then may lead into troubles...<br>
<br>
The initial change was focusing on the TYP file compilation... and
therefore raises some issues 'at the other end'<br>
<br>
Cheers<br>
Patrik<br>
<br>
<div class="moz-cite-prefix">On 18.12.2013 11:48, Steve Ratcliffe
wrote:<br>
</div>
<blockquote cite="mid:52B17D94.400@parabola.me.uk" type="cite">
<br>
Hi
<br>
<br>
This was the thinking that lead to the previous change (in the
example
<br>
I was woring with the CodePage was actually wrong).
<br>
<br>
But it doesn't really work except in a few cases. For example if
you
<br>
are Greek and have a greek typ file which is written in code-page
<br>
1253, then it must be written in that code page. If you are
compiling
<br>
a map of Russia in code-page 1251, and that setting is applied to
the
<br>
TYP file, then compiling the typ file will fail.
<br>
<br>
And this is normal, the typ file is meant to be in your own
language,
<br>
not the language of the map that you are viewing.
<br>
<br>
So you either have to get the CodePage correct, or leave it out
<br>
altogether and then it will be taken from the command line. But
<br>
if it is taken from the command line then it will still fail if
<br>
you specify a code-page that is not compatible with the code
<br>
page that the typ is actually in.
<br>
<br>
..Steve
<br>
<br>
On 17/12/13 22:31, Patrik Brunner wrote:
<br>
<blockquote type="cite">This means that everyone needs to make
everywhere sure that the correct
<br>
stuff is written inside the source file...
<br>
<br>
I really think it's the more convenient way to have:
<br>
<br>
1. The CP taken from the source file is the the one 'normally'
used
<br>
2. CLI Argument 'overrules' the content of the TYP source file.
<br>
<br>
This is the way most of other products work: you're able to
define
<br>
something inside a config file (or similar) CLI argument
overrules it.
<br>
<br>
I have to admit that I didn't really go too deep into Henning's
problem,
<br>
so may I missed something important... then I have to apologize.
<br>
</blockquote>
<br>
_______________________________________________
<br>
mkgmap-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
<br>
</blockquote>
<br>
</body>
</html>