On Tuesday 17 January 2012 21:53:29 Thomas Baumgart wrote: > Hi, > > on Tuesday 17 January 2012 19:49:55 Cristian Oneț wrote: > > On Monday 16 January 2012 15:48:34 Jack wrote: > > > On 2012.01.16 14:12, Cristian Onet wrote: > > > > https://bugs.kde.org/show_bug.cgi?id)1685 > > > > > > > > OFX files with UTF-8 data are not imported correctly. > > > > > > Can I assume that the fix will not affect OFX files which are NOT in > > > UTF-8? (Sorry, I'm just in a paranoid mood today.) > > > > No, they will not be affected since Latin1 is a subset of UTF-8. > > Not really. > > thb@thb-nb:~> cat test > äöü > thb@thb-nb:~> file test > test: UTF-8 Unicode text > thb@thb-nb:~> hexdump -C test > 00000000 c3 a4 c3 b6 c3 bc 0a |.......| > 00000007 > thb@thb-nb:~> recode utf8..latin1 test > thb@thb-nb:~> file test > test: ISO-8859 text > thb@thb-nb:~> hexdump -C test > 00000000 e4 f6 fc 0a |....| > 00000004 > > US-ASCII is a subset of UTF-8 though, so you folks in the US should not be > affected if your bank supplies files in US-ASCII.
OK, my explanation was lame :) I have to admit it. The real explanation is that the buffer returned by libofx containing a string is UTF-8 encoded and it was working fine until now because we only had users importing data conatining US-ASCII characters. -- Regards, Cristian Oneț
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
