So, what I was thinking, is that we should look for ".UTF-8" in the LANG variable in the initial script bin/gnucash, and if found, strip it off.
Is my solution terrible and ugly? Yes.
Is there a better solution? Probably. I'm all ears.
Is this the best solution?
No, the best solution is apparently to wait for the gnome2 port, which may be a while before it is available to the masses in their favorite distros. We need a solution now.
References:
[1] Run "LANG=en_US.UTF-8 gnucash" on the command line, create some accounts with accented characters and open a register window. Watch the error messages fly! Opening this register window takes ~5x longer because of these error messages when you have many accounts. This works with any .UTF-8 language, not just en_US.
[2] UTF-8 GnuCash bugs: http://bugzilla.gnome.org/show_bug.cgi?id=102059 http://bugzilla.gnome.org/show_bug.cgi?id=100845 http://bugzilla.gnome.org/show_bug.cgi?id=105345 ...and possibly... http://bugzilla.gnome.org/show_bug.cgi?id=84604
-- -**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*--- Jon Lapham <[EMAIL PROTECTED]> Rio de Janeiro, Brasil Work: Extracta Mol�culas Naturais SA http://www.extracta.com.br/ Web: http://www.jandr.org/ ***-*--*----*-------*------------*--------------------*---------------
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
