Gnome2 UTF-8 handling
hampton at employees.org
Mon Dec 1 01:26:31 CST 2003
On Tue, 2003-11-25 at 06:57, Derek Atkins wrote:
> Scott Oonk <s.oonk at comcast.net> 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.
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20031201/1c5d08d3/attachment.pgp
More information about the gnucash-devel