wpf localization [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 8 years ago.

Improve this question

Which is the best th开发者_JS百科ird party tool available for wpf application localization.

---

Passolo is a commercial product that one of my clients uses -- if you have set up your app with all the strings that need to be translated in resource files, the Passolo app sweeps through them, generates files to send off to your translaters, and lets you pull the translated text back in.

This product is not cheap, though, it's definitely more of an enterprise solution.

---

Have a look at this question -

• http://www.lingobit.com/
• http://www.sisulizer.com/
• http://www.multilizer.com/

Sisulizer and Lingobit claim to handle .NET and WPF but only Lingobit would handle WPF styles correctly.

http://www.schaudin.com/web/page4.aspx

---

I tested all four tools.

Lingobit can correctly localize RESX resource but failed to extract any string from XAML/BAML. Lingobit reported that XAML component have not id even every single component I had has an id. For me Lingobit is unuseabled for WPF.

Multilizer also failed to scan any XAML/BAML data. In addition I could not even enter any translations. Multilizer is a buggy and extremely difficult application to use. I would not recommend it to anybody.

Sisulizer lets you localize WPF assemblies but popups a message that assembly localization is experimental. However it can correcly localize both RESX and XAML if you speaicy Visual Studio project file (.csproj) instead of assembly file (.exe). No problems with XAML styles.

Passolo worked equally good to Sisulizer. It could localize XAML but did not scan all the properties I wanted.

Lingobit and Multilizer could not localize XAML, Sisulizer only if you have full source code and development enviroment installed, and Passolo misses some strings. I am still waiting for perfect WPF localization tool: a tool that can localize all resources of WPF assemblies.

---

I have chosen to use this method(it looks like old one, often used in winforms):

How to use a ResX file in a WPF application: Create a Resource (ResX) file in your project or you can reuse the Properties/Resources.resx file. In the Visual Studio Resource designer you have to change the Access Modifier from Internal to Public. This can be found in the top toolbar of the designer. Add the namespace to your XAML View:

xmlns:p="clr-namespace:Jbe.TestSuite.Infrastructure.Shell.Properties"


The Resources can be accessed via the x:Static markup extension of XAML:

<MenuItem Header="{x:Static p:Resources.FileMenu}">

taken from here.