StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POn-Tiered .NET application localization guidelines
text
Body
copied!<p>I would like to get some of your ideas about </p> <ul> <li><strong>resource name / categorizing</strong></li> <li><strong>place of resources</strong></li> </ul> <p>Let me just give you the scope of the application:</p> <ul> <li>3 or more supported languages</li> <li>3 MVC websites [with a lot of shared resources, and also some unique resources]</li> <li>1 shared MVC extensions library</li> <li>1 core business library, which has shared functionality, and business objects [also contains resources]</li> <li>3 business libraries that have specific business logic for the three websites [also with resources]</li> <li>1 SQL 2008 database shared among all websites, sends sometimes localized emails.</li> </ul> <p>I would like for it to be easily maintainable (so also easily exported/imported for translation), not to be duplicate (since we have common resources), and understandable for everybody that comes in contact with the code</p> <p><strong>Place of the resources:</strong></p> <ul> <li>should I create one assembly containing all the translations? And create a reference to that assembly in my projects (even if possible adding it to SQL server)?</li> <li>or should I use source control to keep all the resource files in sync?</li> <li>some other ideas?</li> </ul> <p><strong>resource name / categorizing:</strong></p> <p>So we have localized emails, text on buttons (command like texts), labels, error messages, information messages etc etc.</p> <p>How do you categorize these items into resources files, do you just dump them all in one file? Or do you categorize them into a <em>strings</em> , and an <em>emails</em> resource files, which categorization do you use?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload