This is a harder problem then just that. While doing that would allow a 
solution to the name problem, there are more problems django.contrib.auth's 
User model and it would be best to come up with a generic solution that fixes 
all of these problems, instead of applying bandaid fixes.

On Thursday, November 10, 2011 at 12:53 PM, hcarvalhoalves wrote:

> I believe the solution is to actually figure a migration path to move
> everything that is non-essential to outside the User model. To
> identify a User, it should be enough to have username, password and
> permissions, and have the rest of the fields live in a
> django.contrib.auth.models.DefaultUserProfile.
> 
> On 22 set, 02:26, lvella <[email protected] (http://gmail.com)> wrote:
> > The User model included in Authentication subsystem is very annoying
> > to use here in Brazil. The common "first name" and "last name" method
> > of identifying people found in English speaking countries is very
> > unnatural to our culture, which people usually have two or more family
> > names. It is a cultural trait of here that renders unsuitable the
> > splitting of the name into first and last on the model. There are
> > countries/cultures with other people naming customs that is also hard
> > to localize with this model [1][2].
> > 
> > What about changing this in future versions? Maybe simply a
> > "true_name" field would do? Or maybe a way to customize the fields in
> > the User model.
> > 
> > [1]:http://en.wikipedia.org/wiki/Arabic_name
> > [2]:http://en.wikipedia.org/wiki/Eastern_Slavic_naming_customs
> > 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> To unsubscribe from this group, send email to 
> [email protected] 
> (mailto:[email protected]).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en.

Reply via email to