At 2:52 PM -0600 1/9/02, Gilles Detillieux wrote: > > Just to be clear.. do you mean the release is moved back or that >> the feature is postponed until the next release? I'm guessing the latter. > >Yes, I believe Geoff meant the latter
Yes, I did--but as Gilles mentions, we're not particularly rigid about enforcing a deadline or even a real code-freeze if there are obvious reasons otherwise. Certainly you have to draw the line somewhere, but important fixes/changes/features are more likely to get accepted by a developer vote than minor things (that could be added to the next release). >you use the latest 3.2.0b4 snapshot as your starting point, or better >yet the htdig-3-2-x branch of the htdig CVS tree on SourceForge. Actually, I'm about to expire the mainline tomorrow--this won't alter the htdig-3-2-x branch, but it will at least offer other options. It's obvious up to a vote whether we want to switch development CVS trees back to the mainline and revisit the htdig-3-2-x branch as we get to 3.2.0 final candidates. > > I'd be happy to assist in syncing with mifluz. This would certainly help in meeting your calendar goal. I'd be glad to bring you up to speed on what needs to happen for that. Fortunately some of the hooks are left from my previous attempt. (i.e. there shouldn't be much need for autoconf/autoheader changes.) I'd be glad to point towards what needs to happen. The first thing is to take a look at the mifluz example code to see how the word indexing and searching is currently performed. I'd then take a look at the htcommon/HtWord* classes and see what needs to be changed here. This is a large extent of the ht://Dig side of the mifluz API. Most of the htword/ and db/ directories are just the mifluz code itself. At 8:20 PM -0700 1/9/02, Neal Richter wrote: >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. Ah. As you're well aware, if we don't develop it ourselves, it must be GPL compatible. I'd be interested to know if there are any Asian-aware "spelling checkers" or Asian-aware word processors that parse words under the GPL or the like. -Geoff _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
