You can view earlier editions of the Tool Box Journal going all the way back the 2007
in the archives to which you have access if you support my work on the Journal.

Tool Box Logo

 A computer journal for translation professionals


Issue 19-8-303
(the three hundred third edition)  

Contents

1. The Long-Haul View (by Juliet Macan)

2. WIPO Pearl

3. Tips and Tricks: Hidden features in the Across Translator Edition (Guest column by Andreas Rodemann)

4. New Password for the Tool Box Archive

The Last Word on the Tool Box

Of translators and librarians

That was the title of a short article I wrote a little more than 10 years ago, in 2008. The point of the article was to highlight the remarkable speed with which librarians had accepted technology (unlike translators at that point). I contrasted the well-known "The Bookworm" painting by Carl Spitzweg of 1850 with this then-current description of how librarians approach technology in Wikipedia:

"The increasing role of technology in libraries has a significant impact on the changing roles of librarians. (...) Increasing technological advance has presented the possibility of automating some aspects of traditional libraries. In 2004 a group of researchers in Spain developed (...) a robot [that] is able to navigate the library, look for the specified book, and upon its discovery, carefully take it from the shelf and deliver it to the user. Because of the robot's extremely limited function, its introduction into libraries poses little risk to the employment of librarians, whose duties are [no longer] defined by menial tasks such as the retrieval of books." Wikipedia: "Librarian," 2008

I came to the following conclusion:

"There's a great contrast between Spitzweg's wonderful 'Bookworm' painting of 1850 and the 2008 Wikipedia description of the use of technology by librarians. While the 'Bookworm' provokes a poetic image, librarians today have been able to master and accept technology and thus still play an important role today. In sharp contrast, the language industry -- whose main character, the translator, has a historically similar poetic and romantic image -- has chosen a different path. That's why our industry is currently experiencing such heavy turbulences."A lot has changed since 2008. The majority of translators have embraced some translation-related technologies and have recognized that there are ways to distinguish themselves other than rehashing already-translated materials.

 

But what struck me on several recent occasions is that the job of the librarian has once again changed as well, and once again those changes have been embraced with readiness and grace.

My wife and I spent our annual vacation-mainstay at our family's lake cabin in rural northeastern Washington. The cabin is hermetically cut off from any electronic connection, and we leave only a couple of times to go into "town," which happens to be Colville, a struggling blue-collar community about half-an-hour drive from our cabin. Typically we also drop by the library to check our electronic correspondence. And the library in that little town is amazing. It's staffed by three or four librarians who run a large range of activities, some of which have to do with books and all of which have to do with people. The Colville library is a place for toddlers to be read to, for older kids to play video games, for the homeless to cool down from the heat or escape from the wildfire smoke in the air, for travelers to check in, for the elderly to meet, and, yes, for just anyone to borrow books or games or log on to the internet. It's as much of a cross-section of society as you can possibly get, and it's all guided by the librarians who spend so much of their time with social interactions and do it brilliantly. (In the last few years I've always made sure to personally thank them for their services and tell them how much I admire them for what they do.)

Now, I don't think the Colville library is all that different from other libraries. It's just what librarians do, and so often do well.

All this reminded me of a report on National Public Radio (the U.S. lifeline for, well, just about anyone who likes to listen to the radio and wants to stay informed) which discussed exactly that -- only that this report specifically mentioned social workers employed in libraries, which clearly is not in the budget for most libraries. Even the 2019 Wikipedia entry on "Librarians" reflects the social work reality:

"Traditionally, a librarian is associated with collections of books, as demonstrated by the etymology of the word 'librarian' (from the Latin liber, 'book'). The role of a librarian is continually evolving to meet social and technological needs. A modern librarian may deal with provision and maintenance of information in many formats, including: books; electronic resources; magazines; newspapers; audio and video recordings; maps; manuscripts; photographs and other graphic material; bibliographic databases; and web-based and digital resources. A librarian may also provide other information services, including: information literacy instruction; computer provision and training; coordination with community groups to host public programs; assistive technology for people with disabilities; and assistance locating community resources."

It seems unlikely that "social work" is part of the future service offerings for translators (interpreters might be a different story, but I will leave those speculations to more knowledgeable people), but as part of our services we will (continue to) have to market our skills of meaningfully interfacing with people (clients, colleagues, the general public), and we will have to continue to be open to changes.

In spite of what we like to say ("translation is the second-oldest profession in the world"), the translation profession as we know it today (excluding literary and religious translation) is very young -- about thirty or so years old -- and still in its formative stages. While I believe that we may have almost reached a plateau in its development, changes will still be necessary for many. And you know what the beauty of change is? Changing skills doesn't mean giving up one skill in exchange for another, but adding skills to an already impressive array.

That's what librarians continue to do, and that's what we will have to do as well. After all, St. Jerome is not the patron saint for both of those professions for no good reason ;-).  

