Hi, I've finally have some time to improve batik agent and fix rendering rules. After the patches are applied, batik in agent mode should run smoothly again (including problem from "Batik rendering broken?" thread).
First there is new batik-agent.jar (http://jttt.110mb.com/batik-agent.jar). It should now always report when rendering fails and write additional info to log. It also reports to log when classpath is not set correctly. Then little patch to orp to prevent opacity attribute without value: http://jttt.110mb.com/orp.patch And finally fixed sac scale rules: http://jttt.110mb.com/osmarender.patch After the patch is applied, rendered tile is sligtly different. I have no idea why, anyway it's not possible to spot the difference just by eye, so I guess it's ok. On Fri, Jul 18, 2008 at 9:51 PM, Jiri Klement <[EMAIL PROTECTED]> wrote: > This might be caused by newly added sac scale rendering. For example > CSS .sac-scale-t2 contains stroke-dasharray: "0.5%, 0.5%"; which is > not valid (% sign should be there). > > Can somebody please fix the rendering rules? I will make patch for > batik-agent to be more verbose next time it fails because of incorrect > svg. > > > On Wed, Jul 16, 2008 at 8:11 PM, Paul Cunnane <[EMAIL PROTECTED]> wrote: >> On Tue, 2008-07-15 at 23:59 +0100, Paul Cunnane wrote: >> >>> Following up: I had a look at one of the temporary PNG files (attached). >>> Looks like it's rendering the land in black, no idea why. >> >> Still getting some of these. The land only gets rendered in black for >> some parts of the tile at some zoom levels. >> >> I'm puzzled. I guess it's back to Inkscape for the moment. >> >> -- >> Paul >> >> >> _______________________________________________ >> Tilesathome mailing list >> [email protected] >> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome >> > _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
