REG. Locbaml Vs ResX

  • Thread starter Thread starter Naveen
  • Start date Start date
N

Naveen

hi, I am having difficulty on deciding whether to use resx or locbaml for
localizing the project. is resx is the better way to implement localization
or the locbaml tool of way. What are the cons with the two approaches.
-Naveen
 
hi, I am having difficulty on deciding whether to use resx or locbaml for
localizing the project. is resx is the better way to implement localization
or the locbaml tool of way. What are the cons with the two approaches.
Click to expand...

Use the technique that's optimized for the UI framework that you build
on. If it's WinForms, then you should use resx string tables
(especially since WinForms designer aids you there with
Localizable=true). If you use WPF, then also use x:Uid and LocBaml.
 
There are a number of very good solutions posted on Code Project and
elsewhere (see links in the above blog) that use Markup extensions to
get localizable resources from resx files.  These have the following
advantages over LocBaml:

* Visual Studio can be used for the complete build process (including
building satellite assemblies)
Click to expand...

I may be missing something here, but since VS uses MSBuild anyway,
anything that can be achieved with MSBuild can be done for any VS
project (excepting .vcproj, but it's not relevant for this
discussion).
* User Interface language can be changed at runtime (after the window
has loaded)
Click to expand...

Frankly, I don't see such a requirement often, so I would tend to view
it as a rather specialized one. But I can understand the issues
arising there.
* Standard 3rd party localization/globalization tools that handle resx
files can be used if required for managing the translation process
Click to expand...

This is the usual caveat with using any new tech - the tools must be
given time to catch up. However, since LocBaml deals with .csv files,
I don't think it'll take a long time :)
 
Back
Top