+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, it complains about the comma. > > It's a nice feature, but it should support localization. > > On Mon, Oct 6, 2008 at 2:55 PM, Maximilian Weißböck < > [EMAIL PROTECTED]> wrote: > > > Put me on the "me to" List ;-) > > > > We have a (very possible) project where the customer want's us to > > use Struts2 - but we hope we can convince him to Tapestry5. > > But if localization 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@tapestry.apache.org > > > Betreff: Localized Translators - again > > > > > > 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 times but you didn't even > comment > > > >> on > > > >> it...) > > > > > > > > I'm stretched a bit thin, and if I don't get 5.0.15 out today or > > > > tomorrow its going to wait until October. > > > > > > > > In any case, 2457 is going to slip to release 5.1. Your workaround > is > > > > to override TranslatorSource with your own service, with your own set > > > > of Translators. Sorry, I'm really trying to restrict changes at this > > > > point to things that can't be monkey patched it some way. > > > > > > > > > > I tried that solution and it's just not feasible. I can overwrite the > > > service but Tapestrys client side validation prevents me from using it. > > In > > > tapestry.js the format for floating point numbers is fixed and doesn't > > > include the comma character, so it always complains about the number > not > > > being a decimal number. So although my Translators could handle the > input > > > I can't input any localized content. > > > > > > I could disable client side validation for every form where I have to > > > input localized content but then why have that feature in the first > > place. > > > An alternative would be to fix the regular expression in tapestry.js to > > > also include the comma character but then for example '1,5' and '1.5' > > will > > > both pass although just one is valid with the user's current locale. > > > > > > Either way, this is becoming more and more annoying. The workaround > > > doesn't work and making the workaround work introduces other pitfalls. > > > > > > And I just can't believe that I'm the only one who wants his users to > be > > > able to input numbers, currencies etc. in their respective locale. > > > > > > Please Howard, help! > > > > > > Uli > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Atenciosamente, > > Marcelo Lotif > Programador Java e Tapestry > FIEC - Federação das Indústrias do Estado do Ceará > (85) 3477-5910 >
