I have recently upgraded from Abp v3.8.3 to the latest version.
I am finding that client side localization is now returning the unicode representation of the apostrophe character rather than the actual character. Is there a work around for this, as this characeter is used extensively in our system.
Before the release of 4.6. You can copy the code of the LocalizationScriptManager yourself and replace the ILocalizationScriptManager with your own custom components.