Am I doing something wrong? name:int!=* & name=* {set name='${name|ascii:} ${name}' However for Syria or Greece I don't see any change. Is my command wrong, or is there maybe a bug in the patch?... On 11.08.2014 23:26, Steve Ratcliffe wrote:
Hi Felix
Could there be a command like {set name='${mkgmap:trans:name}' } That way one could build a map that is usable for people who do understand the local script/language, and who don't by setting all names e.g. name=('name:en|name:int|mkgmap:trans:name''(name in e.g. Japanese Script) '
A quick patch attached which is a first attempt at such a thing.
Usage:
${name|ascii:} ${name|latin1:}
You need the colon there at the moment, but I will fix that if we go with this syntax. An alternative syntax could be: ${name|transliterate:ascii}
Even better would of course be if there would be an additional function to check if "name" is already in two scripts - this is often the case for Japan or Thailand or Singapore... Dunno if that is easy to implement. I hope/guess the above /mkgmap:trans:name/ would be easy, as the code exists if you use e.g. --latin1.
-- keep on biking and discovering new trails
Felix openmtbmap.org &www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org