Feature Request: specify character encodings on import and export

[GoogleCodeExporter]

Handling character encodings is a very common part of data cleansing for me.  
At the basic level, this means giving the option of specifying a character 
encoding on both import and export.  Going further, if raw bytes are a 
supported type, you could offer character encoding/decoding as a column 
transformation.  To make it really rich you could suggest the mostly likely 
character encodings at import time.

Original issue reported on code.google.com by defensec...@mamber.net on 12 Nov 2010 at 6:23

[GoogleCodeExporter]

Original comment by tfmorris on 16 Nov 2010 at 5:37

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Seems mostly a UI design thing. Assigning to James.

Original comment by dfhu...@gmail.com on 16 Nov 2010 at 12:56

• Changed state: Accepted