Push Up! After using unicode maps for some more time, I think this is really important. Especially for older devices which will only show a subset of latin1 characters present in unicode. I would like to make sure to have the possibility to use transliteration even for unicode maps. Case Object 1: name:en=moscow name=?????? Case Object 2: name=?????? Rules: name:en=* & name=* {set name='${name:en}' '${name}'} name:en!=* & name=* {set name='${mkgmap:translatin:name}' '${name}'} where mkgmap:translatin:name tells mkgamp to try to transliterate the name to latin.. Of course it would be even better if there could be a rule like name:en!=* & name=* & name!=mkgmap:latin - so mkgmap would check if the script is latin, and if not pass on to the next line. But even the simple rule without check would be a great help. On 02.07.2014 22:27, Felix Hartmann wrote:
The standard behavior so far for my maps in Japan or China was to use --latin1, and hope that all towns/cities/names if not name:en present - got transliterated decently into latin characters. However if using Unicode this is of course not happening.
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) '
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