Tickets :: [#9553] Contact name order should not be fixed to "First name Last name"

6.0.0-alpha12

6/12/25

Summary	Contact name order should not be fixed to "First name Last name"
Queue	Turba
Queue Version	Git master
Type	Enhancement
State	Rejected
Priority	1. Low
Owners
Requester	deje07 (at) gmail (dot) com
Created	01/29/2011 (5248 days ago)
Due
Updated	01/30/2013 (4516 days ago)
Assigned
Resolved	01/30/2013 (4516 days ago)
Milestone
Patch	No

01/30/2013 05:17:46 PM	Jan Schneider	State ⇒ Rejected Version ⇒ Git master

01/31/2011 10:29:48 PM	deje07 (at) gmail (dot) com	Comment #10	Reply to this comment
Sorry, I did not see the comments :(

01/31/2011 10:28:37 PM	deje07 (at) gmail (dot) com	Comment #9	Reply to this comment
Could you please be more specific? There is no file named: config/backends.php

01/31/2011 10:21:15 PM	Michael Rubinsky	Comment #8 Version ⇒ FRAMEWORK_3	Reply to this comment
..guess this is FW_3 then :)

01/31/2011 10:18:55 PM	Jan Schneider	Comment #7	Reply to this comment
Actually turba/config/sources.php in your version.

01/31/2011 10:12:02 PM	Michael Rubinsky	Comment #6	Reply to this comment
That's because it's not in the web UI. Read the comments in config/backends.php

01/31/2011 09:54:25 PM	deje07 (at) gmail (dot) com	Comment #5	Reply to this comment
Ok, it seems I'm missing something. I'm using the latest version of Horde Groupware Edition, and the "name" field is always grayed out and receives content from the discrete fields. Have not found any settings on the WEB UI that allows that field to be edited manually. Please excuse me being so lame, could you please tell me what did I wrong?

01/30/2011 03:04:46 PM	Jan Schneider	Comment #4	Reply to this comment
The name field is editable. You are not forced to use separate fields for the name.

01/30/2011 12:06:02 PM	deje07 (at) gmail (dot) com	Comment #3	Reply to this comment
The solution might be easier: the "name" field should be editable, with sane defaults. Like most of PIM applications do, and like vCard format solves this problem.

01/30/2011 10:57:29 AM	Jan Schneider	Comment #2 State ⇒ Feedback Priority ⇒ 1. Low	Reply to this comment
There is no infrastructure at all in Turba that allows per-user, or even per-contact differences in composite fields. And with the complexity we already have with composite fields today, I tend to not allow even more.

01/29/2011 11:18:37 PM	deje07 (at) gmail (dot) com	Comment #1 State ⇒ New Patch ⇒ No Milestone ⇒ Queue ⇒ Turba Summary ⇒ Contact name order should not be fixed to "First name Last name" Type ⇒ Enhancement Priority ⇒ 3. High	Reply to this comment
There are a lot of countries in the world that use the name order "Family name Given name" (for example Hungary, Japan, China, Korea, etc). If I use "First Name" as the "Family name", the display remains consistent within Turba, but Import-Export (at least when using vCard) swaps the names, and I am also unable to properly store names from countries using different ordering. A lot of contact manager applications allow defining the name ordering on a per-contact basis, so when displaying contact names the order will be proper. I'd suggest changing the naming of the fields to "Family name" and "Given name" to prevent confusion, and also introducing a per-contact name order setting (whether name order is "Eastern order" or "Western order", see http://en.wikipedia.org/wiki/Personal_name#Name_order). This would allow full internationalization and the mixture of names with different ordering. Also the vCard format lacks this setting but applications do honour the FN field, so contact import/export should take name order into account and generate/parse the FN field according to the name order. Greetings, Szécsi Gábor (Eastern name order)