Greetings Neal, "ASAP" is quite strong... I vote for "after 3.2.0 is released", and perhaps "after 3.2.1 bug-fix is released".
To me, the bloated database / slow digging seems a more major problem. Feedback from 3.2.0b5 showed that it was a real disincentive for 3.1.6 users to migrate, and that would mean someone needs to support the legacy 3.1.6 code indefinitely. As a side issue, there is debate about whether UTF-8 (rather than wchar) is suitable for internal representation. However, once we encapsulate all of our string handling behind a simple API, we will be able to change libraries easily. Cheers, Lachlan On Tue, 6 Jan 2004 10:15, Neal Richter wrote: > Note that I do think we should look at replacing our string > class with a UTF-8 one ASAP and completely purge all libc (str*) > calls and dependencies on char * for anything other than display > (HTML, stdout). -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
