[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-12-31 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=371069 NSLW changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-25 Thread Thomas Baumgart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #10 from Thomas Baumgart --- >From what I can tell, the data looks good if I read it using the UTF-16 decoder on the next page in the wizard. Nothing fancy or garbled. And I just omitted the return type void when I

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-22 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #9 from allan --- (In reply to Thomas Baumgart from comment #8) > I tried this on my KDE4, KMyMoney 4.8 production system (this is generated > of HEAD on the 4.8 branch). > When I change the encoding in the dialog to

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-22 Thread Thomas Baumgart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #8 from Thomas Baumgart --- I tried this on my KDE4, KMyMoney 4.8 production system (this is generated of HEAD on the 4.8 branch). What is annoying, that once I select a file it automatically goes off. No way to change

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-22 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #7 from allan --- [from Thomas] " Hi Allan, you found out yourself: the BOM is not wrong, it's missing. I am sure, you stumbled over https://en.wikipedia.org/wiki/UTF-16. I have not looked at the code of the CSV

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-21 Thread Jack via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 Jack changed: What|Removed |Added CC|

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-21 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #5 from allan --- Thomas suggested using Okteta to look at the data to see if the BOM was correct. Here are the first few lines :- " 22 00 4D 00 52 00 20 00 41 00 4C 00 ".M.R. .A.L. 000C 4C 00 41 00

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-21 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #4 from allan --- (In reply to allan from comment #3) > It looks like my attempts to provide an edited sample file either produce > rubbish, or remove whatever causes the problem. > So, I may have to provide a complete

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-18 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #3 from allan --- It looks like my attempts to provide an edited sample file either produce rubbish, or remove whatever causes the problem. So, I may have to provide a complete file, but I don't wish to broadcast it, so

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-18 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 allan changed: What|Removed |Added Attachment #101617|0 |1 is obsolete|

[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

2016-10-18 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371069 --- Comment #1 from allan --- Created attachment 101617 --> https://bugs.kde.org/attachment.cgi?id=101617=edit UTF-16 file -- You are receiving this mail because: You are watching all bug changes.