Showing posts with label revision of translations. Show all posts
Showing posts with label revision of translations. Show all posts

Monday, 4 April 2022

My 10 translation workflow stages

What does it take to create a fit-for-purpose commercial or technical translation? In my previous blog post I described how I revise my translations to make sure they are phrased clearly, read smoothly and don’t include any mistakes or translationese.

 

In today’s blog post I’m sharing an overview of my complete translation workflow to provide an insight into how I generally work. It usually comprises the following 10 stages:



1) Formatting the file for word processing if it’s not editable

 

2) Preparing a rough draft of the translation (aka target text) and researching the subject-matter and related terminology

 

3) Identifying issues in the original text (aka source text) and discussing them with the client before the translation is executed further, OR preparing a translator’s report identifying such issues (and delivering it along with the translation at the end)

 

4) Preparing a second translation draft by closely comparing the source text against the target text, implementing any necessary changes and improving on the initial rough draft

 

5) Checking individually that any numbers or reference numerals in the source text have been transferred correctly to the target text

 

6) Printing off the translation, editing and revising it as an independent piece of writing (away from the source text) using pen and paper, and considering the translation in its entirety

 

7) Transferring changes made in the previous stage to the translation on the screen

 

Next, I step away from the translation and revisit it the next day or, ideally, a few days later.

 

8) Checking the translation against the source text again carefully to ensure it is appropriate in every respect for the client’s specific purpose 

 

9) Running a spell check

 

10) Putting finishing touches to the translation and (if required) finalising the translator’s report

 

 

To create a professional, fit-for-purpose commercial or technical translation, a number of tasks involving great diligent care need to be completed. In this blog post I provide an insight into my 10 translation workflow stages.

 


 

Thursday, 17 February 2022

The translation workflow stage that should never be omitted

What measures can and should be implemented to ensure a translation doesn’t “read like a translation”? A professional translation bears the hallmark that it is a text that can stand on its own and that it is fit for its commercial purpose.

 

 

In the world of business, translationese tends to be seen in a negative light,
so it is crucial that any translationese is removed before a translation is put to use

(photo by
Scott Graham on Unsplash )


Essential aspects of translation revision

To make a translation fit for its purpose, a crucial stage in my translation workflow involves printing it off so I can revise it at a place away from my office. On my printout I scrutinise the translation to check it is correct in terms of grammar, punctuation and idiomatic usage. I also check whether I’ve written it in a style and with the naturalness required for the text in question.

An essential aspect of the tasks performed by a translator is to ensure that a translation doesn’t read like a translation (that’s what machine translation may be good for). So when revising a translation I also check its content independently by reading it and continually asking myself: do the words on the page make sense? Do sections in the translation need to be rewritten? Is there any remaining “translationese” that needs to be removed?

 

The negative effect of translationese

What is translationese? Translationese is characterised by strange, literally translated phrases, as a result of which a translated text has a special awkwardness to it. The awkwardness of a translation can be down to various reasons, often because the translation clings too tightly to the original text.

Translationese may render a translated text unusable. It creates a bad impression: it is usually embarrassing and can be reputation-damaging. In the world of business, translationese tends to be seen in a negative light, so it is crucial that any translationese is removed before a translation is put to use. For this, a (human!) translator’s input will be required.

 

 

A different work environment enables me to look at my text from a fresh perspective
and consequently make necessary changes

(photo by Engin Akyurt on Pixabay)

 


The power of pen and paper in high-tech work environments

In my experience, revising a translation using pen and paper on a printout is an effective way to morph it into a piece that reads smoothly and can stand on its own. After all, you do “see” so much more on paper than you would ever pick up on a screen! A properly revised translation will be correct in terms of grammar, punctuation, terminology and idiomatic usage, and it will be phrased in an appropriate style.

The revision of translations also ideally is performed in a different environment from your office or the room in which the draft was created. A different environment will enable you to look at your text from a fresh perspective and consequently make necessary changes.

 

I sometimes combine the activity of revising translations away from my office with exercise and a trip to an atmospheric café, for example: if time allows, I love getting on my bike to head over to the charming Coffee #1 on the outskirts of Bath on the picturesque Bristol-to-Bath cycle track to revise a few translations there.

 

A translation needs to be correct in terms of grammar, punctuation and idiomatic usage
and should be written in the style required for the text in question

