-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TextSymbolizer attributes with Mapnik 2.1 #21
Comments
Hi @Nimn - thanks for the report/patch. Yes, Cascadenik is not up to date with latest Mapnik. The 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 mapnik/mapnik#1115. So, if you have time for a patch I would prefer that is it against Mapnik for the |
Hi @springmeyer |
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 584aafa, 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: |
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:
The text was updated successfully, but these errors were encountered: