[jira] Updated: (TAPESTRY-1852) Document Supported locales in AjaxShellDelegate

["Andreas Andreou (JIRA)" <de...@tapestry.apache.org>]

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

Andreas Andreou updated TAPESTRY-1852:
--------------------------------------

          Component/s:     (was: JavaScript)
                       Documentation
        Fix Version/s: 4.1.4
             Assignee: Andreas Andreou
             Priority: Minor  (was: Major)
           Issue Type: Task  (was: Bug)
    Affects Version/s:     (was: 4.1.4)
                       4.1.3
              Summary: Document Supported locales in AjaxShellDelegate  (was: Supported locales in AjaxShellDelegate)

> Document Supported locales in AjaxShellDelegate
> -----------------------------------------------
>
>                 Key: TAPESTRY-1852
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1852
>             Project: Tapestry
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 4.1.3
>            Reporter: Igor Drobiazko
>            Assignee: Andreas Andreou
>            Priority: Minor
>             Fix For: 4.1.4
>
>
> AjaxShellDelegate#isLocaleSupported is used to check whether the locale is supported. For what ever reason the default list of pre-bundled dojo supported locales is to short. 
>     protected String[] SUPPORTED_LOCALES = { "en-us", "de-de", "de", "en-gb",
>                                              "es-es", "es", "fr-fr", "fr", "zh-cn",
>                                              "zh-tw", "zh" , "it-it", "it", "ja-jp",
>                                              "ja", "ko-kr", "ko", "pt-br", "pt", "en", "xx"};
> I have seen that this check was added to fix https://issues.apache.org/jira/browse/TAPESTRY-1551 but I have another scenario.
> I want to use dojo.i18n.number.parse(value, djConfig.locale); this parsing method uses internally dojo.i18n.number.FORMAT_TABLE
> dojo.i18n.number.FORMAT_TABLE support much more locales. The only one possibility to get the locale on client side is djConfig.locale
> But because of the mentioned limitation djConfig.locale cannot be used for number formating.
> Is it possible to remove this check or at least to complete the list? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org