-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It starts (and ends) like this:
SYMBOLSET
SYMBOL
NAME "point"
TYPE ELLIPSE
POINTS
1 1
END
FILLED TRUE
END
SYMBOL
NAME "dashed"
TYPE ELLIPSE
POINTS
1 1
END
FILLED TRUE
STYLE
8 6 8 6
END
END
...
END
Regards,
David
On 30/04/2009, at 1:13 PM, Steve Lime wrote:
Can you share your symbolset file? I've not had an issue with that
change.
Steve
David Nugent <[email protected]> 04/29/09 9:54 PM >>>
Hello all,
I've recently upgraded to mapserver 5.4 and hit a problem with
SYMBOLSET.
It seems that a file containing symbols referenced from the .map file
must now contain a SYMBOLSET keyword at the start (and presumably end
with END?). I made this change, but the parser still complains with
the message "First token must be SYMBOLSET".
Not really wanting to waste time on debugging the lex code, I simply
removed the check that emits this error from mapsymbol.c and all works
as expected. Obviously there is a deeper problem, whether it be the
logic in that statement (which appears to be correct as far as I can
tell) or the lex parser itself.
I'm just wondering if anyone else had hit the same problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkn5IX4ACgkQgyBtWyGDJqVRXACfZnjgfrOnb7nQmKTF99gjA4WX
bMEAn28/+mRNOk60rbeTX4BbQUBF1q4L
=vbTf
-----END PGP SIGNATURE-----
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
