Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74571 - libofx cannot parse non-ascii characters anymore

Attached to Project: Community Packages
Opened by Bennett Piater (ClawOfLight) - Wednesday, 27 April 2022, 15:01 GMT
Last edited by David Thurstenson (thurstylark) - Wednesday, 27 April 2022, 22:40 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
Recently, libofx stopped being able to parse non-ascii characters.

I encountered this while importing a monthly bank export into skrooge;
First I thought my bank was at fault, then I saw that old files also no longer worked, and after a round through the skrooge bug tracker I was able to track the issue down to libofx.

Additional info:
* package version(s): libofx 0.10.3-1
* config and/or log files etc.
* link to upstream bug report: https://bugs.kde.org/show_bug.cgi?id=452589 (skrooge)

Steps to reproduce:
- ofxdump on any ofx file containing non-ascii characters (e.g. รค).
This task depends upon

Comment by Jaroslav Lichtblau (Dragonlord) - Monday, 06 June 2022, 15:00 GMT
opening skrooge in the command line and trying to import the .ofx file shows the following:


LibOFX ERROR: OpenSP parser: otherError (misc parse error):
/tmp/libofxtmpmdARu2:48:39:E: non SGML character number 195

(Above message occurred on Line 48, Column 40)
LibOFX ERROR: OpenSP parser: otherError (misc parse error):
/tmp/libofxtmpmdARu2:48:40:E: non SGML character number 164

(Above message occurred on Line 48, Column 41)
Comment by Jaroslav Lichtblau (Dragonlord) - Monday, 06 June 2022, 15:02 GMT
although not sure how to get this one fixed or why it started to happen,
it seems that this issue has been seen for some time
https://github.com/libofx/libofx/issues/20
Comment by Bennett Piater (ClawOfLight) - Saturday, 11 June 2022, 10:14 GMT
That upstream issue as reported concerned windows only and thus had a very low priority.
If Arch no longer works, that leads me to think that this will start falling apart on all linux distros soon-ish, so I commented there and asked how I can help.

Thank you so far, let's see how we can get this fixed!

Loading...