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 Toolybird (Toolybird) - Friday, 19 May 2023, 05:16 GMT
Opened by Bennett Piater (ClawOfLight) - Wednesday, 27 April 2022, 15:01 GMT
Last edited by Toolybird (Toolybird) - Friday, 19 May 2023, 05:16 GMT
|
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
Closed by Toolybird (Toolybird)
Friday, 19 May 2023, 05:16 GMT
Reason for closing: Fixed
Additional comments about closing: libofx 0.10.6-1
Friday, 19 May 2023, 05:16 GMT
Reason for closing: Fixed
Additional comments about closing: libofx 0.10.6-1
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)
ofx-works.ofx (2.2 KiB)
it seems that this issue has been seen for some time
https://github.com/libofx/libofx/issues/20
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!
And a fix was recently merged to master: https://github.com/libofx/libofx/pull/64
Upstream has not tagged a new release yet, but I have successfully tested the fix locally by LD_PRELOADing a git build against skrooge.
So this bug can be closed soon, whenever we can upgrade to their version or, if others complain about this issue, by including the patch temporarily.