Things you do in SDL Studio that it probably wasn't really intended for

I've been using Trados from version 6.5 (parallel port dongle!) and now use SDL Studio 2019. Over the years I have found a few strange uses (the ones that get friends who use SDL Studio giving me a funny look when I mention my "hack" having a beer) although in the cold light of day they have often come back to me and said, that crazy as my suggestion sounded in the bar, it might actually work and be useful. Does anyone else have similar uses?

One such example is one I call "Monolingual SDL Studio in Excel". We get a lot of questionnaires to fill out in Excel where the answers are as narrative texts (think word-processing in Excel...) which I receive for editing / language check. Since the questionnaires are usually from the same sources (international organisations), their format is standardised. I have a little Excel Macro that recolours all their questions cells (ie. to then allow me to ignore those cells) and then only the output that I want to edit is shown in SDL Studio. I have a project definition set up, only for editting Excel files, and the empty TM I have is either in German (German (Liechtenstein)-German (Germany)) or English (in SDL Studio 2019 I use English(Europe) - English(UK)) and then set up the project. Where it also works well is when the same answer is given to multiple questions in ensuring consistency. At the end of it, I export the target file and use another Excel Macro to change the recoloured cells back. 

10 Replies Latest Replies: 23 Nov 2018 11:20 PM by Paul < 1   2  >

10 Replies

  • In reply to Evzen Polenka:

    Evzen Polenka
    I believe that's because - for some obscure reason - it's available only in (awfully expensive, therefore rarely used by common translators) Professional version.

    Yes, this is true.  But worth noting that the "update file" feature in Studio 2019 uses Perfect Match and this is available with the Freelance licence as well.  This may be the biggest usecase for Perfect Match anyway... mid-project updates.

  • In reply to Alison Field:

    Hi Ali and Paul,

    The PDF converter is something I have rapidly come to love in SDL Studio 2019 working in financial market supervision where I have to frequently translate administrative decisions (passed on as PDFs to me, due to their containing an electronic signature). Fortunately as the PDFs are originally Word documents, the formatting is not so bad, but I have also used it before now to align an existing translation of a law prior to using Perfect Match with deductions. The only problem that threw up in one instance was an "Unexpected Token Error"

    The OCR part of it has come into its own where I have non-OCRed scans of faxed reporting submissions from a couple of very small supervised entities - the OCR feature is a marked improvement of the previous having to retype the PDF files (1-2 pages of text).


  • In reply to Stepan Konev:

    The issue I mean is using SDL Studio where there is no translation per se, but to get round the problem of dealing with paragraphs of text in Excel that need reviewing, rather than translating. In Excel they are a nightmare to edit.
  • Another workflow I use, which again is using Studio as an authoring memory system, is one I call "Monolingual Track Changes in PowerPoint" which is useful as I get a lot of PowerPoint presentations to review, frequently written in English by non-native authors (second language authoring ("2LA") also being increasingly prevalent, who have presentations in working groups that they ask me to check. One of the weaknesses of PowerPoint is the fact that there is not the same track changes feature as in Word (track changes in PowerPoint from the 2013 uses the Review > Compare feature. SDL Studio's bilingual preview mode (Ctrl + P in Editor mode) is particularly useful as I often have to go through slides with colleagues and can then see what has been changed.

    In addition I also have a Monolingual Termbase that I use in conjunction with this workflow that I use in conjunction with a QA terminology check, as a way of trapping frequent errors and also AutoCorrect entries to correct numbers (e.g. where the English presentations continues to use German abbreviated forms for millions and billions). As I have a lot of regular customers who tend to be consistent in usages (ie. the same changes are often required between one presentation and the next where they write from scratch on each occasion). One colleague has asked me before now if I am aware of mistakes he regularly makes - and by using a job number in each project which includes the customer's in-house abbreviation (we all have three letter abbreviations eg. ABC or BAI etc.) coupled with a "user" field in the Termbase, it has helped some improve their authoring by being aware of what frequently gets changed.

    When the target language version presentation is generated, it can of course also be compared and reviewed in PowerPoint if required. The only downside is that sometimes the formatting needs checking in PowerPoint afterwards.

  • In reply to Michael Bailey:


    Here's another thing that Studio wasn't quite designed to do but can do very well...

    Comparing pre-existing translations

    All the best,

    Ali :)

< 1   2  >