> If I remember gmail has such option, but I don't know if this works 
> on
> addcontact action. If user prefers e.g. Surname,Forename order it
> doesn't means sender will prefer it too. What if user has a two
> (fore)names? What if it is a nick (like mine) or company name? Too 
> much
> guessing and possible mistakes.
>
> In Roundcube the name field is for display name and it should be not
> changed in any way (a part of your patch). When name is not specified 
> in
> address string we're trying to build the (display) name. A possible
> solution would be to get rid of it and leave display-name empty
> (currently it's a required field).

 Ok, I agree with your arguments!
 Another problem (and why I made the patch) is, that the name field is 
 used as CN and thus as key identifier in the LDAP (at least in my setup, 
 others can use the email). So it makes conflicts if it is empty at 
 creating.
 For me, it would make more sense to try to set the "surname", 
 "firstname" fields directly at this place, but I think this fields are 
 not accessible, isnt it?

 My question now: shall I investigate more? Because I can live with my 
 patch for now, and if this topic is planed anyway to be redesigned in 
 the future it makes maybe no sense.

 thanks
 Andreas
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/8f4f07cd

Reply via email to