[threeten-dev] New time zone format patterns in LDML/CLDR

[Stephen Colebourne]

On 16 January 2013 22:41,  <yoshito_umaoka at us.ibm.com> wrote:
> As I mentioned last week, CLDR TC had discussed about new time zone format
> patterns based on Java/JSR-310 proposal. In this morning, we had a
> discussion about the remaining item (time zone ID) and reached to a
> conclusion. Our conclusion is to use pattern "VV" for time zone ID,
> redefine already semantically deprecated "V" for CLDR short time zone ID
> (BCP 47 locale extension - time zone value) and new pattern "VVV" for time
> zone's exemplar location. In other words, we still want to reserve 'I' for
> future enhancement.

I'm happy to swap JSR-310 to VV for time-zone ID.

> I updated the design document -
> http://sites.google.com/site/cldr/development/development-process/design-proposals/time-zone-offset-patterns
> These new date format patterns should be included in UTR#35 LDML for CLDR
> 23 release in March.
>
> Of course, JSR-310 does not need to use the same definition, but if
> possible, it would be nice if JSR-310 can use the same definition
> (probably, just "VV" for now).
>
> I think the distinction between 'X' and 'x' is practically more useful and
> I'd propose JSR-310 (and also, Java SimpleDateFormat)  to accept 'X' and
> 'x' patterns as is.

The X/x definitions look good. I like them. They will involve slightly
more tweaking on our end to make them work, but thats OK.

> Anyway, If you have any comments, please let me know. We might still make
> some minor adjustments if there are any strong objections from JSR-310
> community.

The remaining items were the padding "p" modifier and the use of # for
fraction control. Any others?

Stephen