On Wed, Aug 27, 2003 at 04:05:34PM -0700, David Hampton wrote: > > Few questions to lead developers: > > > > 1. How about i18n in gnucash? > > Currently XML data file has no `encoding' attribute in <?xml?> clause > > and this means UTF-8 encoding. But non-latin1 (eight-bit in > > single-byte charset) characters are stored as '&#code;' where 'code' > > is character's code from local user locale, not from UTF-8! > > This is absolutely BAD WAY. > > Yes, its a problem. One of several issues with international character > support. Gnucash has support for "wide" character sets, but I've never > tested it to see how well it works. > > > 2. How about moving to Gnome2? > > We're working on it.
Good news! > > Who can tell me - how much code needs to be patched for proper i18n > > (storing non-Latin1 characters in XML using right way and proper > > displaying it in reports)? > > Haven't investigated yet. The gnome2 port is a higher priority and > gnome2 has better utf-8 support than gnome1. I expect the gnome2 port > of gnucash to be utf-8 clean so that we don't have the current set of > problems. I hope you remember about user's data. We need a conversion routine for it after G2-version of Gnucash will be released. -- WBR, Andrey Brindeew. "No one person can understand Perl culture completely" (C) Larry Wall.
pgp00000.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
