Importing OFX files with Japanese characters (UTF-8) broken?

Brian Clarkson clarkson at orthogonaldevices.com
Fri Feb 7 08:34:00 EST 2014


Thanks, John. I will definitely take a look once this tax season is 
finished. For now I just imported it in garbled format and then manually 
fixed each transaction. It took a while but at least I can move on for 
now. This will keep coming up for me though, so I want to have it 
working properly somehow. I might instead write my own importer in 
Python that just inserts transactions directly into the gnucash 
database. I have to write Python code to massage some of my bank 
statements anyways.

Is there a sqlite3 backend for windows-version of gnucash? If not, I 
guess I can still do Ubuntu in VMWare...

On 2/6/2014 12:20 AM, John Ralls wrote:
> On Feb 4, 2014, at 10:56 PM, Brian Clarkson <clarkson at orthogonaldevices.com> wrote:
>
>> Hi All
>>
>> I'm just starting out with gnucash and liking it a lot. However there has been one problem. One of my bank accounts is in Japan and the bank provides OFX files with Japanese characters (namely, in the description field) that are UTF-8 encoded. It is pretty clear to me that as a program, gnucash supports Japanese characters via unicode when doing manual entry, however it seems the 'Generic import transaction matcher' fails to handle UTF-8.
>>
>> Here is the header from my OFX file:
>>
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:UTF-8
>> CHARSET:CSUNICODE
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:NONE
>>
>> Does anyone have any ideas how I can import transactions with Japanese characters correctly? Should I go to the dev list for this? I am even willing to go into the codebase to solve this but I would need help compiling on Windows.
> Sounds like https://bugzilla.gnome.org/show_bug.cgi?id=703527 and https://bugzilla.gnome.org/show_bug.cgi?id=703527, which may be duplicates. If you want to have a go at fixing it, the code will be in src/import-export/ or src/import-export/ofx.
>
> Setting up and using a development environment on Windows is a royal PITA. I recommend setting up a Linux VM, as that's much easier.
>
> Regards,
> John Ralls
>



More information about the gnucash-user mailing list