Open Nimn opened 12 years ago
Hi @Nimn - thanks for the report/patch. Yes, Cascadenik is not up to date with latest Mapnik. The mapnik2
branch was an attempt, but it too is quite out of date.
That said, the changes between Mapnik 2.0.x and 2.1.x (unreleased) for the text_symbolizer a still in process, and therefore need to be handled on the mapnik side - basically we need backward compatibility maintained in Mapnik. See https://github.com/mapnik/mapnik/issues/1115. So, if you have time for a patch I would prefer that is it against Mapnik for the placements/format
issues.
Hi @springmeyer Actually this seems better to manage it in mapnik. I will not do it now but I try to give a look at it in the following weeks.
Okay, sounds good. I also previously ask @herm if he could work on this, so just check with him before you start to make sure its not already done.
I will fix this in mapnik soon. Currently I have a very bad internet connection and not very much free time. But the situation will improve soon and then I'll fix it.
I handled a few of these 584aafaf, not all though, and not tested thoroughly.
@herm - can you post an update about when you think you can get to this?
I think next week should be possible.
Should be fixed in mapnik/mapnik@707052c.
Is this a backwards-incompatible change in 2.1?
I added to compatibily layer for 2.1 and it will probably stay there for the whole 2.x series but it might be removed in 3.x.
These are priority: text-opacity/rgba, character-spacing and *-placement: internal
Mapnik 2.1 (not yet released) seems to have made changes on TextSymbolizer attributes. The attributes used by Cascadenik are now under "format" and "placements.defaults". The folowing path applied on branch mapnik2 seems to fix that: