Hi, I have noticed that the encoding must be "UTF-8 without BOM". Notepad++ has en encoding alternative "UTF-8" which seems to write "UTF-8 with BOM" and because of Byte order marker Mapserver does not accept such mapfiles. I am not sure if this is something to mention in the documentation or if it is rather a bug. Similar issue in GDAL was fixed by https://trac.osgeo.org/gdal/changeset/30994
Migration guide is http://mapserver.org/MIGRATION_GUIDE.html Corresponding RCF is http://mapserver.org/development/rfc/ms-rfc-103.html -Jukka Rahkonen- thomas Bonfort wrote: From mapserver 7.0 onwards, *always* encode your mapfile as UTF8. For more info read the migration guide and corresponding RFC. -- thomas On 3 November 2015 at 13:27, Andrea Peri <[email protected]> wrote: > Hi, > > sorry for the question, but I'm not skill on character enconding questions. > > My dubt is to understand what should be the right character encoding > for the mapfile ? > > The question born from the notice that the response at the > getcapabilities request return an xml where is declared: > > <?xml version='1.0' encoding="UTF-8" standalone="no" ?> > > But the containing seem don't be a real utf-8. > > I don't understand if should be the mapserver to convert into UTF-8 or > should be the user to write a regular UTF-8 mapfile. > > Thx, > > -- > ----------------- > Andrea Peri > . . . . . . . . . > qwerty àèìòù > ----------------- > _______________________________________________ > 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 _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
