Dane Springmeyer wrote:
zsj,
Could you please report the below issue on trac.mapnik.org?
Thanks,
Dane
On Jul 19, 2010, at 7:13 AM, feverzsj wrote:
Artem Pavlenko wrote:
Wow, interesting. Could you try using another font (unifont?) to see
if this fixes the problem.
Also, please, provide your setup details and full style .xml file
Regards
Artem
Well, after rechecking the xml, it might be a mistake by me.
There is already another TextSymbolizer rule in the style which appears before
the style showing the larger font in the layer's style list.
But, according to the render order, why the later style is skipped? It seems
that mapnik scans the whole xml and decides what to be rendered in a more smart
way than the painter's algorithm.
The attachment contains the shp and xml files which can reproduce the case
using unifont.
Furthermore, mapnik 0.71 on my win xp also can't handle non ascii(chinese) path
from xml definition.
For example:
If you extract the attachment to some non ascii path and load the xml into
mapnik,
the console will give 'RuntimeError: wrong file code : 1891049728 (encountered
during parsing of layer 'adm_area').'
Using non ascii path in xml will give you somthing like 'RuntimeError:
unrecognizable glpyhs/adm_area does not exist (encountered during parsing of
layer 'adm_area''
-- Regards, zsj
<TextSymbolizer on polygon.zip>
Yes, of course. But, which one? The 'TextSymbolizer on polygon' or the
'mapnik can't handle non ascii(chinese) path from xml definition'?
Regards, zsj
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users
