just an idea, but maybe check your client_encoding parameter in
postgresql.conf
I may be wrong, but I think that mapserver id acting as a client for the
db, and may have the results returned into the client_encoding character
set.
Guillaume
Gabriel Messner a écrit :
Hi all,
I´ve set up a WFS server with mapserver. Data is stored in Postgis
database. Encoding settings are the followings:
-Spatial Data Base encoding is UTF-8
-For each layer in the mapfile encofing is also UTF-8 indicated with
'layer_encoding' 'UTF-8'
The server retuns successfully geometries and attributes but the the
characters 'ñ',á,é,í,ó,ú are missing (spanish).
I´ve tried to solve this problem using 'wfs_encofing' 'UTF-8' into the
Web object Metadata but when doing so and trying to add a wfs layer with
UDig, an alert is displayed saying 'wrong connection parameters'. I´ve
also tried with 'ows_endoding' and 'gml_encoding' at Web object
Metadata but I fail as well.
I´d hughly appreciated if anyone can help me.
Thanks in advance.
Gabriel Messner
------------------------------------------------------------------------
_______________________________________________
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
