Friday, 11 November 2011

Error Message Collection - Problem/Solution


(error displayed in Task Results after trying to convert a doc file)
Pre-Scanning failed to identify the file type, the following messages were generated:
Pre-Scanning Error: The file you are opening does not contain any bilingual segments.

The doc file is set as reference.

Possible Solution:

-> Project Settings -> Microsoft Word 2000-2003 -> Common
Process files with tw4winmark style: checked


Invalid URI: There is an invalid sequence in the string

Type      System.UriFormatException...
Source   Sdl.FileTypeSupport.Filters.Word


-> Project Settings -> Microsoft Word 2007-2010 -> Common
Extract hyperlinks: Never process hyperlinks

Saturday, 1 October 2011

No more Studio icons after Studio 2009 deinstallation...

The installation of Studio 2011 is not a great deal. The software is compatible with Studio 2009 and Trados 2007, no conflict occurs at all, even between the Multiterm version. More, you will find in the terminology recognition of Trados 2007 a new Multiterm Version dropdown value: "Multiterm 9". You won't need to use the component Multiterm side-by-side anymore. More info about compatibility in SDL knowledge database

We planed to install Studio 2011 with Studio 2009 together, so that project managers can finalize old 2009 projects and begin to create 2011 ones. Actually, we discover only one problem during our control checks. This happened at the end, as we de-installed Studio 2009:
the icon of the sdlproj, sdlrpx, sdlppx and all other sdl extension disappear in Windows Explorer and a double-click on each type of files leads you to the classical "Windows cannot open this file" window.

The same occurs with Multiterm and the .sdltb extension.

I can't confirm that selecting the right program for each file type will help you to recover the settings as they were before the Studio 2009 deinstallation. We just did not test it.
We prefer to be sure that everything is OK by rewriting the Windows registry and run it . This will also save time for our project managers and translators.
The following registry code comes from a computer where only Studio 2011 was installed. It is written in a .reg file which has to be double-clicked to rewrite the registry.

IMPORTANT: I cannot assure that this registry code will work on your own system, you may have to do some corrections, for example adjust the exact path of Studio 2011 from your installation. I can't be held responsible for any damage on your system.

Windows Registry Editor Version 5.00





"Content Type"="application/sdltb"







@="SDL File-Based Translation Memory"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\FileBasedTM.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openFileTm \"%1\""

@="MultiTerm 2009 Termbase"

Program Files\\Common Files\\SDL\\MultiTerm8\\Sdl.MultiTerm.TermBase.2009.ico\""




@="SDL File Type Settings"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\FileTypeSettings.ico\""

@="SDL WSXZ Document"



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openPackage \"%1\""

@="SDL XLIFF Document"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\XLIFFDocument.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openDocument \"%1\""

@="SDL Trados Studio Project File"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\Project.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openProject \"%1\""

@="SDL Trados Studio Project Template"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\ProjectTemplate.ico\""

@="SDL TMS Project Package"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\ProjectPackage.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openPackage \"%1\""

@="SDL TMS Return Package"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\ProjectReturnPackage.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openPackage \"%1\""

@="SDL Trados Studio Project Package"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\ProjectPackage.ico\""



Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openPackage \"%1\""

@="SDL Trados Studio Project Return Package"

Program Files\\SDL\\SDL Trados Studio\\Studio2\\ProjectReturnPackage.ico\""



@="\"C:\\Program Files\\SDL\\SDL Trados Studio\\Studio2\\SDLTradosStudio.exe\" /openPackage \"%1\""

Thursday, 15 September 2011

Studio 2011 is coming

A new software version often means new features, new improvements and problem resolutions. I had the opportunity to work with SDL as beta tester and I can announce this: I had more fun working with Studio 2011 as with the precedent version.

Translate to Fuzzy and Perfect Matches revival

Compared to Trados 2007 and the good old TagEditor and Workbench, Studio 2009 lost very important features which couldn't be implemented quick enough in the new environment. To me and for a lot of my colleagues, the greatest lost for translators was the Translate to Fuzzy function. Now it is back...

The most important feature for project managers and important customers and the reason why we didn't upgrade some of our projects to Studio 2009 was the Perfect Matches. They are back too...

The only reason you can invoke to postpone the migration of your Trados 2007 projects is: you do not have the time now!

2 brand new features kept also my attention:

Reviewing and learning effect

Translation reviews can now be done with "Track changes". The feature works like in MS-Word: the reviewer enters its corrections which appear underlined red or stroke blue and the translator can quickly see which segments have been modified, and in case he has to take himself the final decision: he can accept or reject the reviewer propositions with a single click.

Pseudo-translation: better prepare your translation

The second new feature is the so called "Pseudo-translation": implemented in the batch task collection, helps you to generate a "pseudo" or "dummy" translation to check eventual problems who generally appear far too late: after the translator terminated his job. Check for example that the file can be converted back or check that the whole document will be correctly converted and no "jpg text" is left untranslated. Because it is a batch task, it can be easily included in a task sequence. For the OpenExchange developer, this is good news to improve automated workflows.

If you want to learn more about Studio 2011 and its new features, you can also take a look at the SDL Blog and Videos.

Time to migrate

I already told my conclusion to my IT colleagues at DSC: let's install Studio 2011, when it officially comes out, let us take the time to do it. We'll get this time investment back very soon. I'm not saying Studio 2011 is flawless. It will come out with old bugs which have not been seen yet and new bugs connected to the new features. It will also come out without possible improvements that translators ask for years but which couldn't be seriously programmed to satisfy the software performance and stability.

