[Kmymoney] Re: Text encoding problem with aqbanking ofx

[Thomas Baumgart]

Hi,

on Sunday 16 January 2011 20:30:31 Alexander 'Leo' Bergolth wrote:

> Hi!
> 
> I just used the aqofxconnect backend of the aqbanking plugin for the
> first time.
> 
> Unfortunately I noticed problems when importing transactions containing
> 8 bit latin1-characters like umlauts:
> 
> <MEMO>Abbuchung Einzugsermächtigung
> becomes:
> Abbuchung Einzugserm chtigung
> 
> in kmymoney.
> 
> I traced the ofx-packets using AQOFX_LOG_COMM=1 and verified that the
> character encoding on the wire is latin1.
> 
> My locale settings are LANG=en_US, (i.e. latin1).
> 
> I couldn't find any way to specify an import-encoding in kmymoney...

... because there isn't an option for it. The interface at that point expects 
UTF-8. Here's the relevant code line:

      s += QString::fromUtf8(p);

's' is the string inside KMyMoney and 'p' points to the data received by AqB.

It would be handsome to keep the encoding with AqB's OFX settings of the bank 
and maintain a generic interface between AqB and KMyMoney (as we have it today 
with UTF-8).

Do you see the same problems when using KMyMoney's own OFX implementation?

-- 

Regards

Thomas Baumgart

GPG-FP: E55E D592 F45F 116B 8429   4F99 9C59 DB40 B75D D3BA
-------------------------------------------------------------
There's no place like 127.0.0.1
-------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 225 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kmymoney/attachments/20110117/4f14b63c/attachment.sig