I hope this is the right newsgroup for this question: What tools do you
use to translate .NET resource files? We have an in-house translator,
but I can't give him a bundle of RESX files and an XML-editor, can I? I
looked at a few products I found on the net, but none of them looked
entirely convincing, so I'd like to have a few unbiased oppinions: What
tools do you/your translators use, and are they any good?

Thanks in advance!

Niki

Hi Niki,

I have used few localization tools to localize .NET applications. A
year ago I used Multilizer. It was a good tool but there has been no
support or updates for long time. That's why about a half year ago I
started to look for other tools. I tested Passolo and Catalyst but they
did not support .NET 2.0 and were very hard to use. Few weeks ago I
started to use a new tool, Sisulizer (www.sisulizer.com). It supports
..NET 2.0 and is very easy to use. The product is brand new so there has
been some small issues but Sisulizer's people have always fixed
everything very fast. Now it works very well for me. Price was also 1/3
of the other tools (1500 USD)

One issue that is very important for me is that I can easily send the
project for my translators and they must be able to use the tool
without installing .NET runtime. Passolo requires .NET runtime.
Sisulizer does not.

Another feature that I like in Sisulizer is the command line tool. I
can use it im my make file that first builds my application and then
also creates the localized satellite assembly files for me. Everything
goes automatically.

I need to localize also XML and Sisulizer works with XML too.

Best regards,
Johannes

Thanks a lot Johannes!

I tested Multilizer first, but it simply crashed every time I started
it, so I gave it up. I also found Catalyst, and it seemed to have the
best WYSIWYG support of the products I tested, but it's quite
expensive. I've tested Sisulizer but it can't display all of the
controls properly, and only shows small rectangles for user-controls,
so the translator would have to launch the application to see if all
the strings she inserted fit. I still have to test Passolo, but I don't
have a demo-pw yet.

Hi Niki,

I had the same problem. Fortunately it is easy to fix.
It seems that you have 3rd party component. In order to get the visual
appearance right you have to map them.
After creating the project the log contains some hint lines. Select
each of them and the unmapped component appers. Right click the
component and choose Map. Then select the right component type. After
rescan the component should show all right.
You can go to Sisulizer's support forum www.sisulizer.net. They usually
reply fast.

Best regards,
Johannes

Hi Niki,

I see that you haven't yet tested PASSOLO! Beware one thing in testing - most vendors give you 'Demo' licenses which are pretty and aesthetic but lack the full functionality to render .NET2.0 forms.
.NET2.0 devleopers are voting with their feet these days with PASSOLO as it supports .NET2.0 out of the box, is so easily customizable, has a low entry cost and is easily mastered so that you can get localizing right away.
If you care to drop me a line at passolo@opticentre.com, I'll fix you (gratis ) a full working Developer version of PASSOLO, and even a webinar/walkthrough of all the features.

regards....j

josephd wrote:

Actually, the other vendors (Sisulizer, Catalyst) did give me demo
licenses I tested with my own .NET 2.0 forms. I asked Passolo for a
demo license more than a week ago, but didn't get more than a "this
will take a few days" reply. To be honest, if it takes that long just
to make a demo key, I don't really want to find out how long it would
take to get support if I had a problem with their product.

n.estner (AT) gmx (DOT) de wrote:
Multilizer crashed all the time and the rest were too expensive for us
at the moment, so we tried using Lingobit Localizer, so far it works
quite steady. They've got demo on lingobit.com, check it out.