Re: How to build the multi-language application?
- From: Grant Frisken <grant@xxxxxxxxxxxxxxx>
- Date: Wed, 29 Oct 2008 04:17:52 -0700 (PDT)
On Oct 29, 12:13 am, "Herfried K. Wagner [MVP]" <hirf-spam-me-
h...@xxxxxx> wrote:
You can send the ResX files to a localization agent who canlocalizethem
using VS Express. This way even images and other types of resources can be
localized. Even Windows Forms can be localized by another company using
"WinRes.exe".
While resx files are good it can be hard to manage localization of
large projects with many resx files and ensure consistency of
translation between different forms and controls. If you use
external translators then you must also manage the change process ie
if you make changes to resources they have already translated how do
you track these and ensure that the changes are translated.
Using the out of the box localization tools you typically follow these
steps: Send the translator the resources to translate. They translate
resources and send them back. You build the application and send it
to the translator for verification. They find issues and you go
through the whole loop again. This process can be quite time
consuming because there is no way for the translator to see or run the
translated forms and controls. For simple forms you can use WinRes
to view and edit form resources. It does not, however, cope well
with complex forms containing custom controls. You could give your
code to the translator and get them to use Visual Studio Express to do
the editing - but do you really want a translator mucking with your
code?
For the above reasons you should consider using a third party tool to
manage the localization process. There are a number of localization
tools on the market including Globalizer.NET (www.infralution.com/
globalizer.html) which my company Infralution sells. Typically these
tools scan your solution/projects for localizable resources and
consolidate these into a single package that you can send to the
translator. When the translator completes translations they send
them back to you and the tool provides a mechanism to import the
translations and build the localized resource files. You can then
build your application using the standard Visual Studio build
process.
Globalizer.NET in addition to providing these standard localization
management tools provides a free Translator Edition that enables the
translator to preview the actual translated forms and controls as they
translate. The Translator Edition can even build the localized
binary resource assemblies (without requiring your code or Visual
Studio to be installed) which allows the translator to run the fully
localized application without having to go around the build-translate-
build loop.
Regards
Grant Frisken
Infralution
www.infralution.com/globalizer.html
.
- Follow-Ups:
- Re: How to build the multi-language application?
- From: Herfried K. Wagner [MVP]
- Re: How to build the multi-language application?
- References:
- How to build the multi-language application?
- From: yxq
- Re: How to build the multi-language application?
- From: Cor Ligthert[MVP]
- Re: How to build the multi-language application?
- From: Herfried K. Wagner [MVP]
- Re: How to build the multi-language application?
- From: Cor Ligthert[MVP]
- Re: How to build the multi-language application?
- From: Herfried K. Wagner [MVP]
- Re: How to build the multi-language application?
- From: Screaming Eagles 101
- Re: How to build the multi-language application?
- From: Cor Ligthert[MVP]
- Re: How to build the multi-language application?
- From: Herfried K. Wagner [MVP]
- How to build the multi-language application?
- Prev by Date: Re: Include content stream png in HTML email as image?
- Next by Date: Re: Timer won't start from serial port receive routine
- Previous by thread: Re: How to build the multi-language application?
- Next by thread: Re: How to build the multi-language application?
- Index(es):
Relevant Pages
|