> >much work is involved in unicode, I think we're stretched thin enough > >just trying to make a good Roman alphabet search engine. > > I agree.
Definetly agree. > I am fascinated by migrating the whole code to the use of the standard > library features, particularly strings, streams and overall containers (and > related iterators and eventually algorithms). > > However I'd put it in a feature list of an hypothetical 3.3 or even 4 > release together with other things (maybe threads, multi-output database - > e.g. PostgreSQL, MySQL, etc.) Yep... although we can do it in pieces.. there are some base level classes that implement simple data structures that the STL provides... we can look at replacing some of the lower impact ones first. > >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. We can always keep an eye out for software... sooner or later someone will need an open source project to do this..... and only a fluent speaker is going to be able to make it great. Neal Richter Knowledgebase Developer RightNow Technologies, Inc. Customer Service for Every Web Site Office: 406-522-1485 ------------------------------------------------------- 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_id=1278&alloc_id=3371&op=click _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