ADVERTISEMENT

Free Translation Memory Training from SDL

Part 1 - TM Basics and Part 2: Getting the most from your TM

Take a look at the SDL Trados Studio resources available and build your TM understanding.

 

1. The Long-Haul View (by Juliet Macan)

My long-time colleague and friend Juliet Macan recently wrote me this letter. I found it remarkable enough to share with you because it describes the world of translation in a way that only few of us have actually seen. Here you go (and thank you, Juliet!):

 

Your book "Translation Matters" really triggered some amazing memories. Quite literally as someone who experienced the industrial revolution of translation, I wanted to share my experience as a translator and translation technology enthusiast living in Italy since 1973 when this marvellous adventure all began for me. Here is my viewpoint of how things occurred, at least in Southern Europe:

Although I never had any formal (academic) training in translation, I studied Sociology and Psychology at university. I found the great variety of texts I was asked to translate as a junior translator in an Italian agency an endless challenge and delight. Curiosity was the name of the game! Delving into the meaning of elaborate Italian texts which sang beautifully in the original but translated literally would have sounded plain silly to an English ear. Having to extract and mould the message to another culture without losing possible inferences. I loved it. My fascination with words harks back to my childhood, where I soon realised that some of the household words used by my Irish immigrant family were quite different from those used in my English school. This together with my Catholic Latin upbringing, passion for reading, and love of poetry and singing made me particularly sensitive to language and meaning.

But it was less fun having to retype one or more pages on my manual Olivetti typewriter when a lot of changes were required. So I was thrilled, in the early eighties, when I first got my hands on an electronic word processor (Rank Xerox), so I could type up and save a certain amount of text and modify and reprint it as necessary. This was just a short jump to the PC. Unfortunately, my first computer, another Rank Xerox, did not go so well: after losing a translation of 30 pages, I sent it back but, undeterred, opted for my first IBM clone. Here I went for Microsoft Word for DOS, and my computer adventures began!

Certainly, there were hitches in the beginning, but with a group of fellow translators, I learnt to master MS Word for DOS, to format the layout of a table in pre-WYSIWYG days. Lots of adventures in this new digital world. Also, instead of handwritten notes in my dictionaries, or pieces of paper with terminology suggestions, I was able to create "real" glossaries in my PC. But, just like all my reference materials, the original texts were still in paper form and the translations had to be delivered by post or in person. One nasty drawback that I experienced in my early computer (and mouse) days was "tennis elbow"--extremely painful--due to the incorrect position of my keyboard and mouse. Once I learnt the importance of ergonomics, problem resolved. Strangely enough, 15 years on when Dragon NaturallySpeaking was available, it was no use to me, as by that time I needed my daily exercise on the keyboard to keep arthritic fingers supple!

