Yes, that is correct. We need to update the migration guide to include this.
On 13 February 2015 at 10:39, <[email protected]> wrote: > oh! > > That means that if our database or datasource is encoded iso-8859-1, we > need to set ENCODING "iso-8859-1" in all our layers, there is no parameter > at the MAP level right? > > And, > > - Mapfiles themselves will be expected to be UTF8-encoded. Non > UTF8-encoded mapfiles will need to be iconv’d to utf8. > > > That means we cannot right any mapfile in iso-8859-1. we need to set our > IDe to write in utf-8. > > > Is my understanding correct? > > > > > *thomas bonfort <[email protected] <[email protected]>>* > > 2015-02-13 10:21 > A > [email protected] > cc > MapserverList OSGEO <[email protected]> > Objet > Re: [mapserver-users] mapserver 7 wfs_encoding > > > > > > > http://mapserver.org/development/rfc/ms-rfc-103.html > > -- > thomas > > On 13 February 2015 at 10:17, <[email protected]> wrote: > > Congratulations for the huge improve performance for WFS filtering with > > postgis and oracle... > > > > > > Mapserver 7 doesn't use wfs_encoding specified in the mapfile anymore, I > see > > anything in the changelog about that. > > > > Is there something change? > > _______________________________________________ > > mapserver-users mailing list > > [email protected] > > http://lists.osgeo.org/mailman/listinfo/mapserver-users > > > >
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
