Sorry to let you down hard but there is only one solution. Hard graft and
pain.
One method that Microsoft uses is to do localization into a language that
doesn't resemble anything remotely readable. If you can read any part of the
UI, it's not correctly localized.
You need to read up on satellite assemblies.
--
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"per9000" <pe*****@gmail.comwrote in message
news:58**********************************@p25g2000 hsf.googlegroups.com...
We have a big application written without thought of supporting
multiple languages with lots of strings in a default "english". Now
the client wants to support any language (with a latin alphabet) and
we need to redo a lot.
I'm sort of thinking that we are not the first ones to end up in this
kind of situation and I'd like to know if there are any tested and
trusted ways of implementing a multi-language application.
Thanks,
Per 9000