On Wed, 21 Nov 2007 10:27:48 -0500, Peter Ritchie <[EMAIL PROTECTED]> wrote:
>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. sounds unpleasant. > >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. I've seen people tag the controls, and recursively scan all the forms looking up the translation, it was pretty slow and horrid. > >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. What do you mean by "keeping the text in the resources"? How would you go about wrapping Properties.Resources class? > >=================================== >This list is hosted by DevelopMentor® http://www.develop.com > >View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
