views:

59

answers:

1

Hi guys,

I'm developping a little application in WPF and I want to localize my resources. I've always used resources files (.resx), but I heard about BAML that was suppose to change the way of manage localization in a WPF application.

I made my research and I found a way to translate my application using those files.

I wrote a blog post to show how I did it over here (french only, sorry). You can see references at the end of the post for english links.

The fact is, I really dislike this way of managing resources. I think it's way more complicated and I don't see the pros of using this method.

Am I wrong or did I misunderstand something about BAML ?

Thanks.

+2  A: 

I think you've got a fairly good grasp on the concept, and yes, it is too complicated.

BAML is just compiled XAML. You're using an external tool to extract the resource, make changes, and embed your resources back. It's definately not streamlined, and hopefully this process is made easier in the future.

Even on the documentation of the process, you'll notice at the bottom someone has recommended using .resx instead of this process. If this is already a method you're using for localization, you probably won't find much advantage in taking the LocBaml route.

Will Eddins
Allright, you just confirmed what I thought.Thanks Will.
esylvestre