Case sensitivity mismatch about expresslocalization HOT 2 CLOSED

Hi @morgrowe

Actually it is not a bug, the default behavior of localizing strings is case-sensitive. And as you mentioned it is not possible to add "Privacy" and "privacy" to the .resx file because they are considered same from the .resx file pov.

As a workaround, you can use the entry as a key in the resx file; by adding one key for the upper-case and another for lower-case. e.g.:

then you can call each one by its key:

@_loc.GetLocalizedString("upper_Privacy")

@_loc.GetLocalizedString("lower_privacy")

Or you can use <localize> html tag since you already installed LazZiya.TagHelpers.Localization:

<h1 localize-content>upper_Privacy</h1>
<h1 localize-content>lower_privacy</h1>

Notice : LazZiya.TagHelpers.Locaization is merged into the latest version of LazZiya.ExpressLocalization v4.0, currently it is in preview mode, you may see its docs in the wiki.

from expresslocalization.

Ok great, makes sense. I think I'll migrate to using keys in my .resx file instead. Not sure why that didn't occur to me in the first place.

I look forward to using v4.0 when it's out of preview mode. Thanks for all your hard work!

Cheers
Morgan

from expresslocalization.