(photo by Elisabeth Hippe-Heisler: Coffee #1, Riverside complex in Bath)

 

Proofreading your own writing: other tricks and techniques

Other tricks and techniques for proofreading your own work can be found in an article by Alison Quigley, which was republished on Belinda Pollard’s blog and includes many illuminating (and perhaps surprising) insights into proofreading your own writing. If you frequently proofread your own work, I recommend checking it out!
 

According to the article on Belinda Pollard’s blog the following proofreading techniques are, amongst others, recommended:
 

- reading your texts backwards


- using a blank sheet of paper or a ruler to cover up the lines below the ones you’re reading so you don’t skip ahead


- reading your work out aloud (or having your work read out aloud by an app) 


- reformatting the text by changing the font, ideally to a completely different one, which is perhaps even difficult to read



In the world of business, clumsy or overly literal translations create a bad impression and can be reputation-damaging. I therefore revise my translations using pen and paper, and in this blog post explain why in my opinion this workflow stage should never be omitted.

Thursday, 18 March 2021

Must-know Google search operators for translators (part 2)

Google search operators are powerful tools which translators can employ to create correct and idiomatic translations. They help narrow down the hits returned by Google, extracting specific information that a less refined search query would not.

The headache of online searches these days is that many of the words and phrases found online are unreliable, fishy or incorrect. How do translators go about finding correct and reliable words and phrases for use in their translations?


This blog post is the continuation of my previous blog post "Must-know Google search operators for translators (part 1)", which you can find here.

 

Focused internet searches are vital to the specialised work of translators
and can be powerfully aided by Google search operators

 
 

Reading a Google result
 

It is necessary to understand how a Google result is read.

When I enter, for example, the search words "Elisabeth Hippe-Heisler" into the Google search bar (known as "search query"), this is one of the results that will be displayed by Google:

 



The URL, which stands for Uniform Resource Locator, is the address of a given unique resource on the web.

The title is the title which the author of the webpage has added to the webpage.

The search words "Elisabeth Hippe-Heisler" will be displayed in bold in an extract from the webpage text.

 
Note that all examples which I’ve given below are based on translations from English to German (the main language combination I work with), but are, of course, applicable to any language combination.
 

The most helpful Google search operators for translators (part 2) 

 

intitle: 

The intitle: operator serves to search for words likely to appear in the title of a website. It is called “title” because in the underlying HTML code <title> tags are used:




Example:

Since machine learning and artificial intelligence are a frequent topic of my patent translations, I often need to equip myself with relevant English/German glossaries before embarking on my translation. It is possible to track down webpages with the German word “Glossar” or the English word “glossary” in the title.

 

The following search query will bring up 74 glossaries with either “Glossar” or “glossary” as well as “künstliche Intelligenz” (German for “artificial intelligence”) in the title.

intitle:Glossar|glossary intitle:"künstliche Intelligenz" 

 

For a more minimal use of words in my search query, I could alternatively shorten the search query as follows: 

allintitle:Glossar|glossary "künstliche Intelligenz"

 


Example: 

Say I’m thinking of using the term “Beacon-Frame” in my German translation, but am unsure whether it is a term that’s typically used in a German data communications context. Assuming further that I trust the reliability of terms on the itwissen.info site (or say I’ve been instructed to use this site for reference), I can then test for this term by typing the following query into Google:

"Beacon Frame" intitle:itwissen 

 

2 Google search hits will confirm to me that “Beacon-Frame” is used on itwissen.info. This convinces me it is appropriate to use the translation “Beacon-Frame” in my German translation.


The tilde symbol 

The tilde symbol ~ is the Google operator for finding synonyms.

 

Example:

To broaden my search for German deep learning-related glossaries, I can either use the OR operator | (the pipe symbol) and include various synonyms for “Glossar” (German for “glossary”) in my hunt for German glossaries:

"deep learning" intitle:glossar|begriffe|fachbegriffe|lexikon|terminologie 

 

Or so as to have to type less, I could simply use the tilde symbol:

"deep learning" ~intitle:glossar
 

Who (apart from translators and writers) uses Google to track down synonyms? Note: the tilde operator was deprecated several years ago, but I'm listing it here anyway, not least to demonstrate that Google will sometimes drop support for operators if usage is low!


related: 

The related: search operator is used to find sites similar to the one that is useful to me. 

 

Example: 

epo.org is the European Patent Office’s website, so related:epo.org will bring up other IP-related sites relevant to me as a patent translator as I can consequently extract useful terminology from them.

 


 


filetype:

The filetype: operator serves to limit searches to a specific file format of documents I want to look at online.

 
Example: 

Many reliable glossaries are contained in and available on the web as PDF files. If I’m required to collect glossaries for a mechatronics translation and, for instance, want to restrict my search to PDF files, I could use the following search query:


Mechatronik intitle:glossar|glossary filetype:pdf

 

Combinations of search operators (for example site: and intitle:) 

There are obviously lots of ways in which search operators can be combined for more efficient web searching! For example, one particularly useful way of tracking down terminology for a translation is combining the site: and intitle: search operators.


Example: 

Say it occurs to me that the expression “operatively connected” (or “operatively coupled”), which is typically used in patents, has already been discussed by translators on ProZ.com and I want to take a look at the discussion around this expression. 

English-to-German glossaries in the KudoZ database on ProZ.com are listed at http://www.proz.com/glossary-translations/english-to-german-glossaries, and they all have the words “English to German” in the browser title bar. For quick access to KudoZ results right from my Google search bar, I therefore usually use the following search command:

operatively intitle:"English to German" site:proz.com

 



Conclusion


Focused internet searches are vital to the specialised work of translators and can be powerfully aided by Google search operators. Google search operators are strings of characters that are added to a search engine query to help narrow down the hits returned by Google and produce more accurate translations.

 

This blog post is the continuation of my previous blog post "Must-know Google search operators for translators (part 1)", which you can find here.

Wednesday, 3 March 2021

Must-know Google search operators for translators (part 1)

Focused internet searches are vital to the work of translators, as just entering keywords into a search engine often isn’t enough. For more targeted, granular search results, it may instead be necessary to add certain parameters, known as search parameters, to a search query.

 

Google search operators are powerful tools
which translators can employ to create correct and idiomatic translations

 

Creating correct translations using search operators 

The headache of online searches these days is that many of the words and phrases found online are unreliable, fishy or incorrect – a situation exacerbated by the fact that the internet is becoming increasingly swamped with machine translations. How do translators go about finding correct and reliable words and phrases for use in their translations?

This is where Google search operators come in. Google search operators are powerful tools which translators can employ to create correct and idiomatic translations. They help narrow down the hits returned by Google, extracting specific information that a less refined search query would not.


What are Google search operators?

Search operators are strings of characters that are added to a search engine query to narrow the focus of the search. You can, for instance, limit a search to just examining all the text on a particular website by using the site: operator.


Reading a Google result

It is first of all necessary to understand how a Google result is read.

When I enter, for example, the search words "Elisabeth Hippe-Heisler" into the Google search bar (known as "search query"), this is one of the results that will be displayed by Google:

 



The URL, which stands for Uniform Resource Locator, is the address of a given unique resource on the web.

The title is the title which the author of the webpage has added to the webpage.

The search words "Elisabeth Hippe-Heisler" will be displayed in bold in an extract from the webpage text.

 

Note that all examples given below are based on translations from English to German (the main language combination I work with), but are, of course, applicable to any language combination. 


The most helpful Google search operators for translators (part 1)


site:

The site: operator can be used to extract words and phrases from a particular website.

 

Example: 

The site: operator comes in useful, for example, when I’m scouring the leifiphysik.de website for typical German terms or collocations in a physics context for use in my translations. (This website has been recommended to me as a reliable online source for physics by my brother-in-law, who teaches physics in Germany.)

For instance, to find collocations containing the term “Körper” (the German translation of the English term “body”, which in physics is used to describe an object with mass), I input the following search query in Google and will hence be able to browse a host of typical German collocations:

"der Körper" site:leifiphysik.de

 



 










Example: 

Another useful search method which I frequently apply is to use the site:de operator to display websites from Germany only. In other words, the Google search results will be limited to a particular top-level domain (TLD). For instance, I could use the following search query to look at websites with artificial intelligence-related content specifically from Germany:

site:de "künstliche Intelligenz"



Wildcards 

A wildcard is designated by an asterisk (*), which stands for a keyword not yet known at the time I enter my search query. 

 

If I’m unable to remember all the words in a technical term I need to use, I can use a wildcard on Google to find this out quickly. Searches with wildcards – as opposed to searches without them – will usually yield pages about exactly what I'm looking for straight away, thus speeding up my search.

 

Example: 

"Redundant * of Independent Disks"

 


 

I love wildcards and use them all the time – and not just for work! Since I’m not a native speaker of English, I don’t translate into English. I do write a lot in English, though, with much of my writing targeted at British readers. To make sure my English writing sounds right to British ears, I frequently use combinations of wildcards and the site:co.uk operator.


Example:

"pandemic is still * havoc" site:co.uk



Bilingual searches 

Bilingual searches are useful for finding bilingual internet pages that will likely contain both the term and its translation. To narrow down the search, a field-related term in the target language could be added. 


Example: 

I recently had to deal with the term “interrupt coalescing“ in a computing translation. Since I had not come across the term before, I was first of all keen to find a definition of it, ideally a German one to assist me with the appropriate phrasing in my German translation.

I input the following search string into Google:

"Interrupt Coalescing ist"


3 Google hits came up, one of which read: "Interrupt Coalescing ist das Zusammenfassen von mehreren IP-Paketen auf dem Netzwerk-Adapter, bevor ein Interrupt ausgelöst wird." I was satisfied with this definition, not least because I noticed it was part of an e-book, and consequently went on to use „Interrupt Coalescing“ in my translation.

Note: I generally deem text found in e-books or Google Books much more reliable than text found on webpages as the latter are frequently sloppily worded and not properly proofread. 

 

The minus operator – 

The minus operator is used to exclude certain keywords or particular websites from a search. 

 

Example: 

Say I’m thinking of using the translation “Sequenzdetektor” in a machine learning context and wish to check whether this is a common term in German. Say I also wish to to exclude Amazon and Ebay from my search because the machine translations on these sites are known to be unreliable and won’t therefore be of much use in my hunt for the correct term. For this, I use the minus operator:

"Sequenzdetektor" -amazon -ebay

 

Google provides 389 results for “Sequenzdetektor”, including a host of useful German computer engineering sites or book extracts (but not Amazon or Ebay).  


 


 

Alternatively, I could specifically exclude Amazon and Ebay websites from my search:

"Sequenzdetektor" -site:amazon.de -site:ebay.de

 

The pipe symbol |

The pipe symbol stands for OR and is used to include various alternatives of a word in a single search query to cover a number of possibilities. 

 

Example:

I could use the OR operator to find explanations of the meaning of “wear leveling” in an electronics context in German:

 "Wear Leveling ist|bedeutet|wird"

 


 

Example: 

The OR operator comes in useful, for example, in double-checking if “sequenzielle Abhängigkeit” is a typical German term in a deep learning context.

For broader search results, I additionally include various German declensions of the adjectives and nouns I’m using in my search query as well as alternative German spellings (note that I don’t always include so many alternatives):


"sequenzielle|sequentielle|sequenzieller|sequentieller|sequentiellen|sequenziellen Abhängigkeiten|Abhängigkeit" "Deep Learning"


This approach will bring up a few hits. The following book extract convinces me of the reliability of the term “sequenzielle Abhängigkeit”, as a result of which I go on to use it in my translation:

 


 




inurl:

The inurl: operator is employed to check for words likely to appear in the URL of a website.

 

Example: 

I recently had to translate the phrase “to act as a packet capturer (e.g. packet sniffer) during training mode” in a patent translation about machine learning. The term “packet sniffer” is used in German, too, but how to translate “packet capturer”? Translating literally was out of the question. 

Here, the inurl: operator came in useful in the following search engine query:

 "Packet Sniffer" inurl:glossar
 

It transpired from this search that “aufzeichnen”, “abfangen” or “ausspähen” are typical verbs in this context, so I settled on the following translation: “während des Trainingsmodus (z. B. als Packet Sniffer) Datenpakete aufzeichnen”.


Example: 

Recently, the term “feature extractor” (again in a machine learning context) came up in one of my texts for translation, and I wasn’t sure what the correct German equivalent was. I was keen first of all to track down a glossary. To this end I used the following search query:

"feature extractor|extraction" inurl:glossar


The following useful glossary came up: https://quizlet.com/de/459396454/glossar-mti-flash-cards. So I settled on the translation “Merkmalsextraktor”. 
 

Feature extraction
Beim maschinellen Lernen, bei der Mustererkennung und in der Bildverarbeitung beginnt die Merkmalsextraktion mit einem ersten Satz von Messdaten und bildet abgeleitete Werte (Merkmale), die informativ und nicht redundant sein sollen, was die nachfolgenden Lern- und Verallgemeinerungsschritte erleichtert und in einigen Fällen zu einer besseren menschlichen Interpretation führt.


Conclusion

Focused internet searches are vital to the specialised work of translators and can be powerfully aided by Google search operators. In this post I give an overview of Google search operators that are most helpful to translators.

 

This is part 1 of a 2-part article. You can find part 2 of this article here.






Saturday, 1 February 2020

Why translators don’t fear the machines

The takeover of translations by machines is impending (or so we've been told).Why then don’t human translators fear the much talked-about rise of the machines?

As I see it, it all boils down to one simple answer: translators don’t fear the machines because a translation is created in a series of stages.


Most translations require human input

Machine translation is sometimes helpful in the first stage of creating a translation, but it then cannot contribute to what happens in subsequent stages. And where machine translation is no longer helpful, a human translator’s input will be required. 


Why don't human translators fear the rise of the machines?
(Image source: Peggy and Marco Lachmann-Anke on Pixabay)

The translation stages where machine translation is not helpful include, for example:

- Researching terminology in the particular field of the text

- Identifying and pointing out issues in the source text to the client, using appropriate grammatical terminology to describe and explain those issues, suggesting improvements

- Discussing the approach to “untranslatable” terms with the client

- Finding workaround solutions to tricky terms and phrases

- Applying client style guidelines to the translation

- Creating coherence between the individual parts of the text

- Improving the first draft of a translation (also known as “rough translation”)

- Improving the translation further

- Checking that correct punctuation has been used

- Formatting the file

- Eradicating errors (including errors potentially introduced by machine translation!)

- Printing off the translation and checking it on paper

- Double-checking that correct numbers and/or reference numerals (in patents) have been used

- Rewriting the translation (where required) so that it reads like a text that is idiomatically phrased in the target language

- Ensuring that the underlying meaning of the original text has been accurately conveyed (as we know, language is full of ambiguities!)

- Checking that technical terms have been used consistently throughout the translation

- Editing, fine-tuning and polishing the translated text

- Putting a human touch to the translation


Anyone who believes that a translation can be produced by the simple push of a button is unaware that a translation is created in stages. Machine translation may be useful during the first of those stages, but creating a fit-for-purpose translation is a long, drawn-out and intricate process.

A good translation cannot be produced by the simple push of a button
(Image source: Gerd Altmann on Pixabay)



Afterthought: Nobody knows, of course, what's still going to happen on the AI front, and some of the tasks above will maybe be taken over by robots one day. Right now, we're still very far away from it. I also personally believe that we will never get to a stage where robots will be like humans.


(A German translation of this blog article is available here.) 

Monday, 6 August 2018

Translators and small things: 5 peculiar quirks

Translators have peculiar quirks and habits, especially when it comes to small things in language! While some of these are essential to the job, to outsiders they’re likely to come across as oddities. The following list of translators’ peculiar quirks is by no means exhaustive:

1. Translators can become agitated about a misplaced or omitted apostrophe or (yikes!) a spelling mistake in a book.

2. Translators don’t normally sleep too well following the identification of an error in one of their recently submitted translations.

3. If it turns out a product name is not correctly hyphenated on a label, a translator may no longer want to buy that product on her next supermarket shop.

4. It is not at all unusual for a translator to be engaged in a phone conversation with a client in regard to “that comma on page 27”.

5. Translators show great zeal in discussing even the smallest of words, and often invest lots of time in the hunt for that one word that is spot on.


Translators are extremely sensitive to details in language, and their detail-orientedness may seem odd or exaggerated to outsiders. It’s very often small things in language that they notice, have to be mindful of, and even get worked up about!


Translators often get worked up about small things in language

Saturday, 27 January 2018

Machine translation in human translation workflows

With the cognitive computing age approaching at mind-boggling speed (before humans and technology likely will merge from about 2040), there seems to be a certain urgency in the need to familiarise ourselves with Artificial Intelligence. For translators this involves thinking about how (and whether!) to integrate machine translation into their workflows.

Post-editing a translation is not the same as revising it!

On 24 January 2018 an event on the use of machine translation in professional contexts was held at Clifton Hill House in Bristol. It had been organised by the University of Bristol in partnership with Universidad Pablo de Olavide in Seville and the ITI Western Regional Group (WRG), attracting academics, professional translators, translation companies and technology providers.

My main takeaways from the event:

The job of post-editor is a relatively new profession. Post-editing nowadays is either offered as a service in its own right or just used as a tool that is incorporated into the translation process.

Post-editing has been defined in the ISO 18587 standard. Yet, although it’s been defined and hence should be clear-cut, in practice it’s more complicated since clients tend to have different requirements.


Machine translations often are over-edited, rather than under-edited. It is therefore important to note that post-editing a translation is not the same as revising it! They are two different skills.

Ideally, MT should be regarded as an additional tool, or translation memory, or source of reference, which for certain projects (!) can help improve efficiency and productivity.


There will inevitably need to be a move from word count-based pricing to time-based pricing for projects involving the post-editing of machine translations.

There has been a notable shift in the perception towards MT among translators because it’s becoming more capable of producing results that are usable. However, feelings of uneasiness, or strong dislike, towards MT continue to persist.


News headlines about advances in machine translation have led to inflated expectations by clients of what such tools can do. It’s worth bearing in mind we’re still very far from the point where machines can take over from us!

The upside of such news headlines, on the other hand, is they’ve drawn attention to professional translation and interpreting, an industry which had previously often been overlooked.