We are experiencing the following problem with version 4.3. On a brand new site, when you add a Cyrilic based language as additional language, and create a translation for Product, Category, Manufacturer in Cyrilic when you switch the site language to one with Cyrilic letters, the title is HTML encoded resulting in Unicode Hex Character Code instead of the actual string. Example:
Компютри should actually be “Компютри“ (Computers)
We’ve tested on two different environments:
- Windows Server 2016 (SQL Server 2017 Standard 13.0.1601.5), IIS 10.0.14393.0, ASP.NET Core 3.1 Runtime (v3.1.3) - Windows Hosting Bundle
- Window Server 2012 R2 Datacenter, SQL Server 2012 Standard 11.0.5058.0, IIS 8.5.9600.16384, ASP.NET Core 3.1 Runtime (v3.1.3) - Windows Hosting Bundle
Steps to reproduce:
- Download the no source version of NopCommerce from the web site.
- Create empty website in IIS (make sure app pool is configured with proper permissions)
- Extract NopCommerce package into the IIS’s web site folder.
- Open the web site and install using the normal Installer (through the Install page)
- Navigate to administration and add new languages (Bulgarian and Russian)
- Download the translation XMLs for both languages and import them per language.
- Restart the web site from Admin.
- Create new category called Computers – Include in top menu.
o Default name in latin – “Computers”
o English translation – “Computers”
o Bulgarian translation – “Компютри“
o Russian translation – “Kомпьютеры”
- Navigate to the public site and change the language to Bulgarian or Russian from English.
- Right click in Chrome, Firefox or Edge to view page source.
Expected: Whether in Russian or in Bulgarian, the cyrilic translation for “Computers” should appear as “Компютри“ or “Kомпьютеры”,
Actual result: It appears in the page source as “Kомпьютеры” and “Компютри”
The only way to resolve this was by adding text encoding settings in NopEngine => ConfigureServices
services.Configure<WebEncoderOptions>(options =>
{
options.TextEncoderSettings = new TextEncoderSettings(UnicodeRanges.All);
});
