[Kmymoney-devel] [kmymoney] [Bug 352614] New: Banks are using UTF8, iso8859-X or Win-185x page alternatively for CSV export, but csv plugin is using the current locale only
j.taimr at upcmail.nl
j.taimr at upcmail.nl
Sat Sep 12 12:07:35 UTC 2015
https://bugs.kde.org/show_bug.cgi?id=352614
Bug ID: 352614
Summary: Banks are using UTF8, iso8859-X or Win-185x page
alternatively for CSV export, but csv plugin is using
the current locale only
Product: kmymoney
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: General
Assignee: kmymoney-devel at kde.org
Reporter: jata2004 at gmail.com
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...
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel
mailing list