cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COCOON-1648) I18nTransformer add support for ISO8601
Date Wed, 01 Mar 2006 07:42:39 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1648?page=all ]

David Crossley updated COCOON-1648:
-----------------------------------

    Bugzilla Id:   (was: 37094)
     Other Info: [Patch available]
    Description: 
See http://www.w3.org/TR/NOTE-datetime for details about ISO 8601

The main idea of ISO 8601 is to have a variable date format, with variable
granularity.  Currently I18nTransformer only supports date formats with a fixed
pattern.

I propose to add in Cocoon two classes from W3C's Jigsaw.  DateFormatUtils from
Jakarta Commons cannot be used because only the formatting part is implemented.
See
http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/time/DateFormatUtils.html

A patch against I18nTransformer is also provided: when encountering <i18n:date
src-pattern="iso8601"> the special date parser is invoked.  Actually this patch
only provides the parsing part, not the ISO 8601 formatting part.  Because
I18nTransformer is intended for presenting a view to the end-user, it is rarely
needed to present an ISO-8601-formatted date.

  was:
See http://www.w3.org/TR/NOTE-datetime for details about ISO 8601

The main idea of ISO 8601 is to have a variable date format, with variable
granularity.  Currently I18nTransformer only supports date formats with a fixed
pattern.

I propose to add in Cocoon two classes from W3C's Jigsaw.  DateFormatUtils from
Jakarta Commons cannot be used because only the formatting part is implemented.
See
http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/time/DateFormatUtils.html

A patch against I18nTransformer is also provided: when encountering <i18n:date
src-pattern="iso8601"> the special date parser is invoked.  Actually this patch
only provides the parsing part, not the ISO 8601 formatting part.  Because
I18nTransformer is intended for presenting a view to the end-user, it is rarely
needed to present an ISO-8601-formatted date.


> I18nTransformer add support for ISO8601
> ---------------------------------------
>
>          Key: COCOON-1648
>          URL: http://issues.apache.org/jira/browse/COCOON-1648
>      Project: Cocoon
>         Type: Improvement
>   Components: * Cocoon Core
>     Versions: 2.1.8
>  Environment: Operating System: other
> Platform: Other
>     Reporter: Jean-Baptiste Quenot
>     Assignee: Jean-Baptiste Quenot
>     Priority: Minor
>  Attachments: cocoon-i18n-patch, w3c-date.tar.gz, w3c-date.tar.gz
>
> See http://www.w3.org/TR/NOTE-datetime for details about ISO 8601
> The main idea of ISO 8601 is to have a variable date format, with variable
> granularity.  Currently I18nTransformer only supports date formats with a fixed
> pattern.
> I propose to add in Cocoon two classes from W3C's Jigsaw.  DateFormatUtils from
> Jakarta Commons cannot be used because only the formatting part is implemented.
> See
> http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/time/DateFormatUtils.html
> A patch against I18nTransformer is also provided: when encountering <i18n:date
> src-pattern="iso8601"> the special date parser is invoked.  Actually this patch
> only provides the parsing part, not the ISO 8601 formatting part.  Because
> I18nTransformer is intended for presenting a view to the end-user, it is rarely
> needed to present an ISO-8601-formatted date.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message