[jira] [Updated] (DAFFODIL-2823) time zone "z" specifier does not work properly

["Mike Beckerle (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Beckerle updated DAFFODIL-2823:
------------------------------------
    Summary: time zone "z" specifier does not work properly  (was: time zone "z" specifier does not work)

> time zone "z" specifier does not work properly
> ----------------------------------------------
>
>                 Key: DAFFODIL-2823
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2823
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.4.0
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> The time zone string  "EST" is parsed by calendarPattern charater "z", and becomes ISO standard "-05:00" on parse, but "GMT-5" on unparse.
> This happens despite dfdl:calendarLanguge="en_US". That is, the problem is that the unparse should produce "EST", but does not. 
> The locale is needed to implement "z" time zone format because some of these 3-letter timezone specifiers are ambiguous, so the locale must be known to disambiguate them when parsing. 
> For example CST can be "Central Standard Time" (North America), "Cuba Standard Time" or "China Standard Time", and is widely used for "Central Standard Time" (Australia) according to [https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations]
> So when parsing "z" one must use the locale. When unparsing it's not so ambiguous, but Daffodil doesn't appear to use the locale information.
> Per the ICU documentation here:  [https://icu.unicode.org/design/formatting/timezone/icu-4-8-time-zone-names]
> The "z" needs locale information, and several of the other specifiers also need it. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)