AspNetCore.Localizer.Json.Wasm 0.0.2

dotnet add package AspNetCore.Localizer.Json.Wasm --version 0.0.2
NuGet\Install-Package AspNetCore.Localizer.Json.Wasm -Version 0.0.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="AspNetCore.Localizer.Json.Wasm" Version="0.0.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add AspNetCore.Localizer.Json.Wasm --version 0.0.2
#r "nuget: AspNetCore.Localizer.Json.Wasm, 0.0.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install AspNetCore.Localizer.Json.Wasm as a Cake Addin
#addin nuget:?package=AspNetCore.Localizer.Json.Wasm&version=0.0.2

// Install AspNetCore.Localizer.Json.Wasm as a Cake Tool
#tool nuget:?package=AspNetCore.Localizer.Json.Wasm&version=0.0.2

AspNetCore.Localizer.Json

Json Localizer library for .NetCore Asp.net projects

Nuget

NuGet NuGet

Build

.NET

Project

This library allows users to use JSON files instead of RESX in an ASP.NET application. The code tries to be most compliant with Microsoft guidelines. The library is compatible with NetCore.

Configuration

An extension method is available for IServiceCollection. You can have a look at the method here

Options

A set of options is available. You can define them like this :

services.AddJsonLocalization(options => {
        options.CacheDuration = TimeSpan.FromMinutes(15);
        options.ResourcesPath = "mypath";
        options.FileEncoding = Encoding.GetEncoding("ISO-8859-1");
        options.SupportedCultureInfos = new HashSet<CultureInfo>()
        {
          new CultureInfo("en-US"),
          new CultureInfo("fr-FR")
        };
    });

Current Options

  • SupportedCultureInfos : _Default value : List containing only default culture and CurrentUICulture. Optionnal array of cultures that you should provide to plugin. _(Like RequestLocalizationOptions)
  • ResourcesPath : Default value : $"{_env.WebRootPath}/Resources/". Base path of your resources. The plugin will browse the folder and sub-folders and load all present JSON files.
  • AdditionalResourcePaths : Default value : null. Optionnal array of additional paths to search for resources.
  • CacheDuration : Default value : 30 minutes. We cache all values to memory to avoid loading files for each request, this parameter defines the time after which the cache is refreshed.
  • FileEncoding : default value : UTF8. Specify the file encoding.
  • IsAbsolutePath : _default value : false. Look for an absolute path instead of project path.
  • UseBaseName : _default value : false. Use base name location for Views and constructors like default Resx localization in ResourcePathFolder. Please have a look at the documentation below to see the different possiblities for structuring your translation files.
  • Caching : _default value: MemoryCache. Internal caching can be overwritted by using custom class that extends IMemoryCache.
  • PluralSeparator : _default value: |. Seperator used to get singular or pluralized version of localization. More information in Pluralization
  • MissingTranslationLogBehavior : _default value: LogConsoleError. Define the logging mode
  • LocalizationMode : _default value: Basic. Define the localization mode for the Json file. Currently Basic and I18n. More information in LocalizationMode
  • MissingTranslationsOutputFile : This enables to specify in which file the missing translations will be written when MissingTranslationLogBehavior = MissingTranslationLogBehavior.CollectToJSON, defaults to MissingTranslations.json
  • IgnoreJsonErrors: This properly will ignore the JSON errors if set to true. Recommended in production but not in development.

Search patterns when UseBaseName = true

If UseBaseName is set to true, it will be searched for lingualization files by the following order - skipping the options below if any option before matches.

  • If you use a non-typed IStringLocalizer all files in the Resources-directory, including all subdirectories, will be used to find a localization. This can cause unpredictable behavior if the same key is used in multiple files.

  • If you use a typed localizer, the following applies - Namespace is the "short namespace" without the root namespace:

    • Nested classes will use the translation file of their parent class.
    • If there is a folder named "Your/Namespace/And/Classname", all contents of this folder will be used.
    • If there is a folder named "Your/Namespace" the folder will be searched for all json-files beginning with your classname.
    • Otherwise there will be searched for a json-file starting with "Your.Namespace.And.Classname" in your Resources-folder.
    • If there any .shared.json file at base path, all the keys that do not exist in other files will be added.
  • If you need a base shared files, just add a file named localization.shared.json in your ResourcesPath

Pluralization

