The localized js validation must be there, not very serious solution if it
supports server side localization, but not client side :)
+1 too for localized translators and js validation.
Marcelo Lotif-2 wrote:
>
> And me too.
> Here, we're using a javascript + onToClient and
ut the discussion here also deals with the Javascript
validation. Should we open a new JIRA just for the JS part?
I think localized translators implicate localized client side validation on fields, were those
translators are used. So there is no need for a seperate issue.
As a side note, when I
e ago...
> >
> >
> > > -Ursprüngliche Nachricht-
> > > Von: Ulrich Stärk [mailto:[EMAIL PROTECTED]
> > > Gesendet: Montag, 6. Oktober 2008 16:32
> > > An: users@tapestry.apache.org
> > > Betreff: Localized Translators - again
Em Mon, 06 Oct 2008 11:32:01 -0300, Ulrich Stärk <[EMAIL PROTECTED]>
escreveu:
https://issues.apache.org/jira/browse/TAPESTRY-2457 (in fact I tried to
Voted and watching this issue. But I think its description speaks only of
Translators, but the discussion here also deals with the Javascri
alization is still such an issue, this will be really hard...
>
> Max
>
> PS: I already voted long time ago...
>
>
> > -Ursprüngliche Nachricht-
> > Von: Ulrich Stärk [mailto:[EMAIL PROTECTED]
> > Gesendet: Montag, 6. Oktober 2008 16:32
> > An: users@
-Ursprüngliche Nachricht-
> Von: Ulrich Stärk [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 6. Oktober 2008 16:32
> An: users@tapestry.apache.org
> Betreff: Localized Translators - again
>
> Am Sa, 13.09.2008, 22:36, schrieb Howard Lewis Ship:
> > On Sat, Sep 13, 2008
Am Sa, 13.09.2008, 22:36, schrieb Howard Lewis Ship:
> On Sat, Sep 13, 2008 at 2:54 AM, Ulrich Stärk <[EMAIL PROTECTED]> wrote:
>> - localization for translators is still missing:
>> https://issues.apache.org/jira/browse/TAPESTRY-2457 (in fact I tried to
>> bring this to your attention several time
Hi,
Yes, you can just inject Request and PersistentLocale.
-Filip
Ulrich Stärk skrev:
In order to have localized Translators, Howard suggested to override the
default TranslatorSource service and add my own Translators to it. If I
want to have localized Translators I have to take into
Hi List,
I'd like my users to be able to input data in their respective locale.
For example in most european countries you use the ',' to seperate the
decimal places from the integer part of a number.
For a quick workaround I'm using a patched version of Tapestry wich adds
a Locale parameter
