Skip to main content

How to normalize text to English base

Cand avem o aplicatie care este accesata din mai multe tari, poate sa apara o problema cand se pune problema cautarii sau stocarii datelor. Daca avem o adresa scrisa in limba romana de exemplu o sa avem caractere precum 'â', 'ț', ... dar cand un utilizator dintr-o alta tara o sa caute o anumita adresa de exemplu vrem sa normalizam textul.
O varianta destul de simpla la aceasta problema este sa normalizam tot textul spre caractere ascii base. In acest caz de exemplu 'ț' o sa devina 't'.
Acest lucru se face destul de simplu folosind metoda Normalize, făcând o descompunere canonica a textului.
string normalizeText = sourceText.Normalize(Normalize.FormD);
Trebuie sa avem grija la unele semne de legatura precum 'ß', pentru care trebuie sa facem manual transformarea( dacă dorim).
Mai jos gasiti implementarea pe care eu o propun:
private static readonly char[] SplitChars;
private static readonly Dictionary<char, char> SpecialChars;
static Constructor()
{
SpecialChars = new Dictionary<char, char>();
SpecialChars.Add('ß', 's');

SplitChars = new[] { ' ', '"', '\'', '`', '"', '-', ',', '.' };
}
private string ConvertToBaseASCII(string text)
{
var normalize = text
.ToLowerInvariant()
.Normalize(NormalizationForm.FormD)
.Split(SplitChars, StringSplitOptions.RemoveEmptyEntries);
StringBuilder sb = new StringBuilder();

foreach (string item in normalize)
{
foreach (var c in item)
{
UnicodeCategory unicodeCategory = CharUnicodeInfo.GetUnicodeCategory(c);
if (SpecialChars.Keys.Contains(c))
{
sb.Append(SpecialChars[c]);
continue;
}
if (unicodeCategory != UnicodeCategory.NonSpacingMark)
{
sb.Append(c);
}
}
}

return sb.ToString().Normalize(NormalizationForm.FormC);
}

Comments

  1. Interesant - e foarte buna metoda cat timp user-ul se asteapta sa primeasca ceva mai multe rezultate la o cautare decat la ce se gandea el (search dupa "fata" si obtine "fata", „față”, „fată” sau „făta”).

    Ma tem insa ca metoda merita folosita doar cand trebuie sa iti implementezi singur functia de search, altfel trebuie gasit echivalentul din SQL de ex. (collations si alte cele)

    Cat despre ß (eszett-ul germanilor) din cate am vazut echivalentul e 'ss', nu s, si intr-adevar normalizarea din Unicode nu ajuta aici.. Probabil mai sunt multe cazuri similare in alte limbi, de aia nenea Kaplan nu le trateaza nici el la http://blogs.msdn.com/b/michkap/archive/2007/05/14/2629747.aspx :)

    ReplyDelete
  2. In cazul meu este vorba mai multe de comparare a datelor. Cautarea se face automat de catre un alt sistem si trebuie sa verific daca rezultatul returnat este asemanator cu cea ce a introdus utilizatorul.
    Exista framework-uri care iti permit sa compari doua siruri de caractere si iti pot stabilii cat de asemanatoare sunt cele doua siruri, dar eu nu aveam nevoie de un mecanism atat de complex.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too