In version 2.0.0, Pluralization was introduced. You are now able to manage a singular (left) and plural (right) version for the same Key. PluralSeparator is used as separator between the two strings.

For example : User|Users for key Users

To use plural string, use parameters from IStringLocalizer, if last parameters is a boolean, pluralization will be activated.

Pluralization is available with IStringLocalizer, IViewLocalizer and HtmlStringLocalizer :

In version 3.1.1 and above you can have multiple pluralization, to use it, you should use IJsonStringLocalizer interface and this method LocalizedString GetPlural(string key, double count, params object[] arguments)

localizer.GetString("Users", true);

Clean Memory Cache

Version 2.2.0+ allows you to clean cache. It's usefull when you want's tu update in live some translations.

Example

public class HomeController{
  private readonly IJsonStringLocalizer _localizer;
  
  public HomeController(IJsonStringLocalizer<HomeController> localizer)
  {
      _localizer = localizer;
      _localizer.ClearMemCache(new List<CultureInfo>()
      {
          new CultureInfo("en-US")
      });
  }
}

Blazor Server HTML parsing

As you know, Blazor Server does not provide IHtmlLocalizer. To avoid this, you can now use from IJsonStringLocalizer this method MarkupString GetHtmlBlazorString(string name, bool shouldTryDefaultCulture = true)

Information

Platform Support

Platform Version
NetCore 7.0.0+
Blazor Server 7.0.0+
Blazor Wasm 7.0.0+

WithCulture method

WhithCulture method is not implemented and will not be implemented. ASP.NET Team, start to set this method Obsolete for version 3 and will be removed in version 4 of asp.net core.

For more information : https://github.com/AlexTeixeira/Askmethat-Aspnet-JsonLocalizer/issues/46

Localization mode

As asked on the request #64, Some user want to have the possiblities to manage file with i18n way. To answer this demand, a localization mode was introduced with default value Basic. Basic version means the the one describe in the previous parts

I18n

To use the i18n file management, use the the option Localization mode like this : cs LocalizationMode = LocalizationMode.I18n. After that, you should be able to use this json :

{
   "Name": "Name",
   "Color": "Color"
}

File name

File name are important for some purpose (Culture looking, parent culture, fallback).

Please use this pattern : [fileName].[culture].json If you need a fallback culture that target all culture, you can create a file named localisation.json. Of course, if this file does not exist, the chosen default culture is the fallback.

Important: In this mode, the UseBaseName options should be False.

For more information : https://github.com/AlexTeixeira/Askmethat-Aspnet-JsonLocalizer/issues/64

Blazor Wasm

Specific Wasm Options

  • JsonFileList : _default value: null. List of json files to load. If null, all json files will be loaded.

Blazor Wasm Specificities

Because of the way Blazor Wasm works, the plugin will not be able to load files from the server. To avoid this, you should embed your files in the project and use the following code :

 <EmbeddedResource Include="Resources\localization.json">
  <CopyToOutputDirectory>Never</CopyToOutputDirectory>
 </EmbeddedResource>

The second specificities is the management of the language files. Blazor Wasm uses the file path as Assembly name, so you can't have multiple files with the same name.

For example, if you have a file named localization.json in the folder Resources, you can't have another file starting with name localization in the folder Resources, a file with the name localization.fr.json will throw an exception.

So you should have different folder for each language culture.

Performances

After talking with others Devs about my package, they asked my about performance.


BenchmarkDotNet=v0.13.1, OS=Windows 10.0.22000
Intel Core i7-10870H CPU 2.20GHz, 1 CPU, 16 logical and 8 physical cores
.NET SDK=6.0.101
  [Host]     : .NET 6.0.1 (6.0.121.56705), X64 RyuJIT
  DefaultJob : .NET 6.0.1 (6.0.121.56705), X64 RyuJIT


