On Tue, Feb 2, 2010 at 4:05 PM, Ed Leafe <[email protected]> wrote: > Oh, that's so much nicer to code than: self.Application.Language = > <language>
For my current project (C#) I implemented my own translation system. It's a 'port' (i.e. re-write) of an existing xBase++ (think Clipper) application which is already multi-language capable so already I have a large corpus of translated text. The method I used is to implement my own custom GUI controls based on the MS controls. e.g. Label, Form etc. These controls have a LanguageID property which you set to the code that represents the text. The neat thing is that because I implemented my own controls the translated text appears at *design time*. I even added a development-only property to the form that lets you swap between languages. Changing this immediately changes the language. This makes layout of controls easy and avoids the old problem of 'foreign' words being longer than the English equivalent. Maybe it's possible to implement something similar in Fox? (COM control?) I'm too rusty to say for sure... p.s. to whoever mentioned it's not possible to store different languages in a DBF is wrong. We've used this system for 10+ years (for English, Swedish, Norwegian, Estonian, Lithuanian, Latvian, Russian & more). We don't support multi-byte languages, but it is a pain! -- Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
