[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-07-24 Thread Bennett Piater
https://bugs.kde.org/show_bug.cgi?id=452589

Bennett Piater  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |UPSTREAM

--- Comment #8 from Bennett Piater  ---
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.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-05-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=452589

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #7 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=452589

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-24 Thread Stephane MANKOWSKI
https://bugs.kde.org/show_bug.cgi?id=452589

--- Comment #5 from Stephane MANKOWSKI  ---
You can play with ofxdump to check if the issue is coming from libofx.

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-24 Thread Bennett Piater
https://bugs.kde.org/show_bug.cgi?id=452589

--- Comment #4 from Bennett Piater  ---
I will contact my libofx maintainer then, thank you! Do you have any other
hints or ideas?

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-24 Thread Stephane MANKOWSKI
https://bugs.kde.org/show_bug.cgi?id=452589

--- Comment #3 from Stephane MANKOWSKI  ---
Created attachment 148340
  --> https://bugs.kde.org/attachment.cgi?id=148340=edit
Import

Hi,
No issue for me with this file.
The import seems to be correct.

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-20 Thread Bennett Piater
https://bugs.kde.org/show_bug.cgi?id=452589

--- Comment #2 from Bennett Piater  ---
Created attachment 148271
  --> https://bugs.kde.org/attachment.cgi?id=148271=edit
minimal reproducing example

I did some more digging because my minimal anonymous file didn't trigger the
issue.
After playing with 'xmllint' and not finding anything, I tried importing a
pretty-printed file and the cause became obvious: The offenders where all
non-ascii characters.
I attached a minimal example that I was able to reproduce this with.

The funny thing is that nothing major changed about my system. Every software
handles unicode just fine, and this file used to be correctly imported in
previous versions (of skrooge and probably it's dependencies).

This is the output of 'locale':
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-14 Thread Stephane MANKOWSKI
https://bugs.kde.org/show_bug.cgi?id=452589

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
   Assignee|guillaume.deb...@gmail.com  |steph...@mankowski.fr

--- Comment #1 from Stephane MANKOWSKI  ---
Hi,

Could you provide me an anonymized ofx sample file to reproduce the issue ?

This is just to identify if the issue is coming from the format of the OFX file
or from your installation.
For information, the error is not raised by Skrooge but by libofx. This could
be due to an issue in installation of libofx.

-- 
You are receiving this mail because:
You are watching all bug changes.

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-04-13 Thread Bennett Piater
https://bugs.kde.org/show_bug.cgi?id=452589

Bennett Piater  changed:

   What|Removed |Added

Version|Trunk from git  |unspecified

-- 
You are receiving this mail because:
You are watching all bug changes.