Friday, April 20, 2018

How to preview a Bitly address without clicking on it

Sometimes we receive Bitly shortened addresses in e-mails, or sometimes we see them in tweets or blog posts.

The problem is, how to be sure that clicking on them won't redirect us to a malicious address?

A solution, of course, is to just never click on such shortened addresses... but that might mean missing on some interesting sites or links. fortunately, for Bitly there is a way of checking to see what the real address behind the shortened one is, and also what reputation that address has:

Just copy the Bitly address to your browser's address bar, add a "+" sign to it, and hit Enter--you'll be sent to a preview page for the link, where you'll be able to see the real address, and any warning about the reputation of the address, like the following:

Monday, April 16, 2018

SDL invents new language

Not content with providing some of the best-known software tools for translators, SDL, a language technology company, is apparently hard at work inventing previously unknown languages.

The proof: recently translators have been receiving messages to offer them free training. and apparently that training is available in multiple languages.

One of them is "Mexican":

Mexican, a brand new language brought to you by SDL

When asked about the new language, SDL representatives said they could not answer right now about Mexican, as they were busy at work developing other new languages, including Swiss and Belgian.

They confirmed, however, that work on the Yugoslavian language had been definitely put on hold, as news that the country of Yugoslavia no longer existed had finally reached SDL's headquarters.

Thursday, March 01, 2018

Re-Posting from the Xbench Forum

I'm re-posting this directly as it appeared on the Xbench forum, as it may be of interest for all those who use Studio and the Xbench Studio plug-in:
With SDL Trados Studio 2017 Cumulative Update 9 (CU9) the Xbench Edit Segment (Ctrl+E) feature may stop working (it does not open the Studio document).
To be able to use the Edit Segment functionality after you updated your Trados Studio 2017 to CU9, just download and install the latest Xbench plugin for Studio (build 13)

Friday, February 23, 2018

What tools do technical writers use and prefer?

As translators we have to deal with the work of technical writers, but apart from some obvious programs (like MS Word), we often don'know the tools that technical writers use in their work. For a look at what tools technical writers prefer, see Technical Writing Tools: The Ultimate Choice of 83 Experts.

Tuesday, February 20, 2018

Infographic: Software Tools for Translation

I'm currently developing a course on CAT tools for the University College of Denver University.
I find mind mapping useful to generate and organize my ideas, so I created a mind map of the kind of software tools used by translators - CAT tools, of course, but also other types of tools, from those that help us manage our projects, to those we use for more specific tasks.

I asked Jost Zetzsche to take a look at my mind map, to see if he had any suggestions about types of programs I might have forgotten or things that should be changed.

Jost gave me some suggestions, and asked for a copy of the infographic for his Tool Box Journal.

Here is a copy of the infographic:
Software Tools for Translation
Software Tools for Translation

You can click here for a larger copy of the file, and here for a downloadable pdf.

I'd appreciate any suggestion or idea for future improvements.

Monday, October 23, 2017

Bad programming decisions in CAT tools

Everyone knows what software bugs are: flaws in a program that make the software fail or behave in unwanted and unexpected ways. Bugs are unavoidable in something as complex as software. The most we can reasonably ask of programmers is that they try to lessen the frequency and severity of bugs by using sound programming practices, and that they correct bugs quickly, once found.

Bugs are unintentional, whereas virus, Trojans and other malware are created with malicious purpose.

But, between unintentional bugs and willful malware, there is an entire class of problems caused by intentional programming decisions: when software features work as designed, but the design itself is ill-thought-out.

I'll give two examples from SDL Trados Studio and memoQ.

In Studio, an example of flawed design is the deliberate disabling of "smart quotes" when change tracking is active. According to SDL, "This currently is by design so that no uncontrolled/automatic changes should happen when typing in review mode." However, they didn't think through the real-world consequences of their decision: now, a translator may use smart quotes during translation, but since they are disabled during review, any apostrophe or quote entered during review will be straight. After review, the text of the translation will contain a mess of straight and curly quotes and apostrophes.

SDL Studio: The translator used smart quotes, but the apostrophe used during review is a straight single quote.

Furthermore, apostrophes and quotes are tiny characters: it is entirely possible no one will notice the problem for a while. The first person to notice might very well be the customer... perhaps when he receives the final printed copy, after it is too late to correct the error.

Disabling smart quotes when change tracking is active is harmful, and the problem is made worse because it is not well documented.

For me, I have a good workaround: a short program I wrote in AutoHotkey that allows me to use two different types of smart quotes (and also straight quotes) with no tweaking of Studio's settings, no matter whether change tracking is active.

