As a follow-up to the interpretation of the sld error message, I have tried the
following.
First the background:
My server in Norway couldn´t render a shapefile which had to read a filter
based
on attributes which have the letter "ä" in them
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>Zweck_1</ogc:PropertyName>
<ogc:Literal>Wohnbaufl?che</ogc:Literal>
christian.mueller suggested this....
"On your ubuntu server, try the following
env | grep LANG
The result should be something like
LANG=en_US.UTF-8
indicating the default encoding is utf-8
Try
file -mime-encoding yoursld.sld
The result should show you the encoding of the file
These two encodings seem not to be the same.
The best solution for such kind of problems is to use UTF-8 on windows/linux.
Do you have an editor in windows (like ultraedit ) giving you the
possibility to save the sld using utf-8 ?.
If you have, chance your xml header to "encoding=utf-8" and save.
Afterwards you should be happy on both platforms."
I tried this, and uploaded the sld to geoserver, which then still interpreted
the "ä" as a ?
It is probably something simple which I am forgetting. I had to reinstall
Ubuntu a few weeks ago, and I think this may have something to do with it.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
