https://bugs.kde.org/show_bug.cgi?id=452589
Bennett Piater <benn...@piater.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |UPSTREAM
--- Comment #8 from Bennett Piater <benn...@piater.name> ---
I tracked this down to the source and got a workaround implemented in libofx!
The cause of this issue is in OpenSP, which libofx uses to parse SGML and XML.
That library's quality is suboptimal, and the last release is 20 years ago -
obviously predating UTF.
So there are a ton of workarounds in libofx around multi-byte encodings...
Libofx has accepted the bug [0] and merged a workaround [1] for the case
described in this ticket, which amounts to treating this "error" as a warning
and ignoring it in the return status.
I was able to locally build and LD_PRELOAD that branch and could successfully
import previously-failing OFX files into Skrooge.
So I think we can treat this as fixed upstream, as soon as they release a new
version with the fix!
I can handle asking for a new release of libofx in arch, but since the Skrooge
project releases an AppImage that also didn't work for me, I would suggest that
you release a new build with the latest libofx as soon as that is released :)
PS: The "RESOLVED UPSTREAM" status is not described in
https://bugs.kde.org/page.cgi?id=fields.html#bug_status.
I hope this is the correct state for this ticket.
[0] https://github.com/libofx/libofx/issues/60
[1] https://github.com/libofx/libofx/pull/64
--
You are receiving this mail because:
You are watching all bug changes.