Then the BBS arrived in the early nineties, which meant that equipped with a modem, I could deliver my translations in electronic format without leaving the house! Although I did have to install a second telephone line so that I could explain to the agency, or client, how to receive my file. This was rapidly followed by internet: finally, I could send and receive documents in electronic format. This new era changed lots of things, and required increasing technological competence, so I joined a cooperative of translators and interpreters so that I could contribute to, and benefit from, the pooling of knowledge and investment with professional colleagues. The arrival of MS Word for Windows introduced new changes for the better along with challenges--the RTF that lies below a DOC still causes trouble today for those who refuse to move on to DOCX. Other challenges were DTP formats such as Adobe PageMaker and FrameMaker and Interleaf, etc., as technical writers began to provide their documents in these programmes. Either you installed these programmes and learnt how to use them, or you were out of a job! But it was often difficult to focus on the translation in hand when you were struggling with unfamiliar programmes as well as layout problems, as clearly many of the tech writers were focussed on the "appearance" of their documents and unaware of the "text flow" nightmares they were creating. Somehow I feel this was excusable in the nineties, but I really think it is unforgivable today, especially in MS Word files where tables can be excruciating.

Simultaneously, the arrival of terminology and translation memory software created a revolution. The potential benefits were very clear, but there were many new problems, not least choosing the "right" tool and configuring file filters, not to mention compatibility. IBM, Star, Trados and Atril all offered translation tools!! What a tumultuous time! I admit, I just jumped in the deep-end, tried a bit of everything, and gradually refined my choices over the years. Because of this passion and curiosity to find the best solution, at the end of the nineties I was appointed the translation technology manager in the cooperative, responsible for testing new systems and utilities, overseeing the fine-tuning, and training translators and reviewers in the use of these tools. This aspect had become even more urgent following the introduction of the new European Union laws in 1995 that obliged companies to provide all their documentation in the language of the European countries where they sold their products, thus no longer just English, French, and German, but Finnish, Danish, Dutch, etc. Another revolution that multiplied the demands for translation of technical documentation and required the training of new translators.

Then, in 2000, I had to find a replacement for IBM Translation Manager when IBM decided to suspend support. Although we used Trados, and TagEditor, for quite a lot of work, I was one of the few who first used and appreciated Workspace as it offered the possibility of creating multilingual projects and combining the various parts of Trados into a single tool. I was getting exasperated by the total lack of support offered by Trados. Then there was the question of the freelance translators who did not have a licence, or those who swore they worked with it but who used Wordfast, which meant serious segmentation and compatibility issues when they delivered their files. Exactly at this time, SDL put its in-house translation software on the market. SDLX was a great solution. It made it possible to create multilingual projects and provide translators with a free translation environment, with everything set up and connected to aid them in their work. The translation layout was much simpler and more pleasant than IBM Translation Manager, Word+Workbench/TagEditor, and Transit, and quite similar to Déjà Vu. Support was also excellent: if they couldn't fix a problem immediately, they gave you sympathy and a workaround. They appreciated feedback! Furthermore, it was easier to convince translators to try using CAT and appreciate the advantages; all they had to do was open the packages and translate.

In the meantime, not only did Microsoft update its basic Office tools to the XML format, another improvement, but it was also the advent of various so-called "QA tools," another source of great excitement and exploration. QA Distiller, Dog Error Spy, ApSIC XBench, etc. offered new possibilities for helping translators to avoid mistakes and improve the accuracy of their translations. Each of these had to be assessed, to establish how they could be used to best advantage, and instructions prepared for translators and reviewers.

Then there was the new enlargement of the European Union in 2004 and the requirements for translations in the "new" European languages, from Hungarian to Czech, from Polish to Maltese (for the latter it took Microsoft from May to September to include the four special characters unique to this language). Even more translators to introduce to translation memory, and new fonts to be designed for FrameMaker!

And then the breaking news on June 20, 2005: "SDL acquires Trados." I knew immediately what this meant, and that I would be obliged to look for another tool!

A lot of new translation memory tools had appeared, such as MultiCorpora, OmegaT, Across and Heartsome. But none of these felt quite right. Then I tested memoQ, and my first impression was that they had clearly learnt a lot from all the tools that preceded them and appeared to instinctively know what was efficient and comfortable for a translator. In addition, they also appreciated feedback and were prompt in implementing PM functions. Subsequently, I was interested to note the similarities with the new SDL Trados Studio, although I think that Studio was based heavily on the experience gained with SDLX, with bits of Trados plugged in. They certainly had, and still do, keep a close watch on what memoQ does. This has led to benefits for all over the last decade, as both tools have introduced features that they considered useful in the other tool. The only oversight, which I consider appalling, on the part of SDL is their failure to recognise the incredible possibilities offered by LiveDocs.

