XLocalizer Versions Save

Improvements

• New option LocalizeDefaultCultre: Use to enable/disable localizing default culture (fixes #19 )

• Removed deprected property UseExpressValidationAttributes. For latest setup see Localizing Validation Attribute Errors

• c57df238 - Performance improvements, bypass localizing if current culture is same as TranslateFromCulture

Hotfix

• 9647936e fix #9 Resource path for different hosts
• 73b79247 fix #13 Caching keys with reference to resource type

Improvements

• cc269c37 Auto create resource folder if not exits
• f62c766c Improved error logging while writing to resx

XLocalizer for Asp.Net Core

• Localization supported by online translation and auto resource creating
• Use any of the ready online tranlsation services or creat your own translation service
• Easily localize views using simple html attributes and html tags
• Multiple resource type support resx, xml, db
• Customizable resource providers, basicly any file/db types can be used with custom resource providers.
• Export resources from db/xml to resx
• Export from custom resource types using custom exportes
• Easily upgrade from default system localization to XLocalizer thanks to using the standard localization interfaces IStringLocalizer and IHtmlLocalizer. The only code change is in startup.
• The easiest way (almost no additional steps) to localize all DataAnnotation, Valdiation, ModelBinding and Identity errors
• No need to provide error messages inside valdiation attributes, e.g. simply [Required] will generate a localized error message.
• Easily customize all framework errors using single json file or via inline XLocalizerOptions

Notice for preview users

Ex valdiation attributes are deprected, there is no need to use Ex attributes, just replace with the default attributes, and no need to provide error message inside the attribute tags

See all docs: https://docs.ziyad.info/

• New: TranslateFromCulture property to specify the source culture to translate from, if not specified default culture will be used.
• New: All default validation attributes errors, model binding errors and identity errors are customizable/localizable via XLocalizerOptions or Json See https://docs.ziyad.info/en/XLocalizer/v1.0/setup-json.md.

Deprected:

• Express validation attributes are deprected. Use default attributes instead. A new approach has been introduced that allows to customize/localize all framework default validation attributes without the need to use Ex valdiaton attributes.

See all docs: https://docs.ziyad.info/en/XLocalizer/v1.0/index.md

fixes #2

XLocalizer for Asp.Net Core

Localizer package for Asp.Net Core web applications, powered by online translation and auto resource creating.

Say bye-bye to manually creating localization resources...!

- Online Translation : Auto translation of missed localized values. - Auto Key Adding : Auto adding missing keys to the resources files. - Multiple Resource Type Support : Built-in localization support based on .RESX, .XML, DB. Extendable localization support based on any custom file/db type. - Export to Resx : Resources from any source type can be exported to .RESX files via built-in exporters. - Do it Fast : Custom cache support for speeding up the process of getting localized values from sources. - Standard interfaces : Easy to use due to using the standard localization interfaces: IStringLocalizer, IHtmlLocalizer, IStringLocalizerFactory and IHtmlLocalizerFactory.

Documentations:

For all documentations visit: DOCS.Ziyad.info

Sample projects:

Sample projects built with .net5 preview version.