GnuCash
Contact   Instructions
Bug 797088 - Encoding problem with CSV-formated account tree import
Summary: Encoding problem with CSV-formated account tree import
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Import - CSV (show other bugs)
Version: 3.4
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
: 797336 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-02-04 21:04 EST by milotype
Modified: 2021-09-23 18:50 EDT (History)
6 users (show)

See Also:

Attachments
ACCOUNTimport01-HR.csv (684 bytes, text/csv)
2019-02-04 21:04 EST, milotype 		no flags Details
Screenshot of accounts (87.49 KB, image/png)
2019-02-05 05:51 EST, Bob 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description milotype 2019-02-04 21:04:26 EST 
Created attachment 373164 [details]
ACCOUNTimport01-HR.csv

When importing UTF-8 CSV-formated account tree (File > Import > Import Accounts from CSV), the import tool doesn’t accept strings with croatian characters. I’ve also tried different CSV encoding formats, but to no avail.
Changing the diacritic character into a non-diacritic, enables the import.

Please view and test the attached file – row 6 has croatian diacritics:
„ACCOUNTimport01-HR.csv” – with croatian diacritic => import impossible
Comment 1 Bob 2019-02-05 05:51:15 EST 
Created attachment 373165 [details]
Screenshot of accounts

I am confused about this but that is not unusual, I tried your file on my Linux VM which is in English and it imported just fine as can be seen in the attached screen shot.
Comment 2 milotype 2019-02-05 13:10:33 EST 
The problem occurs in the 3rd dialog "Import Account Preview, first 10 rows only". If I've selected the file, this dialog dispays an emtpy preview field. Only the croatian header-strings are shown. And the button to proceed stays inactive.

Mac OS 10.11.6, running the OS's croatian localization
Comment 3 Helmut 2021-02-21 03:49:40 EST 
For Windows 10 I probably found a solution in system settings for the problem on account structure import resulting in funny characters. Reason seems to be missing UTF-8 support by operating system. UTF-8 support can now be added to Win10 but still is in BETA release.

See full instructions as stated this comment:
https://bugs.gnucash.org/show_bug.cgi?id=782850#c11

I'm not sure if Mac OS will offers similar settings, but if you are able to verify please report your results.
Comment 4 John Ralls 2021-02-21 11:33:53 EST 
(In reply to Helmut from comment #3)
> For Windows 10 I probably found a solution in system settings for the
> problem on account structure import resulting in funny characters. Reason
> seems to be missing UTF-8 support by operating system. UTF-8 support can now
> be added to Win10 but still is in BETA release.
> 
> See full instructions as stated this comment:
> https://bugs.gnucash.org/show_bug.cgi?id=782850#c11
> 
> I'm not sure if Mac OS will offers similar settings, but if you are able to
> verify please report your results.

macOS is UTF-8 all the way down, there should be no need for transcoding.
Comment 5 John Ralls 2021-02-21 11:35:12 EST 
@milotype, I imported your test file into macOS 11 with GnuCash 4.4. There were no encoding issues.

Please test on 4.4 yourself.
Comment 6 John Ralls 2021-09-23 18:50:07 EDT 
*** Bug 797336 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.