New converter for SDLTM & SDLTB files

[Dominique Pivard]

Hi!

There's a new converter for SDLTM & SDLTB files (format of translation
memories and termbases used in SDL Trados Studio):

http://wordfast.fi/blog/cat-tools/2012/11/03/convert-sdltm-and-sdltb-without-studio-and-multiterm/
http://wordfast.fi/blog/?p=522
or
http://youtu.be/L0t9n5yZaaQ?hd=1

It can be used by people who have to translate Studio packages
(SDLPPX) without using Studio. Studio packages are ZIP files that
usually contain a TM (SDLTM), a termbase (SDLTB) and document(s) to be
translated (SDLXLIFF). Hans L. already posted instructions on how to
translate SDLXLIFF files in CafeTran.

The new converter is an alternative to existing tools that have been
released recently: Thomas van Nellen's Visual Basic script (see
http://wordfast.fi/blog/?p=491) and Gerhard Kordmann's
GlossaryConverter (see http://wordfast.fi/blog/?p=497). It's much
faster than the script (but it doesn't retain tags in translation
units) and, unlike GlossaryConverter, it can be used even if you don't
have MultiTerm. Like the existing tools, the converter is
Windows-only.

Cheers,

Dominique

[Hans list]

Dominique Pivard wrote:
> Hi!
>

Hi!!!!

> There's a new converter for SDLTM & SDLTB files (format of translation
> memories and termbases used in SDL Trados Studio):
>
> http://wordfast.fi/blog/cat-tools/2012/11/03/convert-sdltm-and-sdltb-without-studio-and-multiterm/
> http://wordfast.fi/blog/?p=522
> or
> http://youtu.be/L0t9n5yZaaQ?hd=1
>

Great software, nice screencast. Now I now where the CAT in CATguru comes from :).

We'll add the author, Jean-Philippe, to the Gallery of All-time Good Guys ;).

It is good to see that many approaches are being made to directly process sdlxliff and sdlxppx with other tools, that offer more features, higher speed, lower prices, more flexibility, smaller footprints.

It is even better to read that SDL is committed to keep the sdlppx packages unencrypted, whereas it would be easy for them to protect their assets by encrypting their packages:

http://www.proz.com/forum/sdl_trados_support/236507-sdl_encrypting_studio_packages.html

This promise will make it easier for CAT tool developers to add code to directly process sdlppx packages, now that they know there programming investment won't be lost when Studio 2013 is launched.

This was this week's Great News for me ;).

For the record: I don't have any grudge against Studio or SDL (AMOF I admit it has some nice features), it is just that I don't want to be forced to use this software, since it doesn't fit into my personal workflow.

Go with the flow. Let the spirits of Cath protect U.

Cheers,

Hans

[Rene]

On Sun, Nov 4, 2012 at 5:52 PM, Hans list <hans...@gmail.com> wrote:
Great software, nice screencast. Now I now where the CAT in CATguru comes from :).

We'll add the author, Jean-Philippe, to the Gallery of All-time Good Guys ;).

It is good to see that many approaches are being made to directly process sdlxliff and sdlxppx with other tools, that offer more features, higher speed, lower prices, more flexibility, smaller footprints.

Absolutely! I will check this out ASAP.

It is even better to read that SDL is committed to keep the sdlppx packages unencrypted, whereas it would be easy for them to protect their assets by encrypting their packages:

Don´t trust them too much on that. It is a safe bet that the next, "improved" Trados format is already in the works for Studio 2013 or 2015, and of course the downward compatibility will be limited.

Don´t expect a tiger to change its stripes or Trados its business formula.

Regards
Rene

[Dominique Pivard]

On 4 November 2012 10:52, Hans list <hans...@gmail.com> wrote:

Hi Hans!

> Great software, nice screencast. Now I now where the CAT in CATguru comes from :).

Thanks! That was my younger cat, the older one turned 18 yesterday,
you can see both here:

http://goo.gl/Ae7ww

> We'll add the author, Jean-Philippe, to the Gallery of All-time Good Guys ;).

He's the guy who wrote Wordfast Server, the engine behind Wordfast
Anywhere. He knows a few things about programming.

One thing to note is that there are shortcomings in the SDLTB -> CSV
converter. Jean-Philippe only had a very simple SDLTB to work on, the
small sample termbase that came with the Studio trial, which I sent
him (he hasn't got Studio/MultiTerm and doesn't know anything about
it). It turns out that larger/more complex termbases are not converted
correctly, or even not at all. But it's just a question for him to get
to see such large/complexe SDLTB termbases. If you have some, please
feel free to send them to him, so he can make the necessary
improvements to the converter.

Cheers,

Dominique