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 onParseClient metho
Thiago H. de Paula Figueiredo schrieb:
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 discus
+1 for locale aware Javascript validation
2008/10/6 Marcelo Lotif <[EMAIL PROTECTED]>
> And me too.
> Here, we're using a javascript + onToClient and onParseClient methods to
> automatically format numbers and currencies to our locale(###.###,##) and
> when the client side validation is enabled,
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
And me too.
Here, we're using a javascript + onToClient and onParseClient methods to
automatically format numbers and currencies to our locale(###.###,##) and
when the client side validation is enabled, it complains about the comma.
It's a nice feature, but it should support localization.
On Mon
