in reply to Re: Strange Unicode normalization question
in thread Strange Unicode normalization question

Thank you. I had not understood what is happening and I think I do now. The NFKD is separating the í into 2 characters and the substitution is removing the 2nd one (the NonspacingMark) leaving an i (similarly for other 2). So "Lubomír,Bartoňová" becomes "Lubomir,Bartonova". Unless this is done there is no match for the combination of strings which include this name (BTW, the name is fictitious - I should have mentioned that). I am at a loss as to why we need to do this via this API which from a UK government organisation but there is no documentation saying this must be done.

  • Comment on Re^2: Strange Unicode normalization question

Replies are listed 'Best First'.
Re^3: Strange Unicode normalization question
by Your Mother (Archbishop) on Aug 16, 2018 at 17:46 UTC

    I have no clue what the most stable/robust answer is here but I thought this belonged in the footnotes of the thread: Text::Unidecode. I have used it for normalizing search indexes such that a user typing Francois finds François; maybe similar to your use case.