For most ASP.NET work I use a hybrid of client and server resources. I manage resources on the server and also publish them as client side resources (ie. publish the resx resources as JSON resources to the client).

This works well for server rendered and server/client hybrid apps.

For mostly client rendered apps (angular, ember etc.) though I'm considering just using JSON resources on the client which is easier.

One advantage of the server rendered resources is that you can do nice stuff with resource providers including runtime translation as I doo with my West Wind Globalization toolkit:

https://github.com/RickStrahl/Westwind.Globalization

Makes managing and editing of resources much easier and includes the tools to serve resources in a variety of ways...


+++ Rick ---

>Hi,
>
>Don't know if this is the best forum but:
>
>I'm looking at the various options for hosting a multi-language web site and wonder what others are using.
>
>Seems like I have two basic options for doing the translation:
>
>(a) Server side with ASP.NET and resource files.
>
>(b) (Since I'm using angular anyway) Client side using angular-gettext, angular-translate or similar.
>angular-gettext seems, on the face of it, simpler to implement.?
>
>
>Client side appeals most since, at the moment, nearly all pages are delivered as static html.
>Also a large part of the app is designed to work offline. Not likely that a user would want to switch languages whilst offline but client side translation would allow that.
>
>
>As I side note - I read this : http://blog.altoros.com/speed-up-i18n-in-angularjs.html and saw an interesting line regarding latency:
>"An additional 100ms delay led to Amazon’s sales to decrease by 1%"