Now to get back to "Translation Matters": one of the first things that really touched me was your reference (in 2010) to the cloud (pages 38-40) and your doubts. Even though the cloud has been around for over a decade in certain tools and lies at the base of many of the newer tools that have appeared since 2010, I still feel uncertain about various aspects. First of all, although I personally have a fantastic fibre connection to the internet from home, I am acutely aware that not everyone is as lucky. Secondly, when you are "on-the-road," connections can be very unreliable/unpredictable, and so if your main tool, and all the material you are working on, is in the cloud, even in 2019, this is not a good thing. Indeed, I had a discussion about this with Michael Farrell in Forlì, as he was looking for the ideal translation environment tool with everything in the cloud. I tried to convince him that this was probably not a very good idea. And it is not even just a question of lock-in, as you mention later on, but the fact that even though you may be able to access, with permission, a cloud from a different tool to do a job, at the end of the translation, you are left with nothing. No trace for your own reference, no idea of how the translation has been used/modified. As a translator I find this more than a little alienating. Furthermore, it is not necessary. You can work in the cloud, but still have the possibility to work locally.

I was delighted with your mention of Terence Lewis, an amazing guy whom we have had the fortune to hear speak twice at the ASLIB/ASLING conference in London. He really fascinates me with his determination to find a solution for whatever problem crops up. On the other hand, I am still in two minds about crowdsourcing. While I fully agree that it is a marvellous opportunity in certain circumstances, for instance Wikipedia, I was very disturbed when memoQ introduced several years ago the online professional workflow by which a translator starts a translation and then, to save time, almost simultaneously, a reviewer can enter and start to check and modify the translation. Maybe I am too old for this but I cannot escape the feeling that when one is doing a translation, often you need to get into a text before you can be sure of the correct translation, then you need to go back and review it yourself, before passing it on to someone else. But if somebody else is pressing hard on your heels and changing your translations before you have had time to reflect -- I am not sure what the result will be. I also notice today an unfortunate drop in the sense of responsibility on the part of translators for their work, probably linked to project and payment structures. This is dangerous and very inefficient.

As regards your Trados history, I think we need to get some of the facts straight. The company Trados was founded as an LSP in 1984 and therefore could boast a history of 25 years in 2009, but the software Trados Workbench for DOS first appeared in 1992 followed by Trados for Windows in 1994. So at the most, we could say that in 2009 Trados Workbench was 17. This is something that SDL, which launched its own project-based translation tool SDLX in 2001, plays a lot on; indeed, Studio (a combination of the two) is only 10 years old this year!  

I very much appreciated your Relationships section, especially now when the pressure is on to automate everything from uploading content by customers, automatic counting and assignment, and automatic delivery and billing, although strangely prompt payment seems to be lagging behind! Clients rarely know much about the intricacies of languages, let alone translations or translation technology, and neither do their staff or content authors. To pretend that all this can be done by a magic tool, which just as soon as NMT has been perfected will do away with humans altogether, is absurd and yet.... I agree that qualified PMs are important to facilitate the whole process; they are NECESSARY to oil the wheels. Indeed, when I was still working in an LSP four years ago, I was delighted by the possibility offered by the memoQ project-communications function, a kind of Skype conversation for all those involved in a project that allows translators to discuss terminology or other aspects of the content with each other, and which can be monitored by the PM who can step in when necessary, or refer questions to the client. It was much appreciated by the translators and the PMs. But even at that time, the pressure was on to automate and eliminate human interaction.

