[jira] Resolved: (WICKET-451) Load translations more dybnamically

["Eelco Hillenius (JIRA)" <ji...@apache.org>]

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

Eelco Hillenius resolved WICKET-451.
------------------------------------

    Resolution: Won't Fix
      Assignee: Eelco Hillenius

date-time didn't exist for Wicket 1.2, so you must be refering to the date picker component in Wicket extensions of 1.2. We discontinued development of that component for 1.3 and moved it to a Wicket stuff project. New date components are available in the wicket-datetime project. Localization is yet to be implemented for that project, though it should have enough hooks to do it by yourself.

I'm happy to provide you access to the wicket-stuff project so that you can maintain the old datepicker.

> Load translations more dybnamically
> -----------------------------------
>
>                 Key: WICKET-451
>                 URL: https://issues.apache.org/jira/browse/WICKET-451
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-datetime
>    Affects Versions: 1.2.5
>            Reporter: Logi Ragnarsson
>         Assigned To: Eelco Hillenius
>            Priority: Minor
>
> Currently translations for DateTime are loaded by lookiing up the current locale in the static localeToLanguageReference. However, the content of the map is entirely predictable, except that some translations may be missing.
> I suggest dropping the map and attempting to load translations based on the full locale, then language+country and finally language so that new translations can be added without having to update the private map. This sort of fallback logic is already implemented in DatePickerSettings.getLanguageFromMap and AbstractResourceStreamLocator.locate

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