Improve localization support in DataAnnotations
Today it's impossible to fully localize the view models / validations without using hacks or clutter the view models with the ErrorResourceName etc.
It would be a lot easier to handle localization if you created an extension point where one could register custom string providers.
Shipping in 4.6.2 in summer 2016
Jun 16 there was some action on this:
And include Documentation: http://docs.asp.net/en/latest/fundamentals/localization.html
Sorry, the GitHub link was incorrect. I've removed it from the status for this suggestion.
Rick Strahl commented
Just one comment here. Somebody mentioned Westwind.Globalization (https://github.com/RickStrahl/Westwind.Globalization) and I would love for something like this to be integrated. IOW, a real localization API not just the extremely limited Resources/ResourceReader/ResourceWriter APIs plus the insanely silly .NET resource manager that has no hook points.
But seems to me this is something that has to be fixed at a lower level - especially with MVC which doesn't use providers, but ResourceManagers with strongly typed resources typically. This is something that has to be addressed at the .NET base level so that ResourceManagers have a way to specify where ResourceSets are loaded from.
I would love to have a discussion with somebody at Microsoft about this in the future because the existing system really sucks for extensibility.
http://www.west-wind.com/westwind.globalization/ has a String Database for DataAnnotations etc
The localization must be better, localization string resources must be able to get from custom provider like sql, xml, json, etc.
I really like the way "QT" uses for translations. we must be able to add, modify or remove string resources at runtime, or programatically.
The link to the GitHub page still does not work. Is it a private repository?
Peter Šulek commented
Linke "https://github.com/aspnet/DataAnnotations/issues/43" does not work for me.
Sergey Litvinov commented
Does the link to issue on DataAnnotations repo correct or maybe the repo itself is private? Because it shows 'Page not found' for me.