GNOME Bugzilla – Bug 310102
Broken reports in locales other than C/english (koi8-r, koi8-u)
Last modified: 2018-06-29 20:52:49 UTC
Distribution/Version: Debian Sarge Reports are broken in, for examle, Russian koi8-r,koi8-u locales. This problem seem to have commen roots with #147717 and #105345. Explaination: ------ export LANG=ru_RU.koi8-u export LC_ALL=ru_RU.koi8-u gnucash ------ Then add some accounts with koi8-u names. Then and some transactions with koi8-u descriptions. Then make report. In report window you'll get characters from second half of iso8859-1 (Russian and Ukrainian characters are in the second half of koi8-u). Workaround: Export broken report to .html. Open it with browser (Mozilla and Galeon tested), resave to test.html. This is done to replace characters in html from the form of &###; to the actual code. Then convert test.html from utf8 to iso8859-1 and you get correct koi8-u file: iconv -f utf8 -t iso8859-1 < test.html > test.koi8-u.html Summary: I'm not good enough with utf8, but it seems that gnucash or maybe library that gnucash uses for this doesn't take into account the actual locale charset when saving into utf8. It always saves characters as iso8859-1 to utf8. It should save to the correct place of utf8 that corresponds to the actual locale used. P.S. I hope there are Russian speaking developers, they should understand my mood :-) For any addidional information I'm available at: casper@meteor.dp.ua
There will be no further development on gnucash 1.8.x. Instead, gnucash-2.x will be based on gtk2 so all UTF-8 locales will be supported. See http://gnomesupport.org/wiki/index.php/GnuCashSvn for the latest SVN-HEAD
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=310102. Please update any external references or bookmarks.