[jira] [Updated] (FLEX-17334) Bugs in i18n

["Justin Mclean (JIRA)" <ji...@apache.org>]

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

Justin Mclean updated FLEX-17334:
---------------------------------

    Labels: easytest  (was: )
    
> Bugs in i18n
> ------------
>
>                 Key: FLEX-17334
>                 URL: https://issues.apache.org/jira/browse/FLEX-17334
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: i18n : Formatter Support
>    Affects Versions: Adobe Flex SDK 3.2 (Release)
>         Environment: Affected OS(s): Windows
> Browser: Firefox 2.x
> Language Found: English
>            Reporter: Adobe JIRA
>              Labels: easytest
>
> Steps to reproduce:
> 1. Run teste.mxml
> FB build: 3.0.2.214193
> I compiled with -locale=en_US,pt_BR -allow-source-path-overlap=true
> Resource Bundle file formatters.properties of en_US and pt_BR possess the lines:
>          currencyFormatterPrecision=2
>          numberFormatterPrecision=2 
>  Actual Results:
>          It is initiating with pt_BR would not have to be en_US? 
>          To modify the data of grid is necessary to use the line adg.dataProvider.refresh () is not bindable?
>          NumberFormatter and CurrencyFormatter show precision -1 with en_US.
>          Date 13/10/2008 doesn't appear in pt_BR. The problem is at dateFormatter. 
>                     AdvancedDataGridColumn.itemToLabel passes to applyFormatting() the return of itemToLabelWithoutFormatting that is toString() of date (Month = Oct always). DateFormatter.parseDateString tries to find the three first letters of the content of DateBase.mx_internal::defaultStringKey that it is contained in the resource bundle file SharedResources.monthNames that at pt_BR é: Janeiro,Fevereiro,Março,Abril,Maio,Junho,Julho,Agosto,Setembro,Outubro,Novembro,Dezembro. 
>                     Out != Oct

--
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