[Gnucash-changes] Fixing UTF-8 support in X sessions

Derek Atkins warlord at MIT.EDU
Mon Oct 17 16:01:51 EDT 2005


Quoting Christian Stimming <stimming at tuhh.de>:

>> prompt> locale -a | grep jp
>> ja_JP.eucjp
>
> Yes, thanks for pointing this out, and this is certainly true for any of the
> gnucash series. So the original patch cannot go into any release.

Well, I backed out the g2 change already.  I agree, it's not safe
to "upgrade" to a .utf8 locale -- that may not always exist.
We should use internal APIs to do translations.

> But concerning a gnucash-1-8-branch workaround, I think I'll add this in a
> commented-out form, so that people can be pointed to that existing setting.
> ("go to file /usr/bin/gnucash and comment out that line after the comment
> that says 'comment out the next line'")

Is it necessarily dangerous to remove 'utf8' from the locale?  Are
there any locales foo.utf8 for which locale 'foo' does not exist?
I can't think of any -- I would think that downgrading from .utf8
to non-utf8 would always be safe, no?

> Christian

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available



More information about the gnucash-devel mailing list