But indeed, that's exactly the most important fact (at least on my personal computer): Studio 2011 is more stable and is faster. As project manager, translator or reviewer, you have the opportunity to do your job quicker. Just take the time to learn your tool.

Friday, 24 June 2011

!Patched! Studio: how to exchange file types without losing your mind?

After having created a new XML file type, I wanted to transfer my settings to a project manager colleague of mine, so that he could prepare a new project. I thought the process would be quite straightforward, but guess again, it wasn't. I don't think that this predicament falls under the category of "designed behavior".

My first try:

I named my file type "Bugged" in the following example.
After saving the file type in "Tools/Options", the file "bugged.sdlfiletype" was created in the folder My Documents\SDL Trados Studio\File Types\. I send the file to my colleague.
He tries to "Add" a new file type, but the file was empty!

I discovered the next day that the file type settings are NOT stored in the the "filetype" files. The file type appears to be merely a container of sorts and the settings are stored somewhere else!

so I tried the following...

Second try: 

I clicked the "Export Settings..." button

Everything seems to work correctly: in this case, an sdlftsettings file was created. I sent this file to my colleague. who then wanted to import the settings by clicking the "Import Settings" button.

But to our surprise, Studio did not ask for an sdlftsettings fils. It wanted a file with a plain vanilla xml extension (see above)!!!

What's the hack?

To make a long story short, I analyzed both our PCs only to discover that we were both using difference interface languages: he was using German, and I had English.
In other words, this file setting problem appears to be a localisation issue ;)

Solutions to the problem?

Simply change the file extension (from xml to sdlftsettings and vice versa) or else switch to another interface language.

Monday, 20 June 2011

Multiterm: termbase downgrade needed?

Multiterm hasn't been modified a lot on the database level between 2007 and 2009. The compatibility between these 2 versions is not as limited as it seems: file extensions are different but contents are very similar.  
SDL documented how to upgrade a 2007 termbase. Here the way to downgrade a 2009 termbase. It's not that I prefere 2007, just that Studio is not to be found on every translator's computer.

2009 server termbases have to be exported (use the default filter, you get an xml file) and imported on the 2007 server. The definition file of 2009 (xdt file) can be used on 2007 without any modification.

To downgrade local termbases, it's much easier. Just change the extension from "sdltb" to "mdb"!
In Multiterm 2007, use "Load External Termbase..." in "Termbase" to load it in your Multiterm Desktop 2007.

Wednesday, 15 June 2011

Studio - Segments won't be stored in my TMs

Working with Project TMs gives you the possibility to control translated segments before they are stored in a main memory, you want to keep clean. It's also a good way to send a project to a translator who can't stay connected to a main server TM: relevant segments from the main TM will be copied in the project TM and sent as a file in the project package. Be aware that working with a project TMs will prevent the translator from writing in the main TM.Updating both main TM and project TM is not possible.

If you decide to work with project TMs, you can use the batch task "Populate Project Translation Memories" either through the task sequence "Prepare"

or through the context menu of the project after creating it.

Project TMs are stored in the corresponding target language subfolder in the "TM" subfolder of the project folder and are named after the project name and the main TM.
-> ".../projectname/TM/fr-FR/projectname_mainTMname.sdltm".

But this is not obligatory: you can also prepare the project without project TM, and choose to include a project TM while creating the packages to be sent to your translators. In this case, the project TMs won't be stored in the project folder.

...Bugs in packages...

We discover recently a bug in our packages.
In the 4th window of the package wizard, you have 3 options connected to "Project Translation Memory":

It's important to use "Create a new file-based project translation memory for every package" if you want your translators to work with a project TM. Studio will create itself new project memories and inserts them in the corresponding package.

"Include the existing project translation memory in every package" doesn't work properly if you created a project with 2 or more target languages. Some Project TMs won't be included in the corresponding packages or a project TM with another language pair will be included, so that your translator won't be able to work with a TM at all.

If you prefere not to work with a project TM, choose the third option...

Thursday, 19 May 2011

XML files - Proof the root tags when turning ini files into sdlfiletype

When creating new XML file types from existing ini files, for example those you used in TagEditor, you may have some difficulties to create a project in which your files will be recognized as translatable with the brand new file types. Create a new file type with Studio is not so complicated if you have an ini file, but there is one "bug" in the conversion you should be aware of: only one root element will be imported in this wizard...

I already mentionned in a former post that the file type button in the "create project" wizard doesn't work. So create your new file types in a template or in your own options (Tools -> Options...).

Here a short description how to create a new XML file type:

You can create a file type with New...

Here, you choose "XML".


Then you give at least a name to your file type.


 Here you enter your ini file with "Browse"

You get then something like this.

 Here you can change the tag properties.


In this window, the conversion from ini to sdlxliff doesn't work exactly. If you have only one root listed in the ini file, you won't get any problem, but if your ini file is to be used with many different xml files, that is, with many different roots, only one root will be imported in this wizard.

This means that not all your files you could convert in TagEditor will be convertible in Studio.
You have to adjust the settings manually by adding the missing root elements yourself:

To know how many roots are set in your ini file, you can check in Tag Editor or in the ini file itself.
Open it in Notepad, search for DOCTYPE and you will get something like this
 DOCTYPE=root1 root2 root3
 (The different roots ar separated by spaces)

In my example I have
DOCTYPE=martif mtf
-> 2 roots, "martif" and "mtf"

After this adjustment, you can save your new file type and try to create a new project with it.

See also this post if you have no ini but a dtd file to create a file type.