windows/libofx: import non utf-8 char bad for é è à ...

Bug #1777553 reported by francois
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
HomeBank
Triaged
Low
Unassigned

Bug Description

Accent in ofx file from my banq is not imported correctly. Accents in memo field are replaced by symbols

See attached file.

Tags: bug-libofx
Revision history for this message
francois (fbeauchemin) wrote :
description: updated
Revision history for this message
Maxime DOYEN (mdoyen) wrote :

homebank version ?
os ?

Changed in homebank:
status: New → Incomplete
Revision history for this message
francois (fbeauchemin) wrote :

HB version: 5.1.8
OS: Win10

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

your file contains
ENCODING:USASCII
CHARSET:8859-1

but OFX library detect CP1152.
this file is a direct download, without any alteration ?
what if you convert it again to 8859-1 (can be done with a text editor ?
https://www.google.com/search?q=text+editor+change+encoding

Maxime DOYEN (mdoyen)
Changed in homebank:
status: Incomplete → New
Revision history for this message
Maxime DOYEN (mdoyen) wrote :

ofxdump the file produce SGML errors, I will post to libofx dev to get guidance on if your file is wrong or libofx problem

LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:38:20:E: non SGML character number 9500

(Above message occured on Line 38, Column 21)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:38:21:E: non SGML character number 174

(Above message occured on Line 38, Column 22)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:38:23:E: non SGML character number 9500

(Above message occured on Line 38, Column 24)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:38:24:E: non SGML character number 225

(Above message occured on Line 38, Column 25)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:46:7:E: non SGML character number 9500

(Above message occured on Line 46, Column 8)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:46:8:E: non SGML character number 174

(Above message occured on Line 46, Column 9)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:46:10:E: non SGML character number 9500

(Above message occured on Line 46, Column 11)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
C:\Users\Maxime\AppData\Local\Temp\libofxtmpXXXXXX:46:11:E: non SGML character number 9508

Revision history for this message
Maxime DOYEN (mdoyen) wrote :
Maxime DOYEN (mdoyen)
Changed in homebank:
importance: Undecided → Medium
importance: Medium → Undecided
Maxime DOYEN (mdoyen)
summary: - french accent
+ libofx: encoding import trouble with non utf-8
Changed in homebank:
importance: Undecided → Low
Maxime DOYEN (mdoyen)
tags: removed: accent
tags: added: libofx
Maxime DOYEN (mdoyen)
summary: - libofx: encoding import trouble with non utf-8
+ win/libofx: import non utf-8 char bad for é è à ...
Revision history for this message
Eduardo (eduedp) wrote : Re: win/libofx: import non utf-8 char bad for é è à ...

I'm having trouble importing any ofx file with special characters like accents, no mather what the encoding is. Tried UTF-8, cp1252, 8859-1....

Is there a workaround for now?

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

the problem is due to a bug with libofx compiled for windows, we wait for a patch
https://github.com/libofx/libofx/issues/20

Maxime DOYEN (mdoyen)
Changed in homebank:
status: New → Triaged
Revision history for this message
Eduardo (eduedp) wrote :

Any news on that libofx patch?

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

As you may see by yourself by reading the bug page @libofx,

the author is blocked in building a test env into his Windows machine.
I've just gave him a procedure to follow, hoping he will succeed and be able to debug, and at last hopefully propose a patch.

Maxime DOYEN (mdoyen)
tags: added: bug-libofx
removed: libofx
Revision history for this message
Sergey Mitrichev (for-serg) wrote :

Similar problems with importing UTF-8 OFX files with non-latin letters on HomeBank 5.2.6 / Windows 10 v1903. The same OFX file in Ubuntu imports well.

Waiting for the ofxlib patch...

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

@All:
don't hesitate to encourage the libofx maintainers @https://github.com/libofx/libofx/issues/20

Maxime DOYEN (mdoyen)
summary: - win/libofx: import non utf-8 char bad for é è à ...
+ windows/libofx: import non utf-8 char bad for é è à ...
Revision history for this message
bleutneut (bleutneut) wrote :

Hello

Is it possible to fix it as well for month's name in french language when data are exported in csv file

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

@bleutneut:
absolutely not related with this bug, csv import do not use libofx.

your csv file file is just not well encoded (UTF-8) see the doc

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.