I do wonder still why it worked sometimes even though syntax was wrong. On 14 September 2017 at 00:15, Felix Hartmann <extremecarver@gmail.com> wrote:
Oh thanks - I was really blind here.
On 13 September 2017 at 19:31, Steve Ratcliffe <steve@parabola.me.uk> wrote:
On 13/09/17 18:17, Felix Hartmann wrote:
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}' }
The syntax for set is:
set name:int = '${name:en}' | '${int_name}' | ...
and not
set name:int = '${name:en}' | name:int='${int_name}' | ...
Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich
-- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich