• Map Creation (where as you describe, the map language is important)
• TYP file compilation (where in my opinion the overruling possibility via option would make sense)

Hi

This was the thinking that lead to the previous change (in the example
I was woring with the CodePage was actually wrong).

But it doesn't really work except in a few cases.  For example if you
are Greek and have a greek typ file which is written in code-page
1253, then it must be written in that code page. If you are compiling
a map of Russia in code-page 1251, and that setting is applied to the
TYP file, then compiling the typ file will fail.

And this is normal, the typ file is meant to be in your own language,
not the language of the map that you are viewing.

So you either have to get the CodePage correct, or leave it out
altogether and then it will be taken from the command line. But
if it is taken from the command line then it will still fail if
you specify a code-page that is not compatible with the code
page that the typ is actually in.

..Steve

On 17/12/13 22:31, Patrik Brunner wrote:

This means that everyone needs to make everywhere sure that the correct
stuff is written inside the source file...

I really think it's the more convenient way to have:

 1. The CP taken from the source file is the the one 'normally' used
 2. CLI Argument 'overrules' the content of the TYP source file.

This is the way most of other products work: you're able to define
something inside a config file (or similar) CLI argument overrules it.

I have to admit that I didn't really go too deep into Henning's problem,
so may I missed something important... then I have to apologize.

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev