You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've a fiscal code that does not pass the validation because the subject has a surname containing a diacritic but he's born before 2011, so it should be stored in a different way on Italian fiscal database.
Going into detail, subject surname is Alù and on his documents the fiscal code is LAXCGRYYYYYYYYYY but the library calculates LAUCGRYYYYYYYYYY. For these cases the library should use X for these kinds of characters or is this a weird case?
The text was updated successfully, but these errors were encountered:
Hi @mattiabasone. Thank you so much for using this library. I'm curious about this specific case. When was the subject born and when they calculated the codice fiscale? Maybe they were using a different rule at that specific time.
Hi @DavidePastore, the subject is born in 1976. I found this document, I suppose that before this change diacritic characters were not translated to the corresponding uppercase letter (Ù => U), but I'm not sure about that.
First of all thank you for your library 🙏
I've a fiscal code that does not pass the validation because the subject has a surname containing a diacritic but he's born before 2011, so it should be stored in a different way on Italian fiscal database.
Going into detail, subject surname is
Alù
and on his documents the fiscal code isLAXCGRYYYYYYYYYY
but the library calculatesLAUCGRYYYYYYYYYY
. For these cases the library should useX
for these kinds of characters or is this a weird case?The text was updated successfully, but these errors were encountered: