Opened 10 years ago

Closed 10 years ago

#9225 closed (wontfix)

Add a 'tussenvoegsel' / 'surname prefix' field to User class

Reported by: prinsroy@… Owned by: nobody
Component: Contrib apps Version: 1.0
Severity: Keywords: user dutch tussenvoegsel surname prefix
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Many Dutch and German names follow the pattern

Piet van der Sloot

Ludwig von Beethoven

For reasons of correct alphabetic ordering, capitalization and representation it is necessary to store the 'surname prefix' in a separate field. Right now this means extending the user class for even the most common cases. Thus the request to add a 'surname prefix' field to User class. I assume the implications for this feature are minimal, and it would be a great help.

Change History (1)

comment:1 Changed 10 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

There would be at least two major problems associated with integrating this change into Django.

Firstly, there is a backwards compatibility problem. Any existing installation will need to modify tables to include the new column.

Secondly, and more significantly, there is a big i18n issue. While western European languages have a generally accepted "firstname/lastname" convention, this doesn't hold for asian names, or names in many other cultures. it's also problematic from a usability point of view - as an english speaker, if I saw "surname prefix" on a form, I would have no idea what to put into that field (I could guess, but it would definitely be a guess).

If you have user requirements that are as specific as this, I would suggest defining your own User model.

Note: See TracTickets for help on using tickets.
Back to Top