You need to check the name and surname entered in the form, as well as a double surname, for example Irina Naro-fominskaja

Closed due to the fact that the essence of the issue is not clear to the participants Saidolim , Nick Volynkin ♦ , apelsinka223 , Aries , Alexey Shtanko 24 Sep '15 at 17:00 .

Try to write more detailed questions. To get an answer, explain what exactly you see the problem, how to reproduce it, what you want to get as a result, etc. Give an example that clearly demonstrates the problem. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • The question is not in the correct form. Describe in the question what exactly you would like to check and so on. Those. describe the verification rules. - Vitalii Obideiko
  • one
    apparently somewhere like \w+\s\w+(-\w+)? . I did not specifically limit the length of the name and surname, as I know a person with the name "Iya Em". - KoVadim
  • There was a view of checking the presence of two words (First Name, Last Name, as well as a double last name), Latin letters, regardless of case. - Sergey Kovalenko
  • KoVadim, thanks, works. - Sergey Kovalenko
  • 2
    @KoVadim: was familiar with the last name "Yu", a Chinese. - Nick Volynkin ♦

1 answer 1

Validating names and surnames is a bad idea . You will not achieve anything by this, except for irritating users when they need to enter something that does not pass the test of your “universal regular schedule”.

Turn to the classics:

So, for the good of all, I have compiled a list of assumptions that your system can probably make about people's names. All these assumptions are wrong . Try to at least reduce the list when you design the system next time.

  1. Each person has one canonical full name.
  2. Each person has one full name that he uses.
  3. At this point in time, each person has one canonical full name.
  4. At this point in time, each person has one full name that he uses.
  5. Each person has exactly N names, regardless of the value of N.
  6. Names fit in a certain number of characters.
  7. Names do not change.
  8. Names change, but only in certain limited cases.
  9. Names are in ASCII.
  10. Names are written in any one encoding.
  11. All names correspond to Unicode characters.
  12. Names are case sensitive.
  13. Names are not case sensitive.
  14. Sometimes names have prefixes or suffixes, but you can safely ignore them.
  15. Names do not contain numbers.
  16. Names can not be written in CAPITAL letters.
  17. Names cannot be written in lowercase letters.
  18. There is order in names. Selecting one of the record ordering schemes will automatically lead to a constant order among all systems if they all use the same ordering scheme.
  19. Name and surname necessarily different.
  20. People have a last name or something similar, common to relatives.
  21. The name of the person is unique.
  22. The name of the person is almost unique.
  23. Okay, okay, but the names are quite rare, so there are no million people with the same name and surname.
  24. My system will never deal with names from China.
  25. Or Japan.
  26. Or Korea.
  27. Or Ireland, Great Britain, USA, Spain, Mexico, Brazil, Peru, Sweden, Botswana, South Africa, Trinidad, Haiti, France, the Klingon Empire - all of these use “weird” schemes for names.
  28. The Klingon Empire was a joke, right?
  29. To hell with cultural relativism! People in my society, at least, have the same idea of ​​a generally accepted standard for names.
  30. There is an algorithm that converts names to one and the other without loss. (Yes, yes, you can do it, if the algorithm at the output returns the same as at the entrance, take yourself a medal).
  31. I can confidently assume that this dictionary of obscene words does not contain surnames.
  32. Names are given to people at birth.
  33. OK, maybe not at birth, but pretty soon after.
  34. Okay, okay, for a year or so.
  35. Five years?
  36. You're kidding, right?
  37. Two different systems, in which the name of the same person is indicated, will use the same name for it.
  38. Two different data entry operators, if given the name of a person, will necessarily enter the same character set, if the system is well designed.
  39. People whose names break my system are strange aliens. They should have normal, acceptable names, like (a sequence of hieroglyphs).
  40. People have names.

The list is by no means exhaustive. If you need examples of real names that refute any of these points, I’m happy to name them. You can add in the comments other items for this list of delusions, and send people a link to this list the next time they come up with a brilliant idea to make a database with the columns first_name and last_name.

Sauce: http://habrahabr.ru/post/146901/