Maybe, under certain circumstances, it would be better to disable smart quotes during review, but this is a decision that should be left to the translator, not imposed by SDL.

Let's now pass to Studio's main competitor, memoQ.

Here, the flawed feature is a change introduced with version 8 of memoQ: a new behavior, touted as an ergonomic improvement, of the Shift+F3 "change case" function.

Before version 8, Shift+F3 behaved in memoQ much the same as in Word, Studio, or many other programs--it toggled through the various permutations of change case: all lowercase, ALL UPPERCASE, and Mixed Case. Now Shift+F3 opens a drop-down menu, where the user can select the case.

memoQ: An unecessary drop.down menu for a simple function.

The result is the same, but the new "feature" hinders smooth typing by shoehorning in the workflow a change no user had sought. The new behavior slows a translator used to hit Shift+F3 a couple of times, until the desired case is achieved, then press the right arrow and continue typing. Changing case now often requires at least an extra keystroke; worse, it introduces an unnecessary change in a behavior that most users had imprinted in their muscle memory. And since Shft+F3 continues working as before in other programs, the irritation caused by the change will not fade away as you form new habits.

Unlike with the Studio example, there is no workaround: the only thing you can do is return to memoQ 2015, abandoning any useful feature added in version 8.

I imagine that if Kilgray introduced this new feature, someone must have either asked for it or thought it was a brillant idea. Instead, just like SDL's disabling smart quotes in change tracking mode, it is a bad programming decision.

Special free software offer

As I mentioned before I use a short AutoHotkey program to enter smart quotes and apostrophes in Studio. The program lets me enter "smart" single and double quotes, curly apostrophes, "French"double quotes, and also, when I need them, "straight" double and single quotes.

This works for me and would work for other Italian translators as well. If you need a copy of this utility, let me know, and I'll be happy to send it to you "as is".

I can customize (for a small fee) this utility to use different sets of single and double quotes. If you are interested, please write me (you can use the contact form in this blog).

Friday, October 06, 2017

New edition of Mats Linder's Trados Studio Manual now available

Mats Linder has just released a second edition of his immensely useful Trados Studio Manual, now updated to cover Studio 2017 SP1.

Of particular interest are the extensive changes and additions to the Machine Translation section.

The new edition of the manual is free for those who purchased the first edition of the Studio 2017 manual, and available at a 50% discount for those who purchased earlier editions of the manual (those for Studio 2015, 2014, etc.)

You can get the manual from the Trados Studio Manual webpage.

Thursday, October 05, 2017

Belt and Suspenders

Some of us may have a tendency to panic, when faced with some unexpected computer error (and such incidents generally occur when little help is available, or very close to deadlines, or both), but there are steps we can take to defend ourselves from the worst effects of such mishaps.

On Sunday, my partner's computer froze: suddenly neither keyboard nor mouse responded. We tried disconnecting and reconnecting keyboard and mouse, but without result. The last thing left to try was a hard reboot. We did that, and, after restarting in safe mode and then again in normal mode, the computer seemed to be working right: all programs responded as expected.

Until, that is, my partner tried to launch Studio 2017 to continue a project she was working on. At that point the Studio splash screen briefly appeared, only to be followed by an ominous error message: "Not found".

We clicked on the Knowledge Base Community link, but to little avail: no useful help there for this particular error message, so we opened a ticket with SDL's support. Of course, since it was Sunday, the earliest we could expect to hear from support was the following day... and my partner's deadline was rapidly approaching, so we needed to find another way to continue work on her project.

We had two options: either copy the project's files and memories to her backup computer (a laptop), where we still had a copy of an earlier version of Studio, or work on the project with a different translation tool.

We chose the latter option. Getting the sdxliff file to continue work was a simple question of copying it from the SDL 2017 "Projects" folder to a different working folder, but since we couldn't launch Studio, we had to use a different tool to export the most up to date copy of the translation memory: we used Xbench to load the TM and then export it in TMX format. It was then a simple matter of creating a new project in memoQ, add to it the partially translated sdxliff file, create a new memory, and import into it the TMX file we had created in Xbench.

My partner was then able to continue her translation.

The next day, Monday, we received instructions from SDL support. We were told first to try re-installing the program; when that didn't solve the problem, we tried renaming the "projects" XML file, and then various other SDL files and folders. Nothing seemed to work, and the SDL support technician was stumped. She said she'd need to escalate the issue to a more experienced engineer, but since the second-level engineers work out of the UK office, that would have to wait until the following day.

