Hi all,
Steve Ratcliffe confirmed the existence of this problem to me in a private
message. In the next few days, I plan to implement special syntax for
variable substitution, because it will allow shorter style rules to be
written. See an example of the syntax at the bottom of my original
Quoting Steve Ratcliffe st...@parabola.me.uk:
On 12/14/2009 04:35 PM, Torsten Leistikow wrote:
Moin,
I have multiple map layers in my gmapsupp.img file, but I can not
set the name
of the layers, so that they can be identified on my nuvi.
The first layer is created by the following
On 12/21/2009 11:25 AM, char...@cferrero.net wrote:
Thanks for the info. I currently generate each layer of my 3-layer
map using the --gmapsupp switch and then just combine the three
gmapsupp.img files. Given your notes, it seems that this may be
wrong. Instead I should only create
On Dec 21, 2009, at 9:52, Marko Mäkelä wrote:
In the next few days, I plan to implement special syntax for
variable substitution, because it will allow shorter style rules to be
written. See an example of the syntax at the bottom of my original message
below.
Thanks. I have not had time to
Just to document my case, POIs in 3d mode is visible in nuvi 205 no
firmware update. I am guessing this is a firmware issue.
On Wed, Dec 9, 2009 at 11:16 AM, maning sambale
emmanuel.samb...@gmail.com wrote:
Ok thanks, so it's a feature, not a bug.
On Wed, Dec 9, 2009 at 10:08 AM, Ben Konrath
On Mon, Dec 21, 2009 at 12:08:26PM +0100, Clinton Gladstone wrote:
Will logical comparisons also work with the variable substitution?
That is, something like the following:
name != $(name:en) { ... }
This would make it easier to avoid redundant information in names.
(Such as, in the
On Mon, Dec 14, 2009 at 11:41:05PM +0200, Marko Mäkelä wrote:
Yet another solution would be to have a special syntax of variable
substitution that would bypass the valueTags, say, $(var) instead of ${var}:
(type=boundary | type=multipolygon) boundary=administrative name=*
{ apply
{
On Dec 21, 2009, at 20:20, Marko Mäkelä wrote:
I believe that the special name:* handling would be best implemented in
a special mkgmap option. I would try to avoid writing language suffixes
in style files.
The question of the logical comparisons is to avoid redundancies, some of which
