GNOME Bugzilla – Bug 305121
Postgresql backend: UNICODE not working properly
Last modified: 2018-06-29 20:52:25 UTC
Please describe the problem: Using 1.8.9 and Postgresql as backend on SuSE 9.2. After O/S upgrade I assume that the character set was changed to UNICODE and some of the non-ascii-127 characters that previously worked well, now are rubbish. I changed the character encoding of database to UNICODE and on database level everything seems to work perfectly ok, but on GnuCash GUI most of the time those characters can be entered, but their outlook is not the right one. It looks like they were still interpreted as 8-bit ascii. Even worse is that while entering entries for one account, when such a text is automatically copied from previous entries this will lead a complete crash and the whole application dies. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? This is a systematic error. Happening always. Other information:
No, gnucash 1.8.x does not support UTF-8 or unicode. It is still a gtk1 application and only uses an 8-bit character set, e.g. ISO-8859-15 or whatever used to be your locale before your OS upgrade. This won't be fixed in the 1.8.x. branch but only in the gnome2 branch, which may or may not be released this year. A related bug is #105345
Gnucash 1.8 is no longer being updated. Please try 2.0 when it is released and see if there is still a problem. The switch from gtk1 to gtk2 and rework in gnucash2 to support unicode should fix all unicode problems.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=305121. Please update any external references or bookmarks.