Intelligent web search?

01I had the pleasure of meeting Michael Farrell, the developer of IntelliWebSearch, at the BP15 Conference in Zagreb this week and was able to have an interesting chat about the IntelliWebSearch application and the similarities to the new Web Lookup! application that was released onto the OpenExchange last week.  IntelliWebSearch allows you to do your lookups from any application and in any browser, it comes preconfigured with a bunch of search sites and you can add your own.  The Web Lookup! application for Studio 2014 allows you to do your lookups inside a window within Studio as you work, it comes preconfigured with a bunch of search sites and you can add your own.  Sounds similar doesn’t it?

Actually it’s very similar and after discussing with Michael a little I came to the conclusion the tools do a similar job.  The one big difference I can see is that the Web Lookup! plugin is language sensitive.  So if the search site is multilingual in the first place then the Studio app takes the languages from your bilingual file and automatically searches in the appropriate language… useful for a translator I think. Continue reading “Intelligent web search?”

Comments… chapter and verse!

The ability to work with comments in a managed localisation process is an important part of communication between translator, reviewer, project manager and the end client… and not necessarily in that order!  Comments are used to clarify misunderstandings in the source text, questioning completed translations you’ve been told to ignore that just don’t look right, suggesting improved terminology, explaining why you translated something in a particular way, clarifying why you changed a translation in review, providing additional context from the client, adding notes to the target file for an in country review, they could even be comments that are just there to be translated, or ignored… the list of reasons could be pretty long and so could the comments.  So it’s very important to be able to keep them linked to the context so it’s easy to deal with the referred text, and also to be able to get to the comments quickly when they might only relate to a couple of segments in three files that are part of a five hundred file project nested within a complex folder structure.

So this post is going to deal with two things… first of all the places where comments can be used in Studio out of the box and secondly a very neat OpenExchange plugin that I reckon many project managers, and translators, have wished for and didn’t know it was there already! Continue reading “Comments… chapter and verse!”

The Innovation Developer Experience…

001On two previous occasions I’ve been lucky enough to attend the SDL Innovate conference held at the San Francisco venue, and this year I get to go again.  But this year is particularly special!

Actually every year is great because someone like me, entrenched in the world of our Language Solutions, rarely gets a really good glimpse into what SDL is capable of providing as a leader in global customer experience.  I have a pretty good idea as I try to attend all the internal briefings we have, and I also get to work across many of our teams as I’m lucky enough to dabble a bit in the things we do for our communities and across social media.  But there really is no substitute for the value we create for our customers at an event like this. Continue reading “The Innovation Developer Experience…”

The JSON files…

01Update Sept 2016: You can find an excellent filetype plugin for JSON files on the SDL AppStore if you don’t want to tackle this yourself.

The JSON files… not really related to Jason Voorhees of course, but for some users who have received these file types for translation the problem of how to handle them and extract the appropriate text may well seem like an episode of Friday the 13th!  I’ve seen a few threads in the last couple of weeks sharing various methods for handling these files ranging from opening them in MSWord and applying a hidden style to the parts you don’t want, to asking vendors to create variations on javascript filetypes.  But I think Studio offers a much simpler mechanism for handling them out of the box.

So what are these file types and how can you handle them with Studio 2014, or even 2009/2011?  In this article I’m going to look at the regex filetype as this is very well suited to files like this, but before we get into that detail let’s take a look at what they are. Continue reading “The JSON files…”

Adjusting the view…

01It’s funny how questions seem to appear like London buses… you don’t get any and then they all come at once!  More often than not it’s very specific questions that behave this way too.  So you don’t see them for ages and then you get the same question in a number of places for a day or two and then it goes quiet again!  One of the topics that falls into this category is changing the view in the Editor.  By this I mean the colour of the text, the font types or the background you’re working on.  All these things can be changed in Studio to make it easier if you’re dealing with documents that don’t display well and you want to work in wysiwyg mode.

Since the release of Studio 2009 the things I’ll cover here have always been available through the options, but now that we have the ribbon in Studion 2014 it’s even easier.  To make this easier to see (hopefully!) I addressed where the options are in this article and then I recorded a short video so you can see in one go how these work in practice.  This is the text I’m working with, “theview“,  which is obviously a deliberately prepared file containing some things that can make it very difficult to read and work with when working in the default view and you can download it to have a play if you like. Continue reading “Adjusting the view…”

Converting Wordfast resources… out with the old!