On Tuesday, we were again on a support call, this time with the second-level engineers. They suggested various other remedies, finally succeeding in restoring Studio 2017 to life -- the culprit turned out to be an obscure Windows file (BTW: kudos to SDL's tech support -- it's well worth the money we pay for it, and they are generally patient, thorough, and professional).

In the meantime, my partner had been able to complete the translation of the project in memoQ, and she then proceeded to finalize it in the newly-repaired Studio. So, a happy ending to our short tale of technical issues.

But it got me thinking that such happy endings don't just happen: they require preparation and planning:

  • If we had relied on a single computer, and a single CAT tool, my partner would have been unable to continue working until SDL support had solved the problem;
  • If we had not installed Xbench, we would have been unable to export the data from Studio's memory;
  • If we had not paid for SDL support, our only recourse would probably have been to take the computer to a repair shop, or perhaps ask for advice in the various online forums available, and hope for the best;
  • In this case, there was no damage to the files or to the computer's hard drive, but if such damage had occurred, we would have been prepared also: we regularly back up our files both to external hard drives linked to our home network, and to online storage.

Technical problems happen, but if you plan for them, you can minimize the damage they cause.

Thursday, September 14, 2017

The Microsoft Language Portal has a new look

The Microsoft Language Portal, an indispensable resource for all translators who work with Windows software localization, has just received a new look, which brings it better in line with recent changes to other Microsoft programs, from Office to Edge and Windows itself.

The new look of the Microsoft Language Portal

Personally, I find the new look, more modern--and perhaps more attractive--but a bit less legible.

Compare the old look below:

Th old look of the Microsoft Language Portal

The addition of more color to the interface helped separate the search form from the results area. The old look also displayed more terms per page:

The old version of the Microsoft Language Portal displayed more terms per page
I haven't worked long enough with the new interface to see if there are other changes other than the obvious cosmetic ones.

Monday, September 11, 2017

GT4T - A tool for translators, instead of a tool to replace translators

Guest post by Dallas Cao, developer of GT4T

Many translators believe that machine translation (MT) is a horror story, and that using machine translation (MT) in our work only results in bad quality. Indeed, after I started advertising GT4T (Google Translate for Translators) on Facebook, the reactions I got from many translators were negative.

They are right to think that the overall quality of machine translation is bad, and that any translator who mindlessly uses machine translation puts his or her career at risk; but the quality of machine translation is improving: Google’s neural translation engine, for example, has surprised many, to the point that some agencies have started using it to replace human translators, relying afterwards on translators as post-editors--a situation that creates even greater hostility against MT among translators, who are rightfully afraid that post-editing means for them toiling at mind-numbing grunt work.

Most of us use on-line reference tools in our work; when an online reference tool gets better, it helps us more. In my opinion, MT is the most advanced technology in translation, and, therefore, it should benefit professional translators first. If we consider MT as a reference tool rather than a threat, shouldn’t we be glad when our tool gets better?

I never liked the idea of letting MT translate and translators confined to an unrewarding task of post-editing; however, we can use MT to “translate” a word, a term, a phrase, or a part of a sentence that we judge it will translate well. Sometimes MT returns nonsense, true, but most of time, when used carefully it provides a surprisingly useful translation.

I developed GT4T because I wanted a tool that could help translators (and not translation companies) make the most of Google Translate, without becoming ourselves post-editors. Copying and pasting between Google Translate and your work is not a good solution, as it takes too much time. Some TM tools already include MT, but they all submit the whole sentence to MT: you cannot choose to have MT translate only part of a sentence.

GT4T is a tool that lets you submit any portion of a sentence of your choice to MT with ease. It’s very simple: you select some text anywhere (including from inside a CAT tool), press a keyboard shortcut, and the selection is replaced by translation from MT. Simple as it is, I believe it is the correct way of using MT. As we use keyboards most of time, GT4T painlessly incorporates MT into our workflow.

A usual problem with MT is inconsistency--the MT engine translates the same term differently in different sentences. GT4T has a simple glossary feature to solve this issue. You press a keyboard shortcut to add a term to GT4T’s glossary, and that term will be pre-translated before submission to MT; thus the results suggested by MT will be consistent.

GT4T - Glossary Setup

GT4T also offers the option to use both Google Translate and Microsoft Translator at the same time. The results from both engines appear in a popup, and you can then press 1 or 2 to paste the corresponding translation.

GT4T - Alternative Translations

I expect there are still many years ahead before MT can effectively replace us. Before that happens, MT can be a great aid--a tool that can increase both the speed and the quality of our translations, if used properly. A tool for translators, instead of a tool to replace translators.


You can find GT4T at: