Janine Sisk's bits of Fri, 26 Jul 2002 translated to: >I have a document with this: > ><meta name="dc.date.created" content="2000-07-20"> > >Now that I have applied that patch to get use_doc_date to work, it's showing >up on the results page as 07-19-2000. All the dates seem to be one day off.
The dc.date.* content is interpreted as if it were a Last-Modified header. As such, the GMT time zone is assumed. Furthermore, since only the date is specified, a time of 00:00:00 is used as a default. When the resulting date/time is displayed, it is converted to a local time zone. If you were to enable the iso_8601 attribute, you would see that the time differs from 2000-07-20T00:00:00 by the number of hours your time zone differs from GMT. Since you are, presumably, in the western hemisphere, that pushes the date back to the previous day. In order to correct the problem, you should convert the local document creation date to GMT and use that date as the content. If you add the time, ht://Dig expects it to be in the form "YYYY-MM-DD HH:MM:SS" (trailing time components are optional if you don't want to use minutes and/or seconds). I am not sure that this format is correct according to Dublin Core, or even according to ISO 8601 for that matter, but that is what the code wants. Jim ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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
