Earlier today, I wrote...
> According to Geoff Hutchison:
> > On Thu, 17 Oct 2002, Gilles Detillieux wrote:
> > > 3) My own lack of time in being able to get the 3.1.6 fixes/updates
> > > forward ported to 3.2.
> > 
> > If you have a list of particular things, it would help significantly. I'll
> > check through the mailing list, but if you have a list somewhere it'd save
> > some time.
> 
> I haven't updated the list since I sent it to Jessica Biola back in August.
> Here it is again...
...
>    - multi-excerpt patch (max_excerpts attribute) for htsearch/Display.cc
>    - better handling of htdig -m option
>    - add startyear et al. to defaults.cc
>    - make startyear et al. handle relative date ranges in Display.cc
>    - fuzzy endings patch and updated english.0 file
>    - get updated external parser scripts into contrib directory
>       (fix eof handling bug in .pl scripts)
>    - list-all feature in htsearch for a query of * or prefix_match_character
>    - ignore_dead_servers attribute
>    - description_meta_tag_names attribute
>    - ignore_alt_text attribute
>    - translate_latin1 attribute, with hooks into SGMLCodec class
>    - search_rewrite_rules attribute
>    - anchor_target attribute
>    - search_results_contenttype attribute
>    - boolean_keywords attribute
>    - boolean_syntax_errors attribute
>    - multimatch_method attribute (still VERY buggy in 3.1.6 though)
...
> Note that some items in the list may already be in the 3.2 cvs.  I just
> haven't checked yet.  Also, a close look at the 3.1.6 ChangeLog may reveal
> bug fixes I've missed in both the list above and the 3.2 cvs.

OK, scratch the first sentence in the paragraph above.  I just looked over
the list, and I'm fairly certain that none of these are in 3.2 cvs yet.
Lachlan's patch to defaults.cc will add startyear et al. to defaults.cc,
but it doesn't include the full description that 3.1.6's attrs.html file
has for these attributes.

And in a separate message, Jim Cole wrote...
> Gilles - Please let me know what I can do to help you with all
> the 3.1.x and 3.1.x->3.2 issues that seem to fall into your
> court. I am a proficient C/C++ programmer. My knowledge of the
> auto* tools is minimal, but I have a book :) I can find my way
> around CVS.
> 
> I can't promise a lot as my free time is nearly non-existent at
> the moment, not to imply that the same is not true for others
> around here. However if you have a couple tasks to toss my way, I
> will see what I can do. I am certainly not going to make any
> significant contributions by forever sticking to the "not enough
> time" excuse ;)

Well, since you're offering, I wouldn't mind a hand in going through
the 3.1.6 ChangeLog to see what other changes need to go in 3.2 still.
I'd like to add to the list above to make it a complete list of 3.1.x
things still needed for 3.2.

If that's not too unappealing a task to start with, that would be a good
starting point.  Apart from that, probably all the htsearch changes
and htsearch-related attributes in the list above would be the easier
ones to go into 3.2, and probably the most pressing because during 3.1.6
development I deliberately held back parallel changes to 3.2's htsearch,
because of other changes that were to take place there, but never fully
materialized.  The htfuzzy, endings and contrib changes should all be
pretty straightforward too.  How's that for starters?  If you want help
or clarification on any of these, please let me know.  And regardless of
what you do end up working on, thank you for offering!

I'll look after these two...
>    - better handling of htdig -m option
>    - translate_latin1 attribute, with hooks into SGMLCodec class
because I have a pretty clear idea in mind of what I want to do with those.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to