.Net Localization vs Branding

Question

Let's say I have a WCF service, it has multiple clients, in multiple languages. It would be appropriate to use the resource files and satellite assemblies to provide localized resource strings.

Now if those resource strings become branded, for example two clients in the same country, same language, but have different terminology, would I make a separate resx file with a separate satellite assembly, or am I missing something?

Adding a branded satellite assembly for that client would mean a lot of redundancy for resource strings that are not branded. But, at the same time in need all resource strings to be brand-able.

Answer 1

We faced the same problems (the customers were able to adapt the initially provided translation) and satellite assemblies did not solve our problem. Resources and assemblies are more suitable for stable content.

We ended up saving all these resource strings in the database and loaded and cached them at first application start.