According to "Baumeister, Christian (init)":
> Hello,
> we would like to write a long.html-template to view the date
> DC.Date.created or DC.Date.Modified in the result-set.
> The phanomen of this Code:
> 
> <dl><dt><strong><a
> href="$&(URL)">$&(TITLE)</a></strong>&nbsp;&nbsp;&nbsp;&nbsp;$(PERCENT)
> %
> </dt><dd>$(EXCERPT)<br>
> $(MODIFIED) $(SIZEK) kb *$(METADESCRIPTION)*
> </dd></dl>
> 
> ... is following:
> 
> Template display (long.html)
> // $(excerpt)
> 2001-03-29
> // $(modified)
> 30.04.2002 
> // $(METADESCRIPTION)
>  *2001-03-29*  
> 
> ... But we are thinking about, that this example result must be like
> this:
> 
> // $(excerpt)
> [The description of the dokument as text] 
> // $(modified)
> 2001-03-29 
> // $(METADESCRIPTION)
>  *[The description of the dokument as text, if a description metatag is
> there]*  
> 
> What is the Problem with this coding and configuration? Why did not
> display htdig the date, dc.date.created or dc.date.modified well. We
> would not use the systemdate for the display. We are using Release 3.1.6
> and we have configured sometimes the Configuration. For all tests we
> have made a new index. 
> 
> At last- the Configuration File for htdig.
> 
> presse.conf-Konfiguration
> 
> date_format:               %Y-%m-%d
> use_doc_date:                      true
> use_meta_description:        true
> server_wait_time:            0
> max_hop_count:               1
> max_prefix_matches:          100
> minimum_prefix_matches:      3
> keywords_meta_tag_names:     keywords DC.Publisher DC.subject DC.Creator
> description_meta_tag_names:  date DC.Date.Created DC.Date.Modified description
> 
> Please, help us for this Problem.
> Thank you very much!

The last attribute, description_meta_tag_names, is the cause of the
problem.  htdig 3.1.6 already parses dc.date tags, and these values
override the last-modified date of the document if use_doc_date is set.
By adding the date tag names to description_meta_tag_names, you're
allowing the last occuring such tag in the document to override the
meta description.

See http://www.htdig.org/attrs.html#description_meta_tag_names and pay
close attention to the description of this attribute.

I'm not sure why the dc.date in your document isn't setting the modified
date in the example you show above.  If you have a meta tag with a name of
date, dc.date or dc.date.created, it should work.  However, I just noticed
a typo on line 96 of htdig/HTML.cc, which will prevent it from recognizing
a dc.date.modified meta tag.  The patch below will take care of that bug:

--- htdig/HTML.cc.orig  Wed Jan  9 16:12:31 2002
+++ htdig/HTML.cc       Fri May 17 16:00:00 2002
@@ -93,7 +93,7 @@ HTML::HTML()
 
     // These are the name values of meta tags that carry date information.
     metadatetags.IgnoreCase();
-    metadatetags.Pattern("date|dc.date|dc.date.created|dc.data.modified");
+    metadatetags.Pattern("date|dc.date|dc.date.created|dc.date.modified");
 
     // These are the name values of meta tags that carry descriptions.
     StringList descrNames(config["description_meta_tag_names"], " \t");


-- 
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)

_______________________________________________________________

Hundreds of nodes, one monster rendering program.
Now that�s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to