Feb 25, 2011 06:43 AM|vshlos|LINK
Putting everything in a resource file is pretty hard when you are thinking about formatting and scripting and stuff. This generally means that you either have to start putting html tags in the resource file, or have many many resource values. Also for a
page that is just a lot of content such as a "Terms and Conditions" page, that can become a very big hassle.
Our approach is to use the right tool for the right job. Bigger things which require more code content, we placed those in seperate files inside a folder for the right culture. So a page like "Terms" would go in "~/Views/en-US/About/Terms.aspx" as well as
"~/Views/pt-BR/About/Terms.aspx". Each culture would have its own file. Combining resource file values with culture specific pages and partial rendering of shared pages makes it pretty simple to include globalization.
The approach is pretty simply, but I already wrote a blog about it so, just see it here:
We structured the code to be more cultured for example:
~/Views/en-US/Home/Index.aspx - is only in english
~/Views/pt-BR/Home/Index.aspx - is only in portuguese.
~/Views/Shared/Site.Master - Has resource file lookup values