The W3C have some recommandation on the question. https://www.w3.org/International/questions/qa-personal-names
2016-07-29 17:47 GMT+02:00 Aymeric Augustin <aymeric.augus...@polytechnique.org>: > Hello, > > Indeed, Django’s default limit on last name length doesn’t work well for > Brazilians (at least). > > Actually having a `first_name` and `last_name` field doesn’t work well in > various cultures, including the US when you want a middle initial. Custom > user models are the general answer to that question. > > In this particular case, the drawbacks of increasing the `max_length` of > `first_name` and `last_name` to something like 50 seem limited now that we > have the migrations framework. Making that change will automatically avoid > the issue for many people — perhaps at the cost of introducing UI issues when > the name is displayed in the header, but that’s arguably a lesser evil. > > So I’m +0 on making that change. > > -- > Aymeric. > >> On 29 Jul 2016, at 09:18, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas >> <raonyguimar...@gmail.com> wrote: >> >> Hello everyone, >> >> For a long time I was having problems to login to djangopackages.com using >> my github account (pydanny/djangopackages#338). After investigating I >> discovered the problem was because my surname is longer than 30 characters. >> I don't know why both first_name and last_name fields have the same size >> limit of 30 characters in Django. That doesn't sound very reasonable. >> >> I'm sure there are other people on the same situation and this already >> happened with me trying to login in other django websites. >> >> Tim Graham suggested I should first ask on this maillist >> (https://github.com/django/django/pull/6988#issuecomment-235945422) to see >> if there is consensus to make the change. >> >> I would like to ask your opinion about an increase from 30 to 60 characters >> on last_name field so that my login and others won't break again in the >> future. I can create a Trac ticket if the response is positive. >> >> Kind Regards, >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/4A15ED67-802B-4A3A-85DA-265A5A5ADEF1%40polytechnique.org. > For more options, visit https://groups.google.com/d/optout. -- Cordialement, Coues Ludovic +336 148 743 42 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAEuG%2BTZXuGBr4_eU5pHBUONX8k5Z-z13YApJOxH%3D4iWbPutArA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
