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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…