WFS proxy csv outputFormat, Excel encoding issue if UTF8

[adube]

Original issue

Microsoft Excel (2003 in our test-case) doesn't detect the encoding nor propose to choose it from a list when double-clicking on a .csv file. So, if our file is UTF8 encoded, it's not correctly read and you can have hazardous characters.

Workaround

In Excel, you can use "Data / import from a file" and you'll have the choice of setting the correct encoding, but it's not as user-friendly as double-clicking on the file.

Solution in GeoPrisma

We could have a new service option, like 'utf8Decode' that could be used by the proxies (the WFS one in our case) that, when set to true would decode the output string from UTF8 to iso-latin-1.

[adube]

Fixed r1140 and r1141, featuring :

• new 'utf8Decode' service option
• currently only used by WFSReadProxy if returned content-type is text/csv
• documentation

Tested with Excel : a double-click opens the file and it has no bad characters.

Fixed.