My Experience with Service Pack 2

happy happy sad sad

So, SP2 came out about a month ago. What do I think about it? Many good improvements but still plenty of room for improvement and, unfortunately, several issues are still unsolved.  I’m not going to list all the changes and improvements because you can find a more detailed list here. However, I will mention those that I have personally found most useful as well as some problems that were not fixed by this SP.

Good:

  • The improved Auto-substitution settings, particularly the possibility to control spacing between a number and its unit. I would still like to see a conversion function like in Trados 2007.
  • Possibility to analyze internal fuzzy match leverage and turn the cross-file repetition analysis on and off.
  • Improved MS Excel file conversion.
  • The real time preview seems to function better and the view actually gets updated automatically. There are still occasionally some functional problems with the linking between the preview and the editor; clicking a sentence in the Preview window should activate the corresponding segment in the Editor but I have met several segments where this does not work.
  • The new Quick Start Guides and the availability of a fully functional Trial version. This is particularly good news to those who are interested in trying out and getting started with Trados Studio.

Interesting:

  • The two new automated translation systems: Google Translate and Language Weaver. You can access these via the Translation Memory and Automated Translation settings. I don’t find this particularly useful for myself because these systems work quite poorly (or not at all) with Finnish. In addition, I would not be able to use them for most of my translation work because of confidentiality reasons, even if they worked better.
  • SDL OpenExchange for building applications for Studio. It will be very interesting to see what kinds of 3rd party apps will be developed and offered through this program.

Not so good:

  • Finnish spell checker is still not there. My colleague Dominique Pivard pointed out on the Finnish Trados users list that both, memoQ and Wordfast Pro, offer MS Word spell checker option in addition to the Hunspell spell checker (which, by the way, does not work for Finnish in either program). If Wordfast and memoQ have been able to do that, then it shouldn’t be technically too difficult for SDL to do it as well.
  • The fuzzy match markings in the translation results window are still as unclear as before, and the fuzzy match results themselves are quite often very strange, as I have mentioned earlier — unfortunately, no improvement here.
  • The problems with Translation Memory fields have not yet been corrected. I was really hoping that this would have been fixed by now, since it has been a known issue for a long time and is quite irritating.
  • Term recognition is still case sensitive.
  • “Non-translatable text” feature is still not working (for details, see this posting).
  • Multi-part variables are still not recognized (for details, see this posting).

In summary, a good set of small and large improvements but there are still many features that are not functioning as they should. Waiting for the SP3 then…

Advertisements

3 Responses to “My Experience with Service Pack 2”

  1. Richard Says:

    Hi. I appreciate your further info on SP2. I have another question on Trados Studio, if you don’t mind. I notice that it generates a new line after every period, not just the ones at the end of sentences like in TagEditor. So, for instance, if there is a series of numbers, such as 5.1, 5.2, etc. to indicate separate paragraphs, Studio will put 5. on one line & then start the next line with 1, 5. on the next line & then the one thereafter starts with 2, & so on. How does one correct this so that the lines start properly with 5.1, 5.2, etc.? This never happened with TagEditor. Thank you.

  2. Tuomas Says:

    Hi Richard. Sounds like the segmentation rules might need to be adjusted. Go to the Translation Memory Settings and select Language Resources on the left and then Segmentation Rules > Edit on the right. Select “Full stop rule” > Edit, and see that “Whitespace” (or Space) is selected in the “After break” pull-down menu on the right. That might be the reason. However, this should be the default setting so I’m not sure why it wouldn’t be already selected. You can find more info about the segmentation rules using the Help, though it doesn’t really explain everything.

    Let me know if that solves the problem.

  3. Richard Says:

    Thanks for your reply & you’re right: “Whitespace” is already selected, so that shouldn’t be the problem. It might have something to do with double-byte characters but I don’t know. When I saved the file to target & checked, the single-byte numbers seemed to be OK but there were some double-byte stragglers, for some reason, & they had the problem. I’ll just have to watch out more carefully for them, I guess.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: