Opened 18 years ago
Closed 18 years ago
#424 closed defect (fixed)
Make encoding used by FlatFileParser a configurable option
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.1.1 |
Component: | core | Version: | |
Keywords: | Cc: |
Description (last modified by )
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. The second step is to make it possible to select an encoding on a per-file basis. See ticket #425.
Change History (3)
comment:1 by , 18 years ago
Description: | modified (diff) |
---|
comment:2 by , 18 years ago
Status: | new → assigned |
---|
comment:3 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [2878]) Fixes #424: Make encoding used by FlatFileParser a configurable option
Added support in AbstractFlatFileImporter for asking and using a character set as a parameter for the configuration and/or job. Added that parameter to existing import plugins.