KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Looking for some advice on the best way to implement localization along with client specific jargon on a asp.net site that will be used by multiple clients. For example the labels on a form must vary depending on what client is logged into the site as well as what there language preference is. So there will be a default set of verbiage/jargon for each client... and then each clients verbiage/jargon will be translated into languages they require. I was thinking about created a custom culture for each client and then using the "built-in" localization features in asp.net and resource files. So I might have a default culture... and then client specific cultures... and then client specific cultures translated to other languages. en-US de-DE en-US-client1 en-US-client2 de-DE-client1 de-DE-client2 Does this sound crazy? seems like a fairly sound approach to me... but also maybe a bit of a hack... so I welcome any better ideas? Thanks all for the help!
Tags (comma-separated)
Save Edits
Cancel