Mapnik's XML parsing (in trunk/Mapnik2) recently switched to using all attributes for symbolizers (for Line/Pattern/Raster, etc like Pattern/Text symbolizers always did), but this means it is easy to make a typo of a property name without knowing. We should throw a warning, and perhaps in strict mode throw an error.
[herm] It would also be nice to have at least a warning when an invalid attribute ist used.
produces no error or warning. But "abc" is not a valid attibute for LineSymbolizer.
[springmeyer] yes, Herm I agree about the attributes. I am going to work on this. so, accepting ticket
[springmeyer] but as far as the first problem mentioned, it seems fixed now, as with ? and extra / I get:
RuntimeError: XML document not well formed:
Couldn't find end of Start Tag TextSymbolizer line 17 (encountered in file 'tests/data/good_maps/text_rotation.xml' at line 18)
[springmeyer] hmm... http://stackoverflow.com/questions/41453/how-can-i-add-reflection-to-a-c-application
[springmeyer] okay, impl of this is working, but I need to apply the function to check each part of the map which will take some time, so attaching patch so far for what I have, then will finish up next week.
[springmeyer] running this on one of the maps in the test suite reveals old usage of 'bgcolor' where mapnik2 only understands 'background-color', so this patch is already helping validate current xml in the test suite. will need to give though about whether to have a setting that might throw...
$ nik2img.py tests/data/good_maps/polygon_symbolizer.xml t.png
[springmeyer] done in r2582