Bug 352614 - Banks are using UTF8, iso8859-X or Win-185x page alternatively for CSV export, but csv plugin is using the current locale only
Summary: Banks are using UTF8, iso8859-X or Win-185x page alternatively for CSV export...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-12 12:07 UTC by j.taimr@upcmail.nl
Modified: 2017-11-11 23:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description j.taimr@upcmail.nl 2015-09-12 12:07:35 UTC
KMyMoney CSV plugin is basically using the current locale and expects the CSV data imported are using the same locale. This cannot be guaranteed, because different banks are using different coding, if non-US. As the result, some input filed might be or malformed or even empty during/after the import. As the workaround the input file might be converted before the actual import, but it is inconvenient. It would be nice to have an option to choose input file coding during the import procedure within the cvs plugin itself.

Reproducible: Always

Steps to Reproduce:
1. On the system with UTF8 coding try to import csv data file containing, for example, 'ščřž' (Czech characters) in iso8859-2 coding
2. these characters will be skipped and become absent in the import previewer
3. .. and also as the result all these characters are missing

Actual Results:  
all characters >80 hex are stripped from the input file during the import procedure

Expected Results:  
There should be possibility to change input coding if it is not UTF8. (UTF8 is imported correctly, if it is the current locale)

there should be possibility to change input file coding during the import procedure, visualized in the previewer, so user may see and choose the appropriate coding...
Comment 1 allan 2015-09-12 12:25:00 UTC
When you get the File selection box to select the file to import,  at the bottom there is an Encoding selector with umpteen different options.  Hopefully,  you should see that and be able to select accordingly.

Does that give you what you need?

Allan
Comment 2 j.taimr@upcmail.nl 2015-09-12 12:45:06 UTC
ok, you are true, this is what I want. I am blind, sorry... Maybe it would be better to put the selection box closer to the previewer (at the moment of file opening you rarely know the file coding), but this is only the cherry on the cake. Close the bug, please...
Comment 3 allan 2015-09-12 12:58:41 UTC
(In reply to j.taimr@upcmail.nl from comment #2)
> ok, you are true, this is what I want. I am blind, sorry... Maybe it would
> be better to put the selection box closer to the previewer (at the moment of
> file opening you rarely know the file coding), but this is only the cherry
> on the cake. Close the bug, please...

I think what you are saying is that until you open the file, you don't realise the encoding is wrong.
At this point, however, the wizard is visible and you only have to click back to return to have the option to reselect, and change the encoding.