GNOME Bugzilla – Bug 102048
accentuated chars cut displayed strings
Last modified: 2018-06-29 20:23:44 UTC
about version 1.7.6 accentuated characters (sorry, I'm French) shown in register windows cut the string which is displayed e.g. with "Dépense" you have "D" alone displayed, but if you select it you have "Dpense" written instead. Maybe a problem of "locale"? However it used to work with gnucash 1.6.6.
Where do you enter the accentuated characters and where do you get the display problems? I.e., in the register window, or in the text reports, or in the graphical reports?
The accentuated chars come from my account file with version 1.6.6. in the XML file accentued chars look like "Épargne". If I reopen the file under 1.7.6, the lines in the register windows are cut after accentuated chars. It may be so for reports as well, I'm not sure.
The same problem occurs when new 'accentuated chars' are typed in the register windows. These chars are not display, although they are in other windows (e.g. account tree).
I hand edited my data file to replace some 'e' characters with the e-acute character "é". If I use the fr_FR locale these show up correctly in both the account tree window and the register window, in both Gnucash 1.6 and CVS. If I use the fr_FR.UTF-8 locale, this fails in both places in both versions.
Hi, I have a similar problem with accentuated characters on the Mac OS X version 1.8.9; Putting "achat légumes" in a description field records the whole string, but only displays "achat l" ... If you need more informations on this, or need me to test something, please let me know: Olivier Kaloudoff <kalou@kalou.net>
I have this behaviour when I am using a locale that is supported by linux, but is not supported by X11. When I was using LC_CTYPE=hu_HU.utf8, I had this same behaviour. For some time I am using en_US.UTF-8 just because of this gnucash issue, and it is fine. When I start gnucash from a konsole window, I get Gdk-WARNING **: locale not supported by Xlib, locale set to C But the behaviour is different from the behaviour that I have with my locale set to C, because if I unset my LC_CTYPE, I see the accented characters and the rest of the description. However, it seems that texts entered with different LC_CTYPE cause trouble, ex. I have strings where the accented characters are hidden, and in reports I have some two characters printed (I suppose UTF8 codes) but the display shows them as separate. (I am quite surprised about this by the way, I thought no matter how I enter a text, it will always be stored in some generic way in the file, like HTML encoded (the é stuff) or UTF8) So right now the display of the same file varies according to the viewer's locale settings. I suggest using en_US.UTF-8, as it works.
*** This bug has been marked as a duplicate of 112091 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=102048. Please update any external references or bookmarks.