Actually, adding UTF-8 to an arbitrary locale might be dangerous. It should only be a temporary workaround, but should not make its way to a release. For instance, on fedora2, the Japanese locale doesn't have an utf8 counterpart. (By the way, Japanese translations of gnucash exist... so we must have some users running gnucash in Japanese).
prompt> locale -a | grep jp ja_JP.eucjp Didier. Le lun 17/10/2005 à 19:41, Derek Atkins a écrit : > A better solution would be to change the gnucash code to use > the g_locale_to_utf8() API in the gnucash locale settings. > We should /not/ force gnucash into a utf8 locale. > > -derek > > Christian Stimming <[EMAIL PROTECTED]> writes: > > > Oops, Neil, > > > > sorry for that -- my first complaint obviously was wrong. Turns out I > > didn't read the generate-gnc-script in full so that I didn't realize the > > commands are part of the here-document. So the "dependence on LANG at > > compile time" doesn't exist, and that is obviously a good thing. > > > > Nevertheless my second issue still remains, and I still think that this > > isn't the solution of the problem you're seeing. > > > > Christian _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
