Skip to content
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

Option to respect original casing and encoding #58

Open
rjalexa opened this issue Jan 13, 2023 · 0 comments
Open

Option to respect original casing and encoding #58

rjalexa opened this issue Jan 13, 2023 · 0 comments

Comments

@rjalexa
Copy link

rjalexa commented Jan 13, 2023

I am amazed by the power and usefulness of this library, but Is there a way to respect the original casing? Example:
database: Hervé Le Corre->nominally->Name: herve familyname: le corre
while I'd love to have:
database: Hervé Le Corre->nominally->Name: Herve familyname: Le Corre
in my language for example there are many family names similar to "De Petris" or "de Iuliis" where the "de" particle originally meant "from the family of", and its casing also carries information since generally speaking the lower case "de" was found in aristocratic families only.
Please also note that in the above example Hervé is a grave accented letter e and I would need to preserve these.
Other examples in my sample which could be troublesome:
database: De Petris->nominally->Name: de Lastname: petris
This wrongly assumes that the lastname prefix De is a first name.
Carlos Ruiz Zafón->nominally->Name: carlos ruiz Lastname: zafon
Here Ruiz gets wrongly processed as a middle name and the accented ó gets demoted to a normal o
Marcos Ordóñez->nominally->Name: marcos Lastname: ordonez
Here the n loses its tilde.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant