On Fri, Mar 18, 2011 at 2:48 PM, Ramiro Morales <[email protected]> wrote:
> Hi all,
>
> Can member of the spanish (Spain) localization team triage ticket
> [1]15640?
>
> Reporter has attached a new copy of forms.py file. The diff is this:
>
> --- django/contrib/localflavor/es/forms.py 2011-02-17
> 10:51:20.000000000 -0300
> +++ forms.py 2011-03-18 07:56:00.000000000 -0300
> @@ -41,7 +41,7 @@
> }
>
> def __init__(self, *args, **kwargs):
> - super(ESPhoneNumberField, self).__init__(r'^(6|8|9)\d{8}$',
> + super(ESPhoneNumberField, self).__init__(r'^(6|7|8|9)\d{8}$',
> max_length=None, min_length=None, *args, **kwargs)
>
> class ESIdentityCardNumberField(RegexField):
>
> Of course, for a patch fixing this to be considered, it'd need to include
> tests
> (probably modification of the tests in
> tests/regressiontests/forms/localflavor/es.py )
Not officially a part of the team (as far as I know), but if what you
want to know is if that is correct by Spanish standards, then it
depends. [89]\d{8} are valid numbers for landlines. 8\d{8} is for cell
phones. 7\d{8} is valid too, theoretically:
http://www.mityc.es/es-ES/GabinetePrensa/NotasPrensa/2010/Paginas/npaperturanuevanumeracionmovil110410.aspx
as they've determined the 6* range will be depleted by 2012, and
decided to open the 7 prefix for cell phones too.
There's a side issue, though: I think they won't start to assign
numbers in that range until at least Oct/2011, so nobody really have
one of those numbers yet, but I guess the locale should be prepared to
accept them.
cheers,
Ricardo
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-i18n?hl=en.