The message needs to be that communication, in one let alone multiple languages, requires the comprehension and mediation of highly qualified humans. Machines can follow patterns, but they do not understand. Unfortunately, often the problem lies with the source content. Despite the valiant efforts on the part of many authoring and content advisors over the years, source content optimisation is lagging sadly behind. A typical example of this can be found in the widespread use of Euro-English as a pivot between the various EU languages. This, combined with the pressure to use NMT and PE, displays complete incomprehension of the issues. Yet another argument in favour of the dream of Interactive Translation mentioned by Félix do Carmo (see edition 299 of the Tool Box Journal) to support expert, specialist linguists in the identification and solution of communication problems that cannot be dealt with by AI or someone just fluent in the target language. We were lucky enough to have Félix as a speaker at the Translating and the Computer conference in London in 2016 and I found his words very inspiring.  

 

You can find Juliet on LinkedIn right here

 

ADVERTISEMENT

It's time to get back to the translation after the vacation and be the best! The money goes to smartest translators who use best translation tools.

Exclusive offer for Tool Box Journal readers from Advanced International Translations (AIT) at translation3000.com/aitpn/557-67.html 

10 copies of each product available at 55% off. The first 10 lucky translators will also get AIT premium support for six months!  

Focus on translation not administration. Get your copy now.

 

2. WIPO Pearl

Years ago I rather briefly mentioned the impressive terminology repository WIPO Pearl, but after meeting Geoff Westgate of WIPO recently, I was once again reminded that it might be one of the most underused tools in our arsenal. I imagine it's relatively widely used by translators specializing in patent translation (after all, "WIPO" stands for the World Intellectual Property Organization, and their 170-million-word-a-year translation efforts are mostly related to patents), but that doesn't mean that the use of this term gem (how is that for a rock band name?) is limited to those translators. In fact, as the following graphic shows, if you are working in any of these fields (which extend to hundreds of subfields if you click on them), you are well-served with this terminology resource (not a great name for a rock band!).

Wipo subjects

WIPO Pearl is available in 10 languages (for both its interface and the data it contains): Arabic, Chinese, English, French, German, Japanese, Korean, Portuguese, Russian, and Spanish. You can do a regular bilingual or multilingual term search that will give you access to a number of filters, sophisticated definitions of the terms in questions, reliability score, sources, links to Google Images search and patent database Patentscope, as well as to a "concept map." The concept map is particularly interesting and can be accessed separately as well.

According to WIPO's own definition, the concept map is a "diagram illustrating the relationships existing between concepts in a specific area of scientific or technical knowledge." Here is an example of a concept map:

concept map

The underlying software code for the maps was specifically developed by WIPO, and it's beautifully dynamic in that you can drag any of the terms to your heart's content and the whole diagram shifts along with your actions. Any of the terms is also clickable, giving you access to all the definitions and translations that are available. You can also simultaneously look for two terms to find out whether they are conceptually related.

I don't need to tell you that this is a phenomenal tool if you need to familiarize yourself with various concepts and their relationships in a field that you are not completely firm on.

I also asked Geoff whether it's possible to access the database with tools like IntelliWebSearch that would have to either make use of the URL containing the search terms or an API. Here is his answer:

"I discussed with the developers and we looked into the details. Currently, we have a fledgling API but it would need some modification to be fully suited for this kind of URL-based search. Since we have other developments underway in the next 2-3 months (including refining the API and making that available -- though probably initially not so widely), we are going to look at the question again in autumn, also factoring in any data security aspects that this kind of change could imply (not yet clear to me what, if any, these could be). So, I'll keep you updated as we move forward."

Sounds good to me.

 

ADVERTISEMENT

The new world economy is driven by content that's:

  • Flowing continuously instead of coming in separate orders.
  • Urgent -- expected to be done in hours, not days.
  • Large in overall volume, but tiny in individual pieces.

Make sure your business isn't left behind. Find out more here.

 

4. Tips and Tricks: Hidden features in the Across Translator Edition (Guest column by Andreas Rodemann)

This is the second in a series on tips and tricks with hidden features in common translation-related tools. Let me know if you're interested in writing a guest article for another tool.

 

