Tuesday, 26 April 2011

Server TM, Local TM and why there are 2 fields in the TM settings window

SDL introduced with Studio a new server TM concept, called multilingual server TM.
To understand this new concept, it's first necessary to forget that we talk about a TM, because it is not a TM as we meet it in Workbench for example.
In Workbench, a TM is a database where segments of a specific language pair are stored. The language pair is set at the creation of the TM. If you need to store other language pair, you have to create new TMs.
This concept has been used again for the local TMs in Studio. One language pair, one file.

Now let us imagine, we have a translation project with many target languages. The TMs we want to use are specific for our customer. Their names are almost the same, actually only the target language code is different.
"customer en-fr", "customer en-de", "customer en-it"... SDL decided to group such TMs in a new "object", a kind of TM collection. A server TM is a TM collection.

In our server TM called "customer", we can set as many target languages as we want. When creating a project for our "customer", we just have to select our "customer" server TM. Because you already entered the source and target languages, Studio knows which TM in the collection is to be used and can generate analysis and pretranslations.


Now, how do I have to set TMs in a new project?
When creating a new project, you have the possibility to enter the translation memories (TMs) to use in 2 different ways.
The first way is through the default view. You are in menu "All language pairs/ Translation Memory and Automated Translation" ("1", left pane) and you can add your TMs with the "Add" button (right pane). The TMs can be server TMs or local TMs. You can enter many TMs for a same language pair.

What will happen?
For each target language, the program first filters which TMs have the relevant language pair. Then, he performs the analysis and/or the pretranslation using ALL relevant TMs. In case 2 different 100% matches have been found in 2 different TMs, the segment won't be translated if you keep "1" as "multiple translations penalty" (menu "Penalties", left pane, see screenshot). You'll have to choose between them in the editor.

Then, what is field "2" for?
There is 2 reasons to get the TMs in field "2".
1. The first one is the official documented reason (just press Help to get more information): you use a server TM in which e.g. 4 language pairs have been set but for one of them, you prefer to use a local TM (from another customer for instance) INSTEAD.

In this case, you have to select the language pair in the menu on the left ("2"). Under "Translation Memory and Automated Translation", tick the box "Use different translation providers for this language pair", and select all the TMs you want to use. If you return to "All language pairs", you'll see your specific TMs in field "2" (see screenshot). Only this/these TM(s) will be used for the analysis/pretranslation for the corresponding language.


2. The second reason is a problem of package size:
If you enter 4 local TMs for each language pairs in "1" and wish a TM copy in the translator packages (package options, see screenshot), all 4 TMs will be added in each package.


With big TMs, you'll get a very big package and all the associated difficulties. Maybe SDL will change this in one of the next update.

Friday, 15 April 2011

SDLXLIFF filetype options - embedded file or not?

You may have already noticed that sdlxliff file are pretty big, even if the number of segment to translate is small...
One of the reason is that the original document is embedded in the sdlxliff file itself during the conversion:

you have a 10MB file with a lot of pictures, you convert it (standard settings) and get a 11 MB sdlxliff file although there are only a few segments to translate.

First difficulty: when the sdlxliff file is over 15/20MB, Studio begins to show some difficulties to open the including package, and then the file itself in the Editor. It takes a ......long...... time. Sometimes it crashes (>30 MB on my computer).

Second difficulty: because you have in each language directory a copy of the original file and its embedded clone in the corresponding sdlxliff, this means for 32 target languages, 130 copies of your original file (counting the project packages, return packages and the source language directory!), you must cope with extra data storage costs.

You have the possibility to set a "maximum embedded file size" to limit the size of your resulting xliff file. 
But what happen then in particular if I set this sdlxliff filetype option to zero?

If the storage "problem" is something important for you (how many copies are there if you back-up your hard disk to protect your work from hardware failures?), you can think about it.
But you have to consider these inconvenients:





- The translator may be unable to take a look at the source file. Some source files are not automatically attached in project package, doc file for example. This makes the translation more difficult, particularly when the context is not clear.
- The translator gets a warning message when he tries to open the corresponding sdlxliff file, saying that the source document can't be found. It may make him nervous. (fortunately, he can translate the xliff anyway)
- The project manager can't use the batch task "Update Main Translation Memories", because he can't find the source file. This seems to be a bug, because the source file is always saved, in each (target and source) language directory. I proposed a workaround in a previous post.


