- From: Davis Peixoto <davis.peixoto@gmail.com>
- Date: Tue, 6 Apr 2010 16:04:48 -0700
Hello fellas, I agree with Mounir. Thing is UA is allowed to do that, but without clear rules, this can be a mess. If for date and time, where we have a lot of formats and standards for internationalization, how can UA specify and be no type mismatch, if we do not have any standard about phone numbers? I mean, american format differs a lot from brazilian, which differs a lot from indian, which differs from... you got it. But it would be great if this kind of data becomes part of i18n packages, meaning that any user, with a UA tunned to its native language can input that, and let it do the job, like for date and time. However, not like date, which is a fixed number, phones can vary a lot from one region to region in length, and prefixes. I think this is open to UA devs and RFC writers to take care, but I am not sure if these statements will be useful someday at all due this lack of pattern among regions. -- Hugs, Davis. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100406/9e45a21b/attachment.htm>
Received on Tuesday, 6 April 2010 16:04:48 UTC