Opened 18 years ago
Closed 18 years ago
#3194 closed enhancement (wontfix)
Telephone and City fields should have multiple locale specific formats
| Reported by: | voltron | Owned by: | hugo |
|---|---|---|---|
| Component: | Internationalization | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi There!
I think that the phone and city fields should extendable, something like models.TelephoneField("DE", format), DE is the international abbreviation for the Country Germany, format being a a format string, for example "(%i %i %i)%i"
Thanks! Kepp up the great work!
Change History (2)
comment:1 by , 18 years ago
| Component: | Database wrapper → Internationalization |
|---|---|
| Owner: | changed from to |
| Summary: | Telephone and City fields → Telephone and City fields should have multiple locale specific formats |
| Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Even within a given country, there isn't really a uniform way of expression things like phone numbers, so each option would have to be a number of choices. This rapidly gets unwieldy to maintain. If somebody wants a particular version, it's only validator away, so is fairly easy to write on a case-by-case basis.
Short version: at the moment, we won't be implementing this. If somebody or a group of people were really enthusiastic and implemented a fairly broad coverage of these sorts of things for many locales, we would be happy to point people towards it (or even maybe host it eventually).