[ 
https://issues.apache.org/jira/browse/TAP5-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662784#action_12662784
 ] 

argoyle edited comment on TAP5-211 at 1/11/09 7:07 AM:
-------------------------------------------------------------

I just attached my crude implementation of locale-aware double- and 
float-translators. The implementation also contains client-side locale-aware 
validation by sending the regular expression used to validate decimal numbers 
in the Tapestry.Init-call.

Maybe it can be of any use when creating a "real" solution to the problem.

      was (Author: argoyle):
    My crude implementation of locale-aware double- and float-translators. The 
implementation also contains client-side locale-aware validation by sending the 
regular expression used to validate decimal numbers in the Tapestry.Init-call.
  
> Add localization to translators to allow for localized display/entering of 
> values
> ---------------------------------------------------------------------------------
>
>                 Key: TAP5-211
>                 URL: https://issues.apache.org/jira/browse/TAP5-211
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.1.0.0
>            Reporter: Ulrich Stärk
>         Attachments: LocalizedTranslatorSource.zip, TAPESTRY-2457.txt, 
> tapestry-locale-float-validation.diff
>
>
> Localization support for pages and messages is great in Tapestry but it lacks 
> support for localization of input values because the translators don't have 
> support for it. It would be great if users could just enter numbers etc. in 
> their respective locale, e.g. use ',' instead of '.' to seperate decimal 
> places from the integer part, out of the box.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to