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.
The hard part is going to be converting the existing XML and database
data from whatever it's currently using to UTF8.
> According to David, the main places this impacts is the register gui
> code and the reading/writing of the xml data file. I poked around the
> register code a bit and have a fair idea of the work needed to be done
> there, but I don't really know which of the two options would be best.
It also affects some of the option "save" code and also the postgres
i/o. Granted, some of it might be a no-op, but you should still look
at it. :)
> Thanks,
>
> Scott
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
