As part of updating of updating the Csv class in Signum.Utilities to .Net 5, I've realize that the value for ListSeparator has changed for many cultures that use , instead of . for decimals separators.
foreach (var ci in new [] { "", "en", "en-GB", "en-US", "es", "es-ES", "de", "de-DE", "fr", "fr-FR" })
{
Console.WriteLine($"Culture {ci}\tListSeparator {CultureInfo.GetCultureInfo(ci).TextInfo.ListSeparator}");
}
netcoreapp3.1
Culture ListSeparator ,
Culture en ListSeparator ,
Culture en-GB ListSeparator ,
Culture en-US ListSeparator ,
Culture es ListSeparator ;
Culture es-ES ListSeparator ;
Culture de ListSeparator ;
Culture de-DE ListSeparator ;
Culture fr ListSeparator ;
Culture fr-FR ListSeparator ;
net5 rc2
Culture ListSeparator ,
Culture en ListSeparator ,
Culture en-GB ListSeparator ,
Culture en-US ListSeparator ,
Culture es ListSeparator .
Culture es-ES ListSeparator .
Culture de ListSeparator .
Culture de-DE ListSeparator .
Culture fr ListSeparator
Culture fr-FR ListSeparator
Both tests in the same machine.
Previously I was using ListSeparator as a way to detect the separator that will be used in a Csv file. Is this the intended purpose?
As part of updating of updating the Csv class in Signum.Utilities to .Net 5, I've realize that the value for
ListSeparatorhas changed for many cultures that use,instead of.for decimals separators.netcoreapp3.1
net5 rc2
Both tests in the same machine.
Previously I was using
ListSeparatoras a way to detect the separator that will be used in a Csv file. Is this the intended purpose?