-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing double last name failed #30
Comments
wyrfel
added a commit
that referenced
this issue
Nov 6, 2019
This enables the detection of lastnames combined via a dash with the prefix to a following lastname, e.g. in "Etje Heijdanus-De Boer". At this point the entire part is treated as Lastname as there is no support for re-combining last name parts or prefixes. This means the 'De' prefix in 'De Boer' above cannot be accessed individually.
Fixed in #31. Not fully happy with the solution, but should be good enough for now. Again, this points to a need for the part splitting to be smarter. |
wyrfel
added a commit
that referenced
this issue
Nov 6, 2019
This enables the detection of lastnames combined via a dash with the prefix to a following lastname, e.g. in "Etje Heijdanus-De Boer". At this point the entire part is treated as Lastname as there is no support for re-combining last name parts or prefixes. This means the 'De' prefix in 'De Boer' above cannot be accessed individually.
wyrfel
added a commit
that referenced
this issue
Nov 6, 2019
…in-combined-parts Detect last name prefixes in combined lastname parts (fixes #30)
Thank you @wyrfel 👏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the following book the name gets parsed incorrectly:
https://www.bol.com/nl/p/dans/9200000105098508
Etje Heijdanus-De Boer
Expected
Etje
Heijdanus-De Boer
Actual
Etje Heijdanus-De
Boer
The text was updated successfully, but these errors were encountered: