Globalization in ASP.net MVC (Resource file per View vs Domain) -


what best practice keeping resource files when comes asp.net mvc globalization ?

for example, have order processing system if try keep our resource files domain i.e order.resx, customer.resx, etc

or else try keep resource files per view i.e orderprocessingview.resx, customerview.resx, etc

common strings such "add", "edit", "delete" can handle using common.resx file.

or there other approaches keep resource files ?

we using client side rendering (jquery templates, kendo templates) also.

one of localizability best practices not reuse translations in different contexts. that's because want allow translator use different translations 1 same piece of english text in different contexts. why? because different languages have different rules (e.g. depending on gender, adjective can take different form) , because of context-specific constaints such space limitations (e.g. translator may forced shorten string make fit somewhere, shouldn't have when it's not necessary).

for reason, having 1 .resx per view practice. if had 1 big .resx, hard determine view string goes (and you'd more tempted reuse strings in different contexts). you'll typically need global .resx application view-independent, should rare.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -