Hi Daniel,

in Studio you get your translated files in the correct formt by running the batch task "Finalize":

In the following dialogue, click "Finish" unless you want to customize settings, then "Close" after the process is done.

You will then be asked whether you want to open the folder containing the finalized files. Select "yes" and you will see the files. If this dialogue box does not come up, select "Explore containing folder":

It will be obvious which is the target file (in your case it will be a pdf) and which are Studio's files (sdlxliff).

For me, there was a learning curve with Studio, but I want to make you aware of what in my eyes is part of the quality of the product, and that is the excellent documentation. Click "Help Topics" on the "Help" tab in the ribbon to get there. Also, there are many video tutorials especially covering the basic steps. If you are looking for help with a specific problem that is not covered by the above mentioned sources, try Paul's blog, which is a very good resource for the more in-depth issues: https://multifarious.filkin.com/

Lots of fun!

Daniel

Daniel

Hi Daniel Schechter 

To add to what  has posted, first a correction: The Target file resulting from a PDF is always a Word document. If you need a PDF to return to the client, you can open the document in Word and save as PDF.

An advantage of the above is that you can also save a Source Word file and take a look at it before you translate in case there is any way it needs improvement, in the layout for example. Then, if you want to you can make changes to that Word file and create a new translation project with it.

A quick easy way to do this is to open the resulting SDLXLIFF in Studio then do the following:

Go to File > Advanced Save > Save Source As

Likewise, a simple way of creating a Target Word file when you have the SDLXLIFF open in Studio is:

Go to File > Save Target As

Make sure you note where the file is being saved so you can navigate to it via Windows Explorer and open it.

I hope this helps,

All the best

Ali

Hi Daniel Hug

Yes, I can understand that. PDFs cover a wide range of accessibility. If a PDF is formatted as an image, it's best to use an OCR program to convert it to text before attempting to translate it via CAT.

That being said, I'm surprised how good Studio has become at processing PDF - though I guess one can also say that PDFs tend to be better compiled these days too!

Have an excellent weekend,

All the best,

Ali :)

Hi Daniel,

as I pointed out above, I always tried to avoid using pdf files as source (for anything). The pdf format is simply designed to be an output format. Its benefit is that it displays/prints satisfactorily on about every platform/printer/program. (Almost.) This file format is not designed to be processed further. It is possible to process it further, but you are working against the grain, so to say. (I understand you did not have a choice.)

Depending on how complex the layout is, it can be hard to get Word to replicate it. IMHO replacing text in a pdf using Acrobat Pro is a Verzweiflungstat.

One way to approach the issue might be to first of all try to get a suitable source file. Ask your customer whether they have the document source, e.g. the InDesign or Word file from which the PDF was generated. Or try the "Export" function of Acrobat Pro. (Quite impressive.) If that does not work, try Studio's pdf filter.

All the best,

Daniel

PS: Vote for the improvement of file handling! Here: https://community.sdl.com/ideas/translation-productivity-ideas/i/trados-studio-ideas/enable-more-document-structure-information-when-using-the-embedded-content-processor