You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2013/04/19 00:44:15 UTC
[jira] [Updated] (FLEX-33504) Some dateFormat locale properties not
well displayed by DateField
[ https://issues.apache.org/jira/browse/FLEX-33504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Mclean updated FLEX-33504:
---------------------------------
Priority: Major (was: Critical)
> Some dateFormat locale properties not well displayed by DateField
> -----------------------------------------------------------------
>
> Key: FLEX-33504
> URL: https://issues.apache.org/jira/browse/FLEX-33504
> Project: Apache Flex
> Issue Type: Bug
> Components: i18n : Formatter Support, Internationalization, l10n: Translations, mx: DateField
> Affects Versions: Apache Flex 4.9.0
> Reporter: Yann Cabon
> Assignee: Justin Mclean
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The DateField has its own Date formatting function that doesn't handle every pattern.
> As an example a Date (in en_US 12/31/2013) will appear 3112122013 in several languages.
> The affected locales are:
> fr_FR
> nb_NO
> nl_NL
> sv_SE
> The issue is due to the month format : MMM declared in locales/{locale}/SharedResources.properties
> The DateField.dateToString function could consume all the M not just the second one.
> Updating the dateFormat properties can solve this but could have impacts on other components.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira