LaTex + SDL Trados 2011 - how to?
Thread poster: Vitals

Vitals  Identity Verified
Lithuania
Local time: 23:26
Member (2008)
English to Lithuanian
+ ...
Mar 20, 2015

Dear all,

I was offered a LaTex format files to be translated in SDL Trados 2011.

How do I configure Trados for LaTex tags, etc.?

Does any of you have experience in that and can provide instructions?

Would be very grateful for your help!

Sincerely,
Vitaly


Direct link Reply with quote
 

Erik Freitag  Identity Verified
Germany
Local time: 22:26
Member (2006)
Dutch to German
+ ...
No easy answer Mar 20, 2015

Dear Vitaly,

I do sometimes get LaTeX files to translate. It looks that there still is no filter available, and it seems that the task of creating one will be worth your while only if you get a whole lot of these files to translate.

Others have invested quite some time before ultimately failing (look here: http://www.proz.com/forum/sdl_trados_support/238618-regular_expression_delimited_text_filter_for_latex.html)

You may want to search for a product called "Tortoise Tagger" - I have no personal experience with it, though.

My solution ultimately is to translate LaTeX files as plain text and just leave the tags untouched. No problem if you know what you're doing.

Sorry that I can't be of any real help. If you get a working filter, please let me know - it's quite some time ago that I looked into this.

Kind regards,
Erik


Direct link Reply with quote
 

SDL Community  Identity Verified
United Kingdom
Local time: 22:26
English
There is an article here... Mar 20, 2015

... by Richard Puschmann that might be useful: http://rpuschmann.jimdo.com/2015/03/20/translate-latex-documents-in-studio-sure/

Regards

Paul
SDL Community Support


Direct link Reply with quote
 

Erik Freitag  Identity Verified
Germany
Local time: 22:26
Member (2006)
Dutch to German
+ ...
Too easy? Mar 20, 2015

Dear Paul,

Thanks for the link - looks promising, but it looks like you'd have to repeat steps 8ff. for any LaTeX command (of which there is a large number if you take the standard commands, and an infinite number if you want to include user defined commands or packages, which is quite a standard procedure in LaTex)?

Regards,
Erik


Direct link Reply with quote
 

Meta Arkadia
Local time: 04:26
English to Indonesian
+ ...
Theoretical workflow Mar 22, 2015

[still downloading tons of LaTex related stuff, fascinating stuff]

I think the following could work:

- Open the Tex file in an editor that can handle it, and can
- Print the resulting text as PDF (requires plug-in). That PDF file would contain the visible text (that needs to be translated) plus images, formulas, and things, but no code
- Extract the text from the PDF, save as plain TXT, delete any (references to) images/formulas
- Translate in your favourite CAT tool, and save the translation as a TMX file (or other suitable memory format)
- Start a new project with the original .json file as plain text file*
- Run "Insert perfect matches from memory"**
- Populate empty source segments**
- Export.

* You may want to add " as a segment delimiter.
**I take it the CAT tool offers those features, don't know about Trados.

Cheers,

Hans


[Edited at 2015-03-22 11:37 GMT]

[Edited at 2015-03-22 12:33 GMT]


Direct link Reply with quote
 

Meta Arkadia
Local time: 04:26
English to Indonesian
+ ...
Nice try... Mar 22, 2015

... but the procedure above can - and therefore will - go wrong if there's any extra formatting within a segment.

An example from the Wiki:



Since I don't have the plug-in yet (still downloading the el-cheapo way, at night only), I can't produce the PDF yet, but it's there one the very same Wiki page. Because of formatting, simply extracting the text from the PDF is going to produce misery. If there's formatting within a sentence/segment, like LaTeX and TeX above, the text will have to be copied piece-by-piece, copying things like LaTeX and TeX as a separate segment.

H

[Edited at 2015-03-22 12:56 GMT]


Direct link Reply with quote
 

SDL Community  Identity Verified
United Kingdom
Local time: 22:26
English
You're right... Mar 23, 2015

Erik Freitag wrote:

Thanks for the link - looks promising, but it looks like you'd have to repeat steps 8ff. for any LaTeX command (of which there is a large number if you take the standard commands, and an infinite number if you want to include user defined commands or packages, which is quite a standard procedure in LaTex)?



... it is tricky because of the number of commands and particularly the user defined stuff. I couldn't see an obvious place where all this information is available in an easily digestible format but for the specific files I have seen from Vitaly (he emailed me off forum) I resolved it like this... for interest.

I extracted all new lines that started without any code as these seemed to be translatable text in these files and I added the specific lines starting with code that also seemed to have translatable text. So this gives me an import of all the stuff that should be handled plus any inline tags. I did this with a single expression that can be expanded as necessary in the document structure section of the regex filetype:

Opening Pattern
^(?!\w|\\chapter|\\item).*|^

Closing Pattern
$

So here you can see I added \chapter and \item as these also seemed to contain translatable text.

Then I used the inline tags to protect code in the extracted lines. I needed three placeholde rules for these files:

\\chapter{
}$
\\item

This does a neat job on the three files I saw. But you're right that this won't do them all. I also think that even if we created a filetype to handle all the specified tags (whatever they are?) then you would still need the flexibility to add your own custom tags as well. So tricky as you noted.

But perhaps this approach would allow you to handle most of what you could identify on a scan through the files and then you could always handle any exceptions in exactly the same way you do now, but making sure you added them to your filetype so that over time your filetype became more and more capable, encompassing more variations.

The best solution of course would be to see a thorough specification and then create a proper filetype for these files. Interesting problem though.

Regards

Paul
SDL Community Support


Direct link Reply with quote
 

SDL Community  Identity Verified
United Kingdom
Local time: 22:26
English
Actually on reflection... Mar 23, 2015

... the inline tags could be better handled like tnis I think and then you "might" get away with only having to edit the document structure line by adding any new elements that contain translatable text:

\\\w+
}$
{


All good fun and depends on what the names of these elements look like!

Regards

Paul
SDL Community Support


Direct link Reply with quote
 

Dan Lucas  Identity Verified
United Kingdom
Local time: 21:26
Member (2014)
Japanese to English
I recommend the simple approach Mar 23, 2015

SDL Community wrote:
All good fun and depends on what the names of these elements look like!

I was mildly obsessed with TeX/LaTeX back in the late 1980s as there wasn't much else out there that would do "real" typesetting back then. I still have the TeX and Metafont books hanging around. Brings it all flooding back! It is an elegant and fascinating system and still widely used in academia.

Having said that, I'd be inclined to suck it all into Studio and just translate the text by overwriting it, as suggested by someone earlier. Once I would have seen this as a challenge, now I just think "Life is too short".

Regards
Dan


Direct link Reply with quote
 

Vitals  Identity Verified
Lithuania
Local time: 23:26
Member (2008)
English to Lithuanian
+ ...
TOPIC STARTER
Some help is still needed... Mar 27, 2015

SDL Community wrote:

... the inline tags could be better handled like tnis I think and then you "might" get away with only having to edit the document structure line by adding any new elements that contain translatable text:

\\\w+
}$
{


All good fun and depends on what the names of these elements look like!

Regards

Paul
SDL Community Support


Dear all,

Paul has been extremely helpful in my problem.

I am still struggling with a few files, and did not quite understand this recent post. Paul is away on a leave, so he is unavailable.

Can anyone explain how I can implement this:

\\\w+
}$
{


Thank you in advance.

Vitaly


Direct link Reply with quote
 

SDL Community  Identity Verified
United Kingdom
Local time: 22:26
English
I sent you... Mar 27, 2015

... an updated settings file. These last three files you sent me start to make it trickier but I think I got it. used these:

Opening Structure
^(?!\w|\\chapter|\\item|\s*\\caption|\s*\w).*|^

Closing Structure
$


Inline tags
\\\w+
}
{
(This one I also added an "Exclude" in the advanced settings to break the text)
\\\\

Hope this does it for all your files now.

Regards

Paul
SDL Community Support


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

LaTex + SDL Trados 2011 - how to?

Advanced search







WordFinder
The words you want Anywhere, Anytime

WordFinder is the market's fastest and easiest way of finding the right word, term, translation or synonym in one or more dictionaries. In our assortment you can choose among more than 120 dictionaries in 15 languages from leading publishers.

More info »
Anycount & Translation Office 3000
Translation Office 3000

Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search