CommentFileSizeAuthor
#4 name-2950062-4-preferred-given-name-support-nameformatparser.patch6.13 KBalan d.
#2 name-2950062-2-preferred-given-name-support-nameformatparser.patch5.95 KBalan d.

Comments

Alan D. created an issue. See original summary.

alan d.’s picture

alan d. commented
Status: Active » Needs review
StatusFileSize
new name-2950062-2-preferred-given-name-support-nameformatparser.patch5.95 KB

Not intending to expand the Name Field element, but to provide support for preferred or nicknames if the preferred key is past into the formatter.

'p' => t('Preferred given or nickname'),
'w' => t('First letter preferred given or nickname'),
'd' => t('Conditional: Either the preferred given or family name. Given or nickname is given preference.'),
'D' => t('Conditional: Either the preferred given or family name. Family name is given preference.'),

Untested patch.

Status: Needs review » Needs work

The last submitted patch, 2: name-2950062-2-preferred-given-name-support-nameformatparser.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

alan d.’s picture

alan d. commented
Status: Needs work » Needs review
StatusFileSize
new name-2950062-4-preferred-given-name-support-nameformatparser.patch6.13 KB

  • Alan D. committed 22ea60f on 8.x-1.x 
    Issue #2950062 by Alan D.: Nickname support for NameFormatParser
alan d.’s picture

alan d. commented
Status: Needs review » Fixed
alan d.’s picture

alan d. commented
Parent issue: » #2949574: [meta] Name Field Full Release

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.