GNOME Bugzilla – Bug 760711
Non-ASCII characters not shown in Report Name when a report is created with 2.6.11
Last modified: 2018-06-29 23:46:31 UTC
I have recently upgraded to version 2.6.11 and one of my first activities was created a new Income Statement report for year 2016 (I created it from a saved report but I think this is irrelevant). I renamed the new report to its Spanish name: "Pérdidas y Ganancias al Cierre 2016". However, when I closed the preferences window of the new report, the name of report in its tab in the application window is shown as "P\303\251rdidas y Ganancias al Cierre 2016", non-ASCII characters. The report name has not actually changed (I can see "Pérdidas y Ganancias al Cierre 2016" in the report preferences). But the report name in the tab (of the report) is not showing non-ASCII characters. I must say that I have several reports in the same window, all of them created using previous versions of GnuCash. The report names of these previous reports are properly shown in their tabs. That is, the non-ASCII names of these reports are shown as they should. I closed GnuCash to see if the new report name is correctly shown after reopening the app. After rebooting, I saw the wrong name (only ASCII) in the tab and the report name has been changed to "P\303\251rdidas y Ganancias al Cierre 2016" in the preferences window of the report. After reopening, the names of the reports created before version 2.6.11 are shown using proper non-ASCII characters (that is, correctly). Thanks a lot.
I have noticed two important things: 1. Maybe this is not an issue with the last version (2.6.11). I have noticed that I have a report named "Perdidas y ganancias al Cierre 2015" (all characters are ASCII). Perhaps this issue started in any version released during 2015. 2. I have changed the name of the report "P\303\251rdidas y Ganancias al Cierre 2016" in the gcm file of the book and I can see the proper name "Pérdidas y Ganancias al Cierre 2016" now. So maybe the problem is related with the code that stores the report description in gcm files.
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution. The string was being passed through g_strescape to prevent a crash when non-printing characters were included. Unfortunately g_strescape also escapes all characters >= 0x80.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=760711. Please update any external references or bookmarks.