Yes, the built-in multilingual support in WinForms is dependant on culture names (like "en-US"). If you wanted to use the built-in functionality you'd have to create and install your own locales.
I've seen people use dictionaries, as Paul mentioned. I've also seen people use database lookups, write classes to wrap XML files that contain the contextual text, and use Settings.settings. If it were me, I'd consider keeping the text in the resources and have some sort of wrapper or adapter for the Properties.Resources class to get the right text based on the context. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
