| Summary | vcard import: use N instead of FN for name import |
| Queue | Turba |
| Queue Version | 2.3.1 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | jan (at) horde (dot) org |
| Requester | brot (at) gmx (dot) info |
| Created | 08/28/2009 (5764 days ago) |
| Due | |
| Updated | 09/10/2009 (5751 days ago) |
| Assigned | |
| Resolved | 08/30/2009 (5762 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | 2.3.2 |
| Patch | No |
I am using the latest turba release with version 2.3.1 from December
10 2008 included in the Horde Groupware Webmail Edition 1.2.2.
Are these changes in the version 1.2.3 from the Webmail Edition available?
The latest Changes file doesn't cover the changes from the versions
1.2.2 and 1.2.3:
http://www.horde.org/webmail/docs/?f=CHANGES.html
Assigned to Jan Schneider
State ⇒ Resolved
Milestone ⇒ 2.3.2
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ vcard import: use N instead of FN for name import
Type ⇒ Bug
State ⇒ Unconfirmed
instead of N?
Today I imported a vcard file into my horde addressbook:
N:Lastname;Firstname;;;
FN:Lastname, Firstname
After the import the value of "turba_objects.object_firstname" was "Lastname,"
the value of "turba_objects.object_lastname" was "Firstname"
RFC 2426 (http://www.ietf.org/rfc/rfc2426.txt) defines a name order
for the N Attribute (3.1.2). But there is no order for the FN
attribute (3.1.1)