Greetings all, My vote is "no", or more specifically "not yet". After seeing how much work is involved in unicode, I think we're stretched thin enough just trying to make a good Roman alphabet search engine.
When 3.2.0b5 was released, there were lots of comments from 3.1.6 users that the digging speed is unacceptable. I vote that the next major project should be to improve the efficiency, in terms of speed, database size and (if possible) code size. Neal, you mentioned big improvements using STL. Do you have any sample code? If we choose to go with STL, then we could use their wchar strings and UTF-8 i/o, which would make the system nominally Unicode complient. Once someone actually wants to *use* ht://Dig for non-word-breaking scripts, then we/they/their-contacts can write the word breaking code. $0.02 Lachlan On Sat, 3 Jan 2004 06:44, Mike Holderness wrote: > Does the team want to (try to) recruit developers who can > work HtDig up into a full-blown Unicode system, dealing > with non-word-breaking scripts properly? -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
