Anyone got any idea why the following rule is not working as expected? name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* | name_int=* | name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* | name:dk=* ) {set name:int='${name:en}' | name:int='${int_name}' | name:int='${name_int}' | name:int='${name_en}' | name:int='${name:de}' | name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' | name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' } If I use it - and then later set name:int=* {set name='${name:int}'} I end up having many places in my map where instead of using the actual name:int value I get "name:int" instead. Sometimes it does work however - so I'm at a loss why. If I instead write out the rules one after another it does work well - is the rule to long? is there some bug in mkgmap? Do I have some super strange spelling mistake in it? (so if I write name:int!=* & name:en=* { set name:int='${name:en}' } name:int!=* & int_name=* { set name:int='${int_name}' } ...... it works correctly (but I think this will be slow to process and is simply many more lines to write.) Is the rule too long? Is there some bug in mkmgap? do I have a typo even though I checked it for ages? It really just works for some objects and for some it will instead put name:int into the label instead even though all name tags are identical. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich