Dear list,
Need your opinion on this one… I’m having a really strange behaviour when rendering a feature with a SLD containing several two rules (a textsymbolizer on each one) pair. The TTF used it’s a custom one. This is the output rendering the same feature simultaneously with default_point and my SLD

I can confirm that the well positioned symbols are default_point’s.
With a combination of default_point and a SLD with textsymbolizers just putting the label ‘AAA’ where the geometries are, I get this:

It seems right.
All my custom SLD work fine with 1.7.2 stable release, but not with nightly builds from 032709 to 040309… Something changed that could provoke this behaviour or is just my custom TTF that could have been build with some “errors” that are uncover just now?
Thanks for your help… as always!
Cumprimentos,
Pedro Mendes
sld_test_label.sld (16 KB)
sld_node_mh.sld (124 KB)
Pedro Mendes ha scritto:
It seems right.
All my custom SLD work fine with 1.7.2 stable release, but not with nightly builds from 032709 to 040309.. Something changed that could provoke this behaviour or is just my custom TTF that could have been build with some “errors” that are uncover just now?
I finally found some time to check out your TTF fonts. I can reproduce
your results, as far as I can see the error is in the fonts, the
symbols is actually placed in the half upper part of the character
height for some reason.
It's easy to check this, just try your fonts in a word processor
and you'll see.
I've attached a screenshot of OpenOffice rendering normal fonts,
Webdings, OpenSymbols and your telecom one. As you can see yours
is not vertically centered and has a lot of space below it (I've
forced a gray background to show what the space used by the
font actually looks like).
Cheers
Andrea

Hi,
Thanks for replying. I just confirmed that when trying to figured out what
was wrong with our dynamic ttf marks SLD. We're rebuilting it to a valid
symbolic TTF. Another thing: this kind of sld configuration (pointsymbolizer
+ ttf mark) only works with Symbolic TTF type? with non-based symbolic
font(arial, courier, our font, etc) TTF marks dont't seem to work, it always
result in the "not defined" symbol (the first glyph of each font).
best regards,
Pedro Mendes
Andrea Aime-4 wrote:
Pedro Mendes ha scritto:
It seems right.
All my custom SLD work fine with 1.7.2 stable release, but not with
nightly builds from 032709 to 040309.. Something changed that could
provoke this behaviour or is just my custom TTF that could have been
build with some “errors” that are uncover just now?
I finally found some time to check out your TTF fonts. I can reproduce
your results, as far as I can see the error is in the fonts, the
symbols is actually placed in the half upper part of the character
height for some reason.
It's easy to check this, just try your fonts in a word processor
and you'll see.
I've attached a screenshot of OpenOffice rendering normal fonts,
Webdings, OpenSymbols and your telecom one. As you can see yours
is not vertically centered and has a lot of space below it (I've
forced a gray background to show what the space used by the
font actually looks like).
Cheers
Andrea
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/TextSymbolizer-%2B-custom-TTF-%3D-incorrect-positioning!-tp22874841p23124440.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi.
If you get the character code like this in your SLD file:
<WellKnownName>ttf://Arial#${'U+0021'}</WellKnownName> (example for Arial
font, character "!")
inside your PointSymbolizer, it will work perfectly for all ttf fonts.
Victor
--
View this message in context: http://www.nabble.com/TextSymbolizer-%2B-custom-TTF-%3D-incorrect-positioning!-tp22874841p23138545.html
Sent from the GeoServer - User mailing list archive at Nabble.com.