Wednesday, 20 April 2016

8.6.1 Standalone numbers and tables

Note: This text is an extract, without pictures, from "My workflow in Studio". The above text is also available in Swedish, in "Att jobba i Studio". Both documents can be downloaded from the links in the right column.
In technical documents there are often a lot of numbers and codes in standalone Tus.
Picture 814. Standalone numbers.
Autopropagation of numbers can delay the work, as Studio always autopropagates numbers.  One way to avoid this is to filter and lock all numbers. In the tab Review, choose the built-in filter "Number only" in the box Display Filter.
Picture 815. Filtering on "Number only".
Picture 816. Display after filtering on "Number only".
I believe that it is better to use a Regex formula like ^[\d.+]+$, which also filters numbers with dots, like 1.27.390. The symbol ^ is written with Alt + 94. Enter the filter formula in the field beside the hopper in Display Filter:
Picture 817. Display after filtering with a regex formula.
Explanation of the formula
^ starts with
[\d. digits followed by a dot
+] repeated
+ previous pattern group repeated
$ only this pattern and nothing else may occur.
If you omit the $ you also get segments that begin with a numerical pattern and continue with the text.
Picture 818. Filtering with ^[\d.+]+$.
The formula ^[\d.+]+[\d,+]+$ also finds numbers with dot and comma.
Picture 819. Filtering with ^[\d.+]+[\d,+]+$.
If you need to localize, and change decimal or thousands delimiter, you can do it after the filtering, with Studios Search & Replace function, or manually, if only some of the punctuation marks have to be changed.
When you filtered out the numbers you should lock them. Click on the TU number in the column for TU-number on the first line. Shift-click on the TU number in the last line of the selection. Then press Ctrl + L.
Picture 820. Locked rows.

Translate to Fuzzy skips locked rows, and no Autopropagation takes place.

Tuesday, 19 April 2016

New version of My workflow

Hi! I have now refreshed the My workflow, and added som stuff about Studio 2015, and some other changes. Download the new English and Swedish versions below.
If you still see the old version, push F5 to refresh.

My workflow in Studio 2014/2015 version 1.3

Att jobba i SDL Trados Studio 2014/2015 version 1.3

Saturday, 12 March 2016

Upgrade to Studio 2015

I upgraded to Studio 2015 Professional today, and also bought SDL MultiTerm 2015 Extractor. I will comment on the new features in 2015, when I have learned to use the new version.

Saturday, 28 November 2015

New documents

Hi there!
I have now updated my Studio workflow manual and translated it into English. I have also refreshed my Customer info. See links in the column to the right, or visit my home page, where the documents are available under the tab Info.


Jag har nu gjort en ny version av Att jobba i SDL Trados Studio 2014. Dessutom har jag uppdaterat min Kundinfo. Båda dokumenten är även översatta till engelska. Se länkarna till höger, eller besök min hemsida, där dokumenten finns under fliken Info.

Friday, 16 October 2015

A productivity manual for Studio 2014

My workflow in Studio 2014
Att jobba i SDL Trados Studio 2014

Tuesday, 29 September 2015

Working with SDL Studio 2014 - video

I made a demonstration video for one of my customers on how I work with their material. The video shows how I use Autosuggest with a combination of entries from my termbases, AutoSuggest glossary and from Google Translate. After trying out various other suppliers of machine translation I reverted back to GT as my only source, and I also only use GT from AutoSuggest. I found that using pretranslated GT material and to get hits of complete sentences is not so good, it leads to too much editing and deleting of useless stuff. 

The GT Api costs some money per month but is well worth it, in terms of increased productivity.

The video:

Friday, 1 May 2015

Align in and outside Studio 2014

I have for many years been using Trados old align function, and it is not intuitive, simple and easy to use, but was actually quite efficient once I learned to master the features of it. There was a degree of intelligence in it that was useful in documents that did not align very nicely.
So I looked forward to the promised new version of align Studio 2014. I got into a pretty big job for aligning, and decided to test this feature thoroughly. Pretty soon I realized that the new align function is not similar to the old one, but was at least as difficult to learn. In addition, the interface is bad, as the texts are not placed side-by-side. The sentences are connected by curved lines instead of straight ones in the old align version, which makes it very hard to get a good overview and see which sentences fit together. There are two sets of different line numbers, which increases the confusion.

Figure 1. Studio 2014 align
It led me to realize that I can not work in this tool, so I started searching for other solutions. Since I have experience from ABBYY FineReader as an easy to use tool, I tested ABBYY Aligner. It proved to be a good alternative, and I worked quickly through my large align projects.

Figure 2. ABBYY Aligner
Problem solving example

Figure 3. Automatic merging in Studio align
Studios align discovers that Obs. is on a separate line and aligns correctly.

Figure 4. ABBY Aligner
ABBYY places Obs. on a separate line, but it is easy to fix. Highlight row 18 and 19, right-click and choose Merge fragments.

Figure 5. Manual merging in ABBYY Aligner
Studios align also introduces problems not present from the beginning.

Figure 6. Studio Align works too hard
Studio tries to insert a hyperlink leading to incorrect segmentation.

Figure 7. ABBYY does not complicate a simple thing unnecessarily
It is possible that ABBYY Align does not solve problems equally good, but it is more than compensated by the transparent interface. It is very easy to add, edit and delete rows with the functions split fragment, delete lines and merge fragments. There is also a search and replace function, which seems to be missing in Studios align.

In short, if you are used to edit Excel tables and Word tables so there is no need to read, understand and learn any extensive documentation. When the work is finished, the result may be exported to a TMX file and imported in a Studio TM. This approach is also better than Studios, where you must choose a TM first. It is quite common that an align fails completely, if the files are different formatted. Then you have to edit the files and try again, and it's fine if you do not need a lot of unnecessary steps to start a new align.