Releases: theiconic/name-parser
Releases · theiconic/name-parser
v1.2.11
- add support for combined initials - without separating space (e.g. in 'TJ Hooker' or 'T.J. Hooker')
(This slightly changes the parsing behaviour as e.g. TJ Hooker
would have previously ended up as Tj Hooker
, with Tj
being the first name. However, this was seen as a bug, so this change is not treated as a breaking change.)
v1.2.10
- add support for multi-part salutations (e.g. 'Her Honour') (#29, thanks @rvanlaak)
- fix parsing of combined lastnames with prefix (e.g. 'Heijdanus-De Boer') (#31, thanks @rvanlaak)
v1.2.9
- support for 'Prof.' salutation (#24, thanks @baletskyi)
- enable re-printing of given name (first name, middle names, initials) in given order (#21, thanks @jpmschuler)
- enable re-printing of full name (given name plus last names) in given order
- add test for custom language support (#23, thanks @ryancwalsh)
v1.2.8
- add test cases for parsing and normalisation of vietnamese names (#17, thanks @yellow1912)
v1.2.7
- enable parsing suffixes in patterns of the form
lastname, firstname suffix
where they were previously parsed as middle names (#18, thanks for reporting @adrienne)
- add tests for
lastname, firstname, suffix
and lastname, firstname initial, suffix
patterns
v1.2.6
- limit salutation to the first half of the parts and allow overriding via
setMaxSalutationIndex()
- remap special values like suffix, nickname and salutation from the end of the string as lastnames if otherwise no lastname can be found (#11, thanks again @VinceG)
v1.2.5
- support parsing of strings that have the salutation at the end without comma-separation (#11, thanks @VinceG)
- add section about special part retrieval features in README
v1.2.4
- enable separate retrieval of last name prefixes via
getLastnamePrefix()
and pure last names (without prefixes) via getLastname(true)
(#10, thanks @divinenanny)
v1.2.3
- correctly parse nickname-type segments even if they are in last position, e.g.
Charles Dickens (20th century)
(#8, thanks @divinenanny)
v1.2.2
- fix for parsing of middle names in
<lastname>, <firstname> <middlename>
scenarios (thanks @francislavoie )