I recommand here to let the maximum size on 20, maybe 10 if your computer is slow, to avoid these difficulties. If your files are too big and you set the size to 0, communicate the inconvenients to your collegues and contractors, so that they don't wonder!

Filetype from DTD

If you need to create a new filetype for XML and have the corresponding DTD, you'll have to use Tag Editor.
In Tools -> Tag Settings... you have the possibility to create a ini file out of a DTD.
Then, you can use Trados Studio to create the corresponding filetype out of this temporary ini file Tools->Options->File Types ... Button "New".

Use the many possibility of the filetype options to sort translatable, not translatable and variables and make the translation job easier.

Monday, 11 April 2011

java error when creating a new project with inx files

Message:
Java class not found:
com/trados/filters/interfaces/CustomInfoProperties

Solution:
The problem came with the cumulative update 9. The "java runtime Engine" is automatically started with Studio to improve the functionality of multiterm. This standard setting causes now this problem with inx files, but can be switched off:
in Tools > Options > Java Runtime Engine Startup (see screenshot)
uncheck the option "Start Java Runtime Engine when starting up SDL Trados Studio" and restart Studio.
Now, you can prepare your project.


...Don't forget to check the box again if you plan to work with terminology in the editor...



More information in http://kb.sdl.com. Search "cumulative update studio"

Friday, 8 April 2011

Template is not updated at the end of the project wizard

(---still in Studio 2011---)

When creating a project based on a template, you have an option to update the template at the end of the wizard (see screenshot, in red).
This option seems not to work... so that:
either you have to enter modification direct in your template (File -> Setup -> Project Template...)
or you must save as a new template at the end of the wizard (see screenshot, in green) and overwrite the old one by selecting its file name.

!Patched! File Types in New Project Wizard are not those from my template

Problem:
When creating a new project based on a template, the "File Types" settings in the "Project Files" window (see screenshot) are not the settings from the template, they are your profile's settings.
When looking at the settings from the the last wizard window "Project Summary" (button "Project Settings", see screenshot), the settings are those from the template. So are they also in the project after creating it.

So I recommand not to modify any file type from the "Project Files" window but in the "Project Summary" window (Button "Project Settings") or from the template itself .

Update Main Translation Memories - Could not find file 'myfile.extension' (Update 15.4.2011)

This happened once as we wanted to finalize a project with *.mif files which were merged together into individual sdlxliff files. I couldn't reproduce this case!

(Update) I could reproduce this case. It happens when the SDLXLIFF filetype option "Maximum embedded file size" is set to zero. It has with the merge functionality nothing to do.

Message:
Severity Error
Message Could not find file 'myfile.extension'
File myfile.sdlxliff
Origin Update Main Translation Memories

Note:
- myfile.extension is the document to translate in native format.
- the error happens also when running a batch sequence including the batch task "Update Main Translation Memories", in particular "Finalize".
- the file is there!! it hasn't been removed.
- the batch task export files and generate target translation doesn't generate any error.

Solution(!):
Set the SDLXLIFF filetype option "Maximum embedded file size" to another value so that the file will be embedded
OR
Try the workaround, if you don't want to create a new project / to embed the original file.


Workaround:
make first a copy of the xliff file, in any case. It must be found in the target language directory (e.g. en-US).
Open the xliff file with notepad++.
Replace the expression:
<reference>.*</reference>
with nothing,
with regular expression activated. See Screenshot.

Use "replace all" if your XLIFF contains many files merged together.



This operation will erase a link to the native document which seems not to be usable through the batch task "Update Main Translation Memories".

After that, you can try again "Update Main Translation Memories" in Studio, it could have worked for your case too! (Update) I tried it again with my second case, it worked well.

IMPORTANT
With this modification, you can't run the export files or generate target translation anymore:
This means:
EITHER you convert your file back BEFORE you update your TM
OR you update your TM, then you erase the modified file with your backup copy