[Zope-PTK] problem with pending review

Tres Seaver tseaver@digicool.com
Tue, 24 Oct 2000 12:13:29 -0400 (EDT)


On Tue, 24 Oct 2000, Joachim Schmitz wrote:

> 
> On Tue, 24 Oct 2000, Tres Seaver wrote:
> 
> > Joachim Schmitz wrote:
> <snipp>
> > Thanks for reporting this -- a patch for this problem (as well as a
> > similar
> > one) is in the PTK Tracker:
> > 
> >   http://www.zope.org/Products/PTK/Tracker/114
> > 
> > On a related note:  I would like some community feedback on the
> > handling of dates in the DublinCore.  The current implementation
> > always returns ISO-style strings for the date queries 
> > (Date/CreatedDate/EffectiveDate/ModifiedDate/ExpirationDate).
> > 
> > 
> > I made this choice because the DublinCore spec is mainly about
> > interoperability with other systems, and returning a Zope DateTime
> > object won't get us a good mark for "works and plays well with
> > others."  However, the downside is that the internals of the PTK
> > need to access some of the same items, but as *real* dates.  We
> > could play funny games with the naming (e.g., add a method,
> > 'effectiveDate' which returned the DateTime object), but that feels
> > clunky to me.
> > 
> > Any suggestions?
> 
> I think it is ok for the default format, where would I localize it, if I
> want to make a german version.

The DublinCore interface is declared in the PTKBase/interfaces
directory, and implemented in PTKDemo/DemoDublinCore.py.  It
currently uses the ISO() method of DateTime to render the date
as a string -- perhaps you could patch the class to allow the
installation of a different formatter?

Tres.
-- 
===============================================================
Tres Seaver                                tseaver@digicool.com
Digital Creations     "Zope Dealers"       http://www.zope.org