[wp-trac] [WordPress Trac] #6148: Internationalization of personal names

[WordPress Trac]

#6148: Internationalization of personal names
-------------------------------------------------+-------------------------
 Reporter:  aradams                              |       Owner:  (none)
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.3
Component:  Users                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion needs-design-feedback    |     Focuses:  ui
  needs-screenshots has-patch                    |
-------------------------------------------------+-------------------------

Comment (by azaozz):

 Replying to [comment:19 kjellr]:

 > I think the patch may need an update as well

 Looking at it again, it is a solid start and fixes several issues. On the
 other hand thinking it would be more beneficial in the long run if we go
 with @johnbillion's
 [https://core.trac.wordpress.org/ticket/47522#comment:3 suggestion (from
 #47522)] and the recommendations from the
 [https://www.w3.org/International/questions/qa-personal-names W3 article]
 about having a single "Name" field.

 A bit more background:
 - In WordPress the first_name and last_name fields are optional. The users
 may choose to not add their name at all, or to use only one of their
 names. These fields are
 - In addition to the "personal" name there are three other name related
 settings:
   - user_login, required, non-changeable,
   - nickname, required, initially set to user_login,
   - display_name, optional, set from the user's first and last names if
 present, falls back to user_login.

 As both first_name and last_name are optional, backwards compatibility
 looks straightforward. The only UI decision would be how to "show" the
 users that they can switch to one field for their full name. We can
 probably "grandfather" the two fields and show the single "Full Name"
 field as an alternative.

 - If both first_name and last_name are used, keep the fields and show a
 "Full Name" field under them as an option.
 - If only first_name or last_name is used, just show the value in the
 "Full Name" field.

 Switching to a single "Full Name" field would also affect the
 display_name. The current UI there offers combinations of the first_name,
 last_name, and nickname fields, but would be straightforward to update to
 only use the value from the "Full Name" field and let the user edit it.
 The other name related settings remain unchanged.

 In the back-end the most backwards-compatible transition would be to save
 the full name in `first_name`. As `last_name` is optional this would
 ensure all uses of the user's "formal name" (as opposed to display_name or
 nickname) will continue to work. Alternatively the full name can be stored
 in new meta but in this case all themes and plugins would need updating.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/6148#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform