Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GnuCash exports QIFs within a compressed archive, but confusingly gives the archive a .qif file extension rather than a .zip extension. #889

Open
FatherMcGruder opened this issue Aug 27, 2020 · 2 comments

Comments

@FatherMcGruder
Copy link

FatherMcGruder commented Aug 27, 2020

Steps to reproduce the behaviour

  1. Use the export to QIF function within the app.

Expected behaviour

The app should produce a QIF file that is human readable in a text editor and compatible for import into the GnuCash desktop program.

Actual behaviour

The app generates a QIF file that GnuCash desktop will not import and will not open properly in a text editor. None of the encodings the text editor lets me choose from, including UTF-8, UTF-16, and ISO-8859-15, render the file in a readable format. compressed archive with a .qif extension rather than .zip. The actual QIF file (multiple if you have transactions in different currencies) is not usable with GnuCash Desktop unless you extract it with an archive manager, which is not obvious and rather frustrating. Some text editors will successfully open the compressed QIF if there is only one actual QIF within (if there are only transactions in one currency), which adds to the confusion.

Software specifications

  • GnuCash Android version: 2.4.1
  • System Android version: Oxygen OS 10.0.11.HD65AA
  • Device type: OnePlus 7T
@FatherMcGruder FatherMcGruder changed the title Incorrect or problematic encoding of exported QIF file. GnuCash exports QIFs within a compressed archive, but confusingly gives the archive a .qif file extension rather than a .zip extension. Nov 15, 2020
@Thumas
Copy link

Thumas commented Jun 20, 2021

The problem is that the user has to choose the file name before the data is exported. If the app finds multiple currencies, it creates a zip archive and moves it to the chosen location, without telling the user it had to do that.
I think the best way to resolve this is to always create a zip file, even if you only have one QIF file to export. That way we do not have to overrule the user's file name choice or inform him about the result. The minor inconvenience of having to extract the file before importing it into GnuCash desktop is acceptable IMHO.

@FatherMcGruder
Copy link
Author

FatherMcGruder commented Jun 20, 2021 via email

Thumas added a commit to Thumas/gnucash-android that referenced this issue Jun 20, 2021
…files.

Synchronization of active database. Some refactoring en passant. Fixed some IntelliJ warnings.
Thumas added a commit to Thumas/gnucash-android that referenced this issue Jun 20, 2021
…files.

Synchronization of active database. Some refactoring en passant. Fixed some IntelliJ warnings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants