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 (5247 days ago) |
Due | |
Updated | 01/30/2013 (4515 days ago) |
Assigned | |
Resolved | 01/30/2013 (4515 days ago) |
Milestone | |
Patch | No |
Version ⇒ Git master
Version ⇒ FRAMEWORK_3
config/backends.php
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?
fields for the name.
with sane defaults. Like most of PIM applications do, and like vCard
format solves this problem.
State ⇒ Feedback
Priority ⇒ 1. Low
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.
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
"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)