Skip to content

encoding and charset lead to wrong imported char #20

@mdoyen

Description

@mdoyen

Hi,

Relative to HomeBak bug https://bugs.launchpad.net/homebank/+bug/1777553
Under windows 10 x64 latest with libofx 0.9.9 and opensp 1.5.2 (complied from sources in MSYS2 env into my Windows machine.

With this file Compte-CP-01_ex.qfx.txt

if I ofxdump, I get some invalid SGML error on what seems to be valid under the encoding
this file contains
ENCODING:USASCII
CHARSET:8859-1

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

(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
(this is on the first à)

I also tried with
CHARSET:1152, which was the real file encoding according to sublimetext
I also did encode to iso-8859-1

any french char is badly converted to weird char, ofxdump will display it

I also make a few more test with other files and same result.
So at last, is it a bug, of this file not specifying the right charset/encoding ?

I tried to gg to find some similar problem and just get into a post of a libofx bug fixed in 0.9.5
I did not find that much on valid value for libofx/opensp about charset/encoding values.

Any guidance welcome;)
Max.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions