You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (Jira)" <ji...@apache.org> on 2020/11/21 14:40:00 UTC

[jira] [Commented] (WW-4929) Fallback i18n Locale

    [ https://issues.apache.org/jira/browse/WW-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236676#comment-17236676 ] 

Lukasz Lenart commented on WW-4929:
-----------------------------------

I took a look and it would be possible to support {{Accept-Language}} header, but it requires a large refactoring of the {{LocalizedTextProvider}} - basically to allow accept a set of {{Locale}} instead just one Locale. This would be a breaking change.

> Fallback i18n Locale
> --------------------
>
>                 Key: WW-4929
>                 URL: https://issues.apache.org/jira/browse/WW-4929
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.5.14.1
>            Reporter: Kai Denzel
>            Priority: Major
>             Fix For: 2.6
>
>
> What i noticed is, when i set the perfered languages in my browser for example in this order:
> fr - francais
> de - german
> en - english
> The framework will set the ActionContext.getLocale() to fr. Then the framework will look for resources for francais, and if this locale resources do not exist, the framework will look for the system locale. If the system locale in this example is en, the german resources will be overlooked.
> I mean the HTTP-Header "Accept-language" has an Array of locales. So why not fallback to the next selected if the first Locale does not exist? 
> Is it possible, to make the framework ready for fallback?
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)