Globalization

LocalizationProvider v5.7 Is Out

It's been a while since last Episerver DbLocalizationProvider package update. Fortunately this release includes couple bug fixes delivered by amazing developer community and also few new features. What's included in this release: "Transient" referenced projects are now properly respected and scanned (#github/28) Resource import in Episerver was not polite and threw up when importing not active/disabled languages (#github/30) Duplicate keys are ignored and first one is taken during MigrationTool process (#pull/25) There are also some other smaller bug fixes, but who really reads release…

Keep reading

LocalizationProvider Client Side Feature now also for Asp.Net Mvc Apps

There are sometimes moments when you just need to take deep inhale and add backward support for apps that most probably you will hardly see selected in "File > New Project". We do have some projects still based on "pure" Asp.Net Mvc that need client-side localization. Therefore adding support for this type of apps sounds like feature with "must have" label. At least for now. This applies to v5.5.1 and forward. However, if you are targeting .NET Core - support is…

Keep reading

Localization Provider - 5th generation out!

Freshly baked v5.0 is out now. Changes in this version (some of them are breaking ones). Mostly release was focused on .Net Core AdminUI improvements and new features.…

Keep reading

Switch Content Language Everywhere in EPiServer

Nowadays lot of sites are localized or globalized (depending from which point of view you are looking at). Usually it means that developer has to provide some sort of language switcher for the end-user to pick another content language. This blog post is about small trick that I’m using when need to provide switcher on web sites driven by EPiServer. I’ll not dig into details on how to get started with globalization and how localization engine and services are working (you can find lot of information in SDK)…

Keep reading