In January 2019, Across Systems introduced the new version 7.0 of the Across Translator Edition (ATE) and named it after the hummingbird sub-species colibri to draw attention to the speed of the translation process. In July 2019, the first major service pack was released under the name Gilded Sapphire. The ATE comes in two versions: Premium for all translators who want to translate their own projects, and Basic for all translators who work with Across from time to time because their clients require them to do so. The Premium version has to be purchased, while the Basic version is free of charge.

Features Available in the Premium and Basic Versions

Spell-check

Across has a built-in spell-checker called the Sentry SpellChecker Engine. However, the Sentry SpellChecker is far from perfect, so a lot of words will be marked as misspelled though they are actually not. Did you know that you can use the MS Office spell-checker in Across? Simply go to the User Settings and look for the Spell-check option. Select the checkboxes for the MS Office spell-checker and the MS Office dictionary spell-checker (which is the user dictionary of MS Office). While there, you can also checkmark the crossTerm spell-checker to use your own terminology.

Across 1

Paragraph states

The ATE knows several paragraph states, with Untouched, Touched, Translated, and Keep Source being the most common ones for translation projects. These states can do more than merely indicate the state of the paragraph. When you click the Filter icon in crossView, you will see a lot of preset filter criteria to filter for paragraphs with any of the major states. But you may also filter for machine translated paragraphs or post-edited paragraphs to check any machine-translated paragraphs before you start translating the rest. You can also use the paragraph states to organize your working day. There is an icon in crossView called Progress information. This will show you the number of words in each of the Untouched, Touched, and Translated states so you can check whether you have done enough that day to meet the deadline.

The Keep Source state is a special case. Sometimes you come across paragraphs that do not need to be translated or whose translation has been put into another paragraph. When you choose the Keep Source state, a small window pops up letting you select whether you want to keep the source text or leave the paragraph empty. Paragraphs like this will not be stored in crossTank so you can keep your crossTank nice and clean.

Across 2

Searching and replacing across multiple documents

There are two ways to perform an S&R across multiple documents. I already mentioned one way, which is to right-click a project in the Projects module. The other one has a few minor restrictions but works, too. Go to the My Tasks module and select the first task. If there are other tasks you can open together with the selected task, you will see a "+" sign in front of them. Now select all files with that little "+" in front of them and click the Open button. All these documents will be opened together, enabling you to perform your S&R. If you don't see a "+", this means that you cannot open the respective task together with the others, e.g., because it's a different file type.

Across 3

Features in the Premium Version Only

The Project Settings Template

Across 4

The ATE includes several settings templates, including the Project Settings Template (PST). These settings templates let you define settings that you need over and over again, but that may be different from client to client or from task to task. The PSTs are located in the System Settings. Click the New button and specify a name for your PST. Then, on the General tab, you can define whether you want to use the Quality Assurance v6.3 or the new and very neat Quality Assurance v7.0. Additionally, you can enable or disable machine translation if you have an account by selecting / unselecting the option Allow secure external processing in local server environment. On the same tab, you can also define specific attributes, such as Relations or Subjects or even user-defined attributes, and make them mandatory if necessary. <

On the crossTank tab, you can define Storing Settings, i.e., at what stage Across will store translation units in crossTank and what to store along with them. Furthermore, you can define penalties in several categories. Under Pre-Translation Settings, you can define the minimum threshold until which Across will look for a match in crossTank and whether to automatically set pre-translated paragraphs to the final paragraph state. Last but not least, you can set filters here, for instance if you only want to see matches from a particular Relation or from a particular Subject. Of course, you can also combine different filter criteria to narrow the results even further.

The third tab is the crossTerm tab. There are only a few options here, one of which is the same kind of filter you have for crossTank. The other important option that might be useful is the number of words that you can combine into a single term. I, for instance, need this feature for Chinese, as Across counts each character as one word and I sometimes have terms of four or even more Chinese characters.

Document Settings Templates

