Am Montag, 17. Oktober 2005 21:05 schrieb Didier Vidal:
> 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
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.
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'")
Christian
>
> 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
