.Net Localization vs. Branding

Question

Say I have a WCF service, it has several clients, in several languages. It would be wise to use resource files and satellite assemblies to provide localized resource strings.

Now, if these resource lines become branded, for example, two clients in one country, in one language, but have a different terminology, would I make a separate resx file with a separate satellite assembly, or would I miss something?

Adding a proprietary satellite assembly for this client will mean a lot of redundancy for resource strings that are not branded. But, at the same time, it is necessary that all resource lines are branded.

Answer 1

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

We ended up storing all of these resource strings in the database and loading them and fixing them the first time the application was launched.

Answer 2

; , , XML , , , . "", ; , . ( , .)

, , .