The main purpose of the Document Settings Templates (DST) is not to check in anything to Across that you do not need, either because you cannot translate the respective elements in Across anyway, such as pictures, or your client does not want them to be translated. Sometimes clients will send you documents telling you to translate "only the text highlighted in yellow" or "only columns C and D on sheets 2 and 3", only certain slides of a PowerPoint presentation, or only certain tags of an XML file. In such situations, you need to determine the word count and then make sure you do not do more work than you are actually asked to do.

For exactly these purposes, the ATE comes with DSTs for all supported file types. Go to System Settings and select the file type for which you would like to set up a DST in the Document Settings section. You will see a number of predefined criteria for some DSTs, which are usually good as they are. One of my all-time favorites in the DST settings is the Check in hidden text option in the Word 2007-2016 DST. To access this setting, click the Advanced button in the lower right-hand corner. This feature alone will usually cover some 90 percent of the "this text only" requests that clients come up with. Make sure that this option is not selected. Then open the MS Word document that your client sent you and format all text that your client does not want to have translated as "Hidden." Then check in the file to Across. In crossDesk, you will now see only the text that your customer wants to have translated.

Across 5

And why bother with numbers and dates in Excel files? By formatting the respective cells, these can be easily converted to whatever number or date format you need. However, you don't have to touch them. In fact, you don't even need to see them. So, in the Excel 2000-2003 or Excel 2007-2016 entry, click the Add button, select the filter type (e.g., Column), set the Filter range or value to the columns that you don't need and the Mode to either Locked (=you'll see it in crossDesk, but cannot translate it), Hidden (it's in the Across database, but you don't see it in crossDesk), or Ignored (it's not even in the Across database). Specify a sheet name if you do not want to apply this to all sheets.

Across 6

Attributes

Attributes are the feathers that make the Across colibri fly. Across is based on a huge database that contains all your translations. And this database has to be organized in some way. There are a few standard attributes such as the Source Language attribute and the Target Language attribute (which is not quite correct because there is no real distinction between them, as Across always works in both directions), the Relations (client) attribute, the Projects attribute, the Subjects attribute, and the Creation Date attribute. But did you know that you can define your own attributes, called System attributes?

For example, you could define an attribute called End Client if you are working for an LSP who gives you projects from different clients and separate your crossTank entries of all end customers so that you don't accidentally use translation units of client A for client B. To enter a new System attribute in your ATE, go to System Settings and select the System Attributes entry in the General section. Then click Add below the top window and enter a new attribute name. After entering an attribute name, select the new attribute in the top window and click Add below the bottom window to enter new Attribute Values for you to select for your translation units. Now you can filter your crossTank in your Project Setting Template or in crossDesk to see only the correct matches or just fewer matches.

Across 7

 

About the author: Andreas Rodemann is an EN, DE, ZH <> EN, DE translator and Across trainer. His website is at ar-uebersetzungen.de and you can find him on Twitter right here.  

 

ADVERTISEMENT

Across Language Server v6: The Most Important New Features at a Glance:

  • Across Dashboard:Relevant project information at a glance.
  • crossWeb Review Mode: Easy involvement of international subsidiaries in the review process.
  • Across Data Cube: Easy collection of indicators.
  • Project Management Cockpit: Optimized work process for project managers.

Find out more about Across version 6 at http://www.across.net/en/support/whats-new/

 

4. New Password for the Tool Box Archive

As a subscriber to the Premium version of this journal you have access to an archive of Premium journals going back to 2007.

You can access the archive right here. As a Premium subscriber you can have access to the password.

 

The Last Word on the Tool Box Journal

If you would like to promote this journal by placing a link on your website, I will in turn mention your website in a future edition of the Tool Box Journal. Just paste the code you find here into the HTML code of your webpage, and the little icon that is displayed on that page with a link to my website will be displayed.

If you are subscribed to this journal with more than one email address, it would be great if you could unsubscribe redundant addresses through the links Constant Contact offers below.

Should you be interested in reprinting one of the articles in this journal for promotional purposes, please contact me for information about pricing.

© 2019 International Writers' Group  

 


Home || Subscribe to the Tool Box Journal