Localization

Localizing Asp.Net Core Applications now with AdminUI

Finally it's time to release administrative user interface for complementing Asp.Net Core application localizing process. It's been a while since localization provider has been released for Asp.Net Core applications, but until now - actual translation of the resources was limited due to absence of the user interface through which editor can make adjustments to the translations. I'm happy to announce that AdminUI has been rewritten to utilize Vue.js framework and to grind some of the rough edges of the library. Installation The only thing you need to…

Keep reading

Some smaller updates for DbLocalizationProvider

Localization provider is well and alive. Lately I've been heads down busy with porting some of the parts over to .Net Core targeting .Net Standard version 2.0. Anyway just wanted to let you know some of the smaller updates and fixes for the latest version of the provider packages. Multi-Target -> NetFx and Core Now there are specific multi targets for .Net Framework and .Net Core for and packages. This was required due to reported issues when package was used context together with WebApi (to be more specific…

Keep reading

Alternative Localization for Asp.Net Core Applications

Asp.Net Core Built-In Support This is code fragment from official documentation how to localize content using built-in functionality. App Content Localization [Route("api/[controller]")] public class AboutController : Controller { private readonly IStringLocalizer<AboutController> _localizer; public AboutController(IStringLocalizer<AboutController> localizer) { _localizer = localizer; } [HttpGet] public string Get() { return _localizer["About Title"]; } } And if you are working with Html content that shouldn't be escaped during rendering - you are using IHtmlLocalizer implementation that returns LocalizedHtmlString instance. public class BookController : Controller { private readonly IHtmlLocalizer<BookController&…

Keep reading

LocalizationProvider - Tree View, Export and Migrations

It's been a while since last blog post about localization provider. It just means that I've been heads down busy with implementing some great features :) Anyway - these are most probably last features before I'm switching over to .Net Core. I know that you might ask - why you need .Net Core if Episerver is still not there yet!? I'm planning to migrate to .Net Core because Episerver plugin is just small fraction of localization provider and actually you can use it outside of Episerver also - just in regular…

Keep reading

Strongly Localized EPiServer Categories

Initially strongly typed localization provider was not planned to be used everywhere in EPiServer, but localizing categories came as complimentary feature: [LocalizedResource(KeyPrefix = "/categories/")] public class Categories { [ResourceKey("category[@name=\"" + nameof(SampleCategory) + "\"]/description")] public static string SampleCategory => "Some Category !"; } Still there is lot of ceremony to get things right.. Sick and tired of generating proper resource keys for localizing EPiServer categories? Say no more. Localization provider gives you now (within latest version) possibility to decorate your class with attribute…

Keep reading