Issues/Observations with OFX & online banking

Benoit Gregoire bock at
Thu Jul 13 17:54:15 EDT 2006

> *) OFX encoding ignored?;
> Importing from OFX files within gnucash (and also downloading
> transactions directly from within gnucash) seems to ignore the OFX
> charset encoding; the OFX files (version 1.02) I've encountered had
> CHARSET:1252
> which is also what libofx seems to request; but for some reason this
> information isn't passed on to OpenSP (actually I didn't find any
> parsing for those headers in libofx), and neither gnucash seems to do
> any conversion; and since my bank statements include the following
> characters (the 1252 codepage corresponds to latin1) in the MEMO field:
>        Oct   Dec   Hex   Char   Description
>        304   196   C4     Ä     LATIN CAPITAL LETTER A WITH DIAERESIS
>        313   203   CB     Ë     LATIN CAPITAL LETTER E WITH DIAERESIS
>        326   214   D6     Ö     LATIN CAPITAL LETTER O WITH DIAERESIS
>        344   228   E4     ä     LATIN SMALL LETTER A WITH DIAERESIS
>        353   235   EB     ë     LATIN SMALL LETTER E WITH DIAERESIS
>        366   246   F6     ö     LATIN SMALL LETTER O WITH DIAERESIS
> those get passed on to gnucash unmapped, and cause broken memo fields
> there...

The problem is that the only documented API to OpenSP has no facility to pass 
encoding information.  Changing to the internal API would be somewhat of a 

However, assumning SP dosen't mess with the characters, it should be possible 
to pass the source encoding to gnucash to allow it to do an appropriate 

More information about the gnucash-devel mailing list