Opened 18 years ago
Closed 18 years ago
#6311 closed (duplicate)
"First name" and "Last name" in user model is too bad
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Internationalization | Version: | dev |
| Severity: | Keywords: | first last name user model | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The user model has fields for "first name" and "last name". In many non-English speaking countries, people are not named this way, which can lead to several problems.
See: http://rishida.net/blog/?p=100
Change History (3)
comment:1 by , 18 years ago
comment:3 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Agreed, a framework which is designed to be internationalizable shouldn't rely on Western first/last name schema. That's a legacy shortseeing, like not using unicode in the initial django releases.
If anyone actually needs the formal person data, he might use 1:1 relation with some Person model (and put there First, Last, Title, Position, Date of Birth and other fields which shouldn't be in the "generic" User model).