Re: [mkgmap-dev] --transpatent not work

But you could rightfully complain that mkgmap silently ignores unknown command line switches. As far as I understand, the problem is that there is no centralized command line parsing. Each code snippet looks for its own magic parameter among all command line options. One thing that could be done is to set a flag whenever an option gets processed. Then, at the end of the run, mkgmap could list the ignored options.

Have a look at the command line parsing stuff I added to the splitter, it makes it pretty easy to validate and document the params. Maybe a similar approach could be used in mkgmap? Chris