Mailing-List: contact deltaspike-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gerhard.petracek@gmail.com
 designates 74.125.82.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <518C2273.6080604@gmail.com>
References: <518C0D26.6070006@gmail.com>
 <CAGJtJfFZ3sb0txKZgi8hxReKOKjaUS8H-djAr1UF7TXBhe6biQ@mail.gmail.com>
 <CAGJtJfHaTGF8eWq+FDVHR7VixQmP+2qtt72N1GgpAh+8LNBP-A@mail.gmail.com>
 <518C2273.6080604@gmail.com>
From: Gerhard Petracek <gerhard.petracek@gmail.com>
Date: Fri, 10 May 2013 02:04:30 +0200
Message-ID: 
 <CAGJtJfH-A+f=j_qi_HanRqzN1oxw7sw7_T8Qq9+HXtAHkW8cGQ@mail.gmail.com>
Subject: Re: I18N Module
To: deltaspike-users@incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c2469277610b04dc51eab3

--001a11c2469277610b04dc51eab3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

like MessageContext#messageSource(/*list*/), we would need
MessageContext#supportedLocale(/*list*/)
-> the MessageResolver has to do the correct handling (like it does for
message-sources).

that wouldn't solve your use-case (due to >multiple dynamic< fallbacks) ->
you would need a custom MessageResolver.

regards,
gerhard


2013/5/10 Christian Beikov <christian.beikov@gmail.com>

> If you don't localize your texts properly you will always sooner or later
> end up with differently localized messages.
> In my application I know for every set of texts, in what languages they
> are available. I also have a prioritized set of locale preferrences that
> are orderd like:
>
> 1. user locale
> 2. company locale
> 3 - (n - 1): locales sent by the browser
> n. default locale
>
> I resolve the locale that should be used by considering these two sets an=
d
> returning the best match. When the locales that are supported are not kno=
wn
> it's just not possible to use my resolving algorithm. So probably somethi=
ng
> like the following would suite the LocaleResolver interfaces a bit more?
>
> public Locale getLocale(Collection<Locale> supportedLocales);
>
>
> Mit freundlichen Gr=FC=DFen,
> ------------------------------**------------------------------**
> ------------
> *Christian Beikov*
> Am 10.05.2013 00:09, schrieb Gerhard Petracek:
>
>> i've attached a first draft to [1].
>>
>> regards,
>> gerhard
>>
>> [1] https://issues.apache.org/**jira/browse/DELTASPIKE-360<https://issue=
s.apache.org/jira/browse/DELTASPIKE-360>
>>
>>
>>
>> 2013/5/9 Gerhard Petracek <gerhard.petracek@gmail.com>
>>
>>  hi christian,
>>>
>>> you could end up with a mixture of messages easily.
>>> what you would need is a LocalResolver which checks the current locale
>>> (based on a list of supported locals + a default locale).
>>>
>>> regards,
>>> gerhard
>>>
>>>
>>>
>>> 2013/5/9 Christian Beikov <christian.beikov@gmail.com>
>>>
>>>  Hello there,
>>>>
>>>> I was just about to configure the I18N module for my needs and hit a
>>>> limitation. The LocalResolver can only return a single Locale which is
>>>> somehow bad. Normally you have various preferences. Are you going to a=
dd
>>>> something like:
>>>>
>>>> public Iterable<Locale> getLocales()
>>>>
>>>> to LocaleResolver or is the current design intended to be kind of fina=
l?
>>>> --
>>>>
>>>> Mit freundlichen Gr=FC=DFen,
>>>> ------------------------------****----------------------------**--**
>>>> ------------
>>>> *Christian Beikov*
>>>>
>>>>
>>>
>

--001a11c2469277610b04dc51eab3--