On Wed, 9 Jan 2002, Gilles Detillieux wrote:
> Parts of it are fully functional now, but some parts are still in early
> development (e.g. Cookie support). Whether it's solid for you depends
> on what parts you use and what parts you don't.
I will be mostly treating htdig as an index/query API. I don't
yet know just how much htdig calls vs direct mifluz calls..
>
> > I'd be happy to assist in syncing with mifluz.
>
> Great, that's probably the most urgent change to 3.2 that's needed to
> improve its reliability. I wouldn't say that it's impossible to get
> 3.2 reasonably solid by mid-February, but it is an awfully tight
> deadline!
I'll look and see what files need to be updated. The mifluz
site looks like it hasn't been updated since july.. the cvs tree is very
quiet.
> I'd caution that any htdig development should be done in "clean-room"
> conditions, i.e. not by anyone who's signed the NDA and seen
> the proprietary code, to avoid any licensing pitfalls. (See
> http://www.linuxjournal.com/article.php?sid=5496 for a cautionary tale.)
Absolutely.
I'm not the main internationalization developer. We don't have
access to the source code of the Basis Tech tools, we use it as an API for
transcoding, etc.
Thanks
--
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