Method Mean Error StdDev Min Max Ratio RatioSD Gen 0 Gen 1 Gen 2 Allocated
Localizer 57.34 ns 0.590 ns 0.523 ns 56.65 ns 58.46 ns 1.00 0.00 - - - -
JsonLocalizer 41.50 ns 0.552 ns 0.516 ns 40.60 ns 42.46 ns 0.72 0.01 0.0057 - - 48 B
JsonLocalizerWithCreation 169,174.60 ns 1,070.840 ns 1,001.664 ns 167,445.80 ns 170,873.85 ns 2,950.03 33.21 4.6387 2.1973 0.2441 40,706 B
I18nJsonLocalizerWithCreation 228,438.65 ns 4,188.350 ns 6,643.166 ns 218,070.12 ns 245,103.20 ns 4,026.62 130.32 12.2070 6.1035 0.4883 104,172 B
JsonLocalizerWithCreationAndExternalMemoryCache 2,813.26 ns 51.894 ns 48.541 ns 2,731.36 ns 2,920.27 ns 49.04 0.92 0.5264 0.2632 - 4,424 B
JsonLocalizerDefaultCultureValue 145.34 ns 1.284 ns 1.201 ns 142.61 ns 146.81 ns 2.53 0.04 0.0315 - - 264 B
LocalizerDefaultCultureValue 159.06 ns 0.919 ns 0.859 ns 157.63 ns 160.51 ns 2.77 0.03 0.0257 - - 216 B

Contributors

<table> <tr> <td align="center"> <a href="https://github.com/lethek"> <img src="https://avatars2.githubusercontent.com/u/52574?s=460&v=4" width="100px;" alt="Michael Monsour"/> <br /> <sub><b>Michael Monsour</b></sub> </a> </td> <td align="center"> <a href="https://github.com/lugospod"> <img src="https://avatars1.githubusercontent.com/u/29342608?s=460&v=4" width="100px;" alt="Luka Gospodnetic"/> <br /> <sub><b>Luka Gospodnetic</b></sub> </a> </td> <td align="center"> <a href="https://github.com/Compufreak345"> <img src="https://avatars3.githubusercontent.com/u/10026694?s=460&v=4" width="100px;" alt="Christoph Sonntag"/> <br /> <sub><b>Christoph Sonntag</b></sub> </a> </td> <td align="center"> <a href="https://github.com/Dunning-Kruger"> <img src="https://avatars0.githubusercontent.com/u/1564825?s=460&v=4" width="100px;" alt="Nacho"/> <br /> <sub><b>Nacho</b></sub> </a> </td> <td align="center"> <a href="https://github.com/AshleyMedway"> <img src="https://avatars3.githubusercontent.com/u/1255596?s=460&v=4" width="100px;" alt="Ashley Medway"/> <br /> <sub><b>Ashley Medway</b></sub> </a> </td> <td align="center"> <a href="https://github.com/NoPasaran0218"> <img src="https://avatars2.githubusercontent.com/u/25226807?s=460&v=4" width="100px;" alt="Serhii Voitovych"/> <br /> <sub><b>Serhii Voitovych</b></sub> </a> </td> <td align="center"> <a href="https://github.com/JamesHill3"> <img src="https://avatars0.githubusercontent.com/u/1727474?s=460&v=4" width="100px;" alt="James Hill"/> <br /> <sub><b>James Hill</b></sub> </a> </td> <td align="center"> <a href="https://github.com/Czirok"> <img src="https://avatars2.githubusercontent.com/u/1266377?s=460&v=4" width="100px;" alt="Ferenc Czirok"/> <br /> <sub><b>Ferenc Czirok</b></sub> </a> </td> <td align="center"> <a href="https://github.com/rohanreddyg"> <img src="https://avatars0.githubusercontent.com/u/240114?s=400&v=4" width="100px;" alt="rohanreddyg"/> <br /> <sub><b>rohanreddyg</b></sub> </a> </td> <td align="center"> <a href="https://github.com/rickszyr"> <img src="https://avatars.githubusercontent.com/u/10763102?s=460&v=4" width="100px;" alt="rickszyr"/> <br /> <sub><b>rickszyr</b></sub> </a> </td> <td align="center"> <a href="https://github.com/ErikApption"> <img src="https://avatars.githubusercontent.com/u/3179656?s=460&u=4a6b52f80b64f5951d3d04b4cfe18ac7f050a52a&v=4" width="100px;" alt="ErikApption"/> <br /> <sub><b>ErikApption</b></sub> </a> </td> </tr>

</table>

A special thanks to @Compufreak345 for is hard work. He did a lot for this repo.<br/><br/> A special thanks to @EricApption for is work to improve the repo and making a very good stuff on migrating to net6 and System.Text.Json & making it working for blazor wasm

License

MIT Licence

Product Compatible and additional computed target framework versions.
.NET net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.0.2 290 10/22/2023
0.0.1 179 8/20/2023