On Tue, 2003-11-25 at 06:57, Derek Atkins wrote: > Scott Oonk <[EMAIL PROTECTED]> writes: > > > 2.) Get rid of the "wide character set" and use utf-8 for the user I/O > > as well as the internal calculations. > > #2 is the correct option. We should just keep everything in UTF8.
Agreed, 100%. > The hard part is going to be converting the existing XML and database > data from whatever it's currently using to UTF8. We don't currently include an "encoding" in the XML data file. That could be used as a trigger to ask the user for the old encoding and then convert the data to UTF-8. A nice touch would be to scan the file first looking for any characters with the high order bit set to see if conversion is needed in the first place. David _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
