The video files are in the WebM format and it should be possible to view them in any recent browser, including on mobile devices.
The files can also be downloaded for offline viewing with supported video players, for instance the popular VLC media player.
It should be noted that – for some reason – SDL decided to produce the videos in standard definition (480 x 852 pixels, also known as 480p). Hopefully, they will eventually make higher definition (720p, 1080p) versions available on their YouTube channel.
Terminology recognition in OmegaT is handled via tokenizers. Starting with version 3.0.0, tokenizers are included in the standard OmegaT distribution, whereas one had to download them separately in previous versions. They are also automatically selected during the project creation process, whereas one had to launch them via the command line in previous versions. Tokenizers are especially important for terminology recognition in heavily inflected languages. This video shows how the tokenizer works with Finnish as the source language.
Starting with OmegaT version 3.0.1, recognized terminology can be inserted in the target segment via a new auto-completer feature, which works entirely in the editor pane and with the keyboard (the shortcut is Ctrl+space in Windows, and Esc in OS X, so as to stay consistent with the system-wide completion engine). In previous versions, one had to right-click with the mouse in the glossary pane. This video shows how terminology can be inserted in the target segment, using a sample Finnish-English project.
When SDL first announced its OpenExchange platform in March 2010, it was touted as an innovation that would “revolutionize the translation industry”. Three years later, in March 2013, SDL states in a press release that “over 500 developers have signed up” and that “app downloads double year on year”.
This video shows that the OpenExchange platform has had a rather limited impact so far and mostly provides a way for SDL to add missing features that are built-in in competing tools.
Translation tools use different mechanisms to store data in their translation memories, resulting in TM’s that varies greatly in size and structure. This video shows how a sample Finnish-English TMX with about 70,000 translation units and 48 MB results in a 31 MB TM in Trados Translator’s Workbench 8.3, in a 83-139 MB TM in SDL Trados Studio 2011 and in a 303 MB TM in memoQ translator pro. The Trados Workbench TM consists of 5 files, the Studio 2011 of a single file and the memoQ TM of 20 files.
This constitutes the introduction to a video to be released later on about concordance search in Trados Workbench, SDL Trados Studio and memoQ, focusing on single Finnish words.
The default font in the TXML editor of Wordfast Professional is Times New Roman 14. Many translators will find it inadequate (too big and not very legible). This video shows how to change the font (for both the source and the target cells of the editor) to something more adequate, eg. Tahoma 10.
OCR software like ABBYY FineReader or Nuance OmniPage are convenient for converting PDF files into Word documents. Although the conversion can be launched automatically, it may be beneficial to manually define certain areas in PDF files that have a complex layout. This video shows how to manually define a table in FineReader 10. Although the process is time-consuming compared to an automatic conversion, this is usually time well-spent as it will avoid many problems in Word and/or in CAT tools later on.
As an alternative to manually drawing lines for rows and columns, it’s also possible to use a FineReader feature called Analyze Table Structure. FineReader then tries to “guess” where the table’s rows and columns are located.
In some configurations with Wordfast Classic installed, Microsoft Word may crash either when launching a translation session, or when exiting. This can be caused by an older, buggy Bluetooth driver from Broadcom/Widcomm. Such configurations are often found on Bluetooth-enabled laptops that ship with Microsoft Office pre-installed. The problem occurs with different versions of Windows (eg, XP, Vista), different versions of Microsoft Office (eg. 2007, 2010) and different brands of laptops (eg. Lenovo, Dell, Hewlett-Packard etc.). This video shows where to look for the Send to Bluetooth menu option or icon in Microsoft Word and how to identify the Bluetooth version in Control Panel. The problem can be solved by uninstalling Bluetooth in Control Panel and rebooting. If newer, bugless drivers are available, they can be used to replace the buggy ones.