Store the character encoding for text files

[Nicklas Nordborg]

When the FlatFileParser? reads files it uses the system default encoding. On my Linux machine the default is UTF-8 and on Windows the default is cp1252. This causes problems since files doesn't have to use any of these encodings but cp1252 or ISO-8859-1 is more likely than UTF-8. The first step towards solving this problem is to add a configuration option in the base.config file for the encoding to use (ticket #424). The second step is to make it possible to select an encoding on a per-file basis. This possible also affects the encoding used in web pages, the view/download servlet, export plugins, etc.

[Jari Häkkinen]

Is there a need to fix this ticket.

[Nicklas Nordborg]

(In [4520]) References #425: Store the character encoding for text files

Fixed in data and core layer, test program, list and view page on web, file upload and download. Remains to fix in "Test with file" and auto-detect file format functionality.

[Nicklas Nordborg]

(In [4521]) References #425: Store the character encoding for text files

"Test with file" function fixed.

[Nicklas Nordborg]

(In [4522]) References #425: Store the character encoding for text files

Added missing file needed for the "Test with file" function.

[Nicklas Nordborg]

(In [4523]) References #425: Store the character encoding for text files

Export plug-ins saves the character set used when exporting the data.

[Nicklas Nordborg]

(In [4524]) References #425: Store the character encoding for text files

Document changes in ExportOutputStream?.

[Nicklas Nordborg]

(In [4525]) References #425: Store the character encoding for text files

Adding support for selecting character set in the autodetect file format function.

[Nicklas Nordborg]

(In [4526]) References #425: Store the character encoding for text files

Updated the UML diagram

[Nicklas Nordborg]

(In [4540]) References #425, #1126. Now sets character set correctly when file upload.