01This article is all about out with the old and in with the new in more ways than one!  In the last week I have been asked three times about converting Wordfast translation memories and Wordfast glossaries into resources that could be used in Studio and MultiTerm.  Normally, for the TXT translation memories I get I would go the traditional route and use a copy of Wordfast to export as TMX.  Then it’s simple, but what if you don’t have Wordfast or don’t want to have to try and use it?  Wordfast glossaries are new territory for me as I’d never looked at these before.  But on a quick check it looked as though they are also TXT files so I decided to take a better look.

Before I get into the detail I’ll just add that I’m not very familiar with Wordfast so I’m basing my suggestions on the small number of files I have received, or created, and the process I used to convert them to formats more useful for a Studio user.  I’ll start with the glossaries as this is where I got the idea from,  I better explain my opening statement too… this is because after I did an initial conversion using the Glossary Converter from the SDL Openexchange I was asked to explain how this would work with MultiTerm Convert.  This of course made me think about the old versus the new… I wouldn’t compare Wordfast and Studio in this way at all 😉 Continue reading “Converting Wordfast resources… out with the old!”

Product Comparisons… apples and oranges?

01When we want to purchase software what’s the first thing we do?  I know what I do… I look around on the internet for websites where I can learn more about the tools I’m interested in and only purchase if I can try them myself, and I imagine you’re no different.  If I want to compare TEnTs (Translation Environment Tools) it’s a small and very competitive field and you don’t see the sort of widely published comparisons you might for Office products, or desktop publishing tools for example.  So one place to start might be reviews from real users… but can you trust them?  They are often written by fans of a particular product who like to rate the comparisons based on their own personal choice, and often the comments they make about other tools are based on not knowing other tools well enough.  Certainly when you read the comments from users of the tools that came off worse you can see it’s also quite an emotive area… although it’s good to see users so passionate about their translation tools.  Even articles that are written in a well meaning and honest way, such as the one that Emma Goldsmith co-authored with David Turner (comparison between Studio and Déjà Vu) last week, can raise the hackles of some users and if you take a look at the comments you’ll see what I mean!

Continue reading “Product Comparisons… apples and oranges?”

The ins and outs of AutoSuggest

001The AutoSuggest feature in Studio has been around since the launch of Studio 2009 and based on the questions I see from time to time I think it’s a feature that could use a little explanation on what it’s all about.  In simple terms it’s a mechanism for prompting you as you type with suggested target text that is based on the source text of the document you are translating.  So sometimes it might be a translation of some or all of the text in the source segment, and sometimes it might be providing an easy way to replicate the source text into the target.  This is done by you entering a character via the keyboard and then Studio suggests suitable text that can be applied with a single keystroke.  In terms of productivity this is a great feature and given how many other translation tools have copied this in one form or another I think it’s clear it really works too!
AutoSuggest comes from a number of different sources, some out of the box with every version of the product, and some requiring a specific license.  The ability to create resources for AutoSuggest is also controlled by license for some things, but not for all.  When you purchase Studio, any version at all, you have the ability to use the AutoSuggest resources out of the box from three places: Continue reading “The ins and outs of AutoSuggest”

2014 in review

001Happy New Year to everyone reading my blog.  It’s been fun writing it, and I hope it’s been just as enjoyable and useful for you all as well.
Before we hit 2015 the WordPress.com stats helper monkeys prepared a 2014 annual report for multifarious.
 
 
Here’s an excerpt:

The Louvre Museum has 8.5 million visitors per year. This blog was viewed about 110,000 times in 2014. If it were an exhibit at the Louvre Museum, it would take about 5 days for that many people to see it.

Click here to see the complete report and thanks again for reading it!  Maybe 2015 will be the year I finally get a view from Greenland!

Working with shared resources…

001One of the reasons SDL Trados Studio, and Trados before that, has been such a popular choice for translators and small teams is the ability to work with shared resources.  Many Translation Environments require the use of a server solution in order to share work and if you only do this occasionally, or if you work with a couple of colleagues, then whilst the server solutions can offer a lot of additional capabilities they are often over the top for simple sharing needs and may even require you signing up for things you may not be interested in.
Sharing resources at a simple level is pretty straightforward with Studio because they are mostly file based.  So you have a Translation Memory (*.sdltm), and a termbase (*.sdltb) for example, both of which can be accessed by several translators at the same time.  You may well have read that several times just to make sure this is what I actually said!  If this is possible then why do we sell server solutions at all, as we have SDL GroupShare, SDL WorldServer and SDL TMS?  The reason of course is that sharing a filebased resource like this has many limitations and it’s not a solution for serious Projects.  Limitations like these that are detailed in KB Article #5098 in the SDL Knowledgebase:
Continue reading “Working with shared resources…”