Aug 29, 2011
Loriot's contributions to learning German as a second language
Gabriele Zöttl recently posted a farewell to the great German comedian Bernhard Victor Christoph Carl von Bülow, known as Loriot to most of the world. She rightly described him as an inexhaustible source of inspiration for writers. And for many others I would say. What no one has mentioned, surprisingly, is Loriot's valuable, original contributions to the learning of the German language by foreigners. Here is an example of his inspiring facilitation of international communication:
Aug 28, 2011
Using OCR to support translation processes
I recently noticed an element on the "wall" on my business Facebook page that I hadn't paid attention to before: questions. Since I've resumed research for a tutorial project I shelved several years ago when great uncertainty in the world of translation tools made my plans impractical, I thought I might try this feature and see what sort of feedback results. The question I posed was
Some of the points raised so far involve the eternal topic of OCR for translation business. When my client Sansalone Technische Übersetzungen in Cologne first introduced me to the effective use of OCR for translation purposes many years ago, it was relatively rare in the world of commercial translation and too often incompetently performed, but I had been using that technology in one way or another for a decade already. But in many cases, "standard" procedures for optical character recognition are simply not well suited for our purposes, so I had a lot to learn.
Now some 9 years later, many of the LSPs and colleagues I know use OCR in some way, but unfortunately few do so efficiently or even usefully. Though sometimes there are TIFFs or JPEGs to be converted, most often these days the documents to be converted are obtained as some form of PDF. And there is enormous confusion and misrepresentation among translators as to what the various PDF formats are and how to deal with them.
I distinguish between two types of use for optical character recognition in my work: (1) quotation or count verification and (2) translation preparation. The former allows for considerable sloppiness, the latter for very little.
One of my LSP clients whom I introduced to OCR technology years ago uses it for one thing only: estimating text counts for quotation. Depending on the source, this may be very accurate or only a rough count (if there are serious contrast problems that can't be compensated, for example). I do this not only with PDFs and bitmap files such as JPEG or TIFF, but also with large, complex documents in other formats. For example, f someone sends me a 200 page document in an MS Word format and I need to prepare a cost estimate for services quickly, I will often print it to PDF, then run the PDF through an OCR engine and save the results as plain text for counting. One cannot always rely on the counts from Microsoft Word itself or various translation tools for text counting. Embedded objects, even editable ones, are generally not included in the counts. I have seen RTF documents where have the tables are ordinary RTF tables (which are counted) and others which look the same are spreadsheet objects (not counted unless you are a Star Transit user AFAIK). And PowerPoint files can have embedded Excel or Visio objects or other uncountable elements. Printing to PDF and doing an OCR subsequently avoids this problem and enables one to ensure that nothing big was missed when counting by other means. This procedure also serves as an "early warning" if there is text to translate that is not extracted by the translation tools. It really sucks to "finish" a long job only to discover that several thousand words in tables and diagrams remain untranslated.
Using OCR to prepare translations is often straightforward, but there are a number of traps that people commonly fall into. Do not, under any circumstances, be seduced by the automatic conversion settings of any commercial OCR program nor by options to save with the "original formatting". This is nearly always a disaster when working with translation tools. Problems may include bizarre text changes, disappearing chunks of text due to text box sizing problems, a plague of tags and more. About six years ago I wrote some guidelines on the ways to save and work with OCR text; these are a bit dated, but generally valid. I would also suggest getting and learning to use Dave Turner's Code Zapper macros for MS Word; these can not only clean a lot of garbage out of troublesome OCR texts but also from MS Word or RTF documents that suffer from the tag plague for other reasons.
It is usually best to go through documents to be converted and manually set OCR zones and their properties (such as text, picture, orientation, inversion, etc.). The extra time spent doing this will be saved later when translating or making final edits to your work. And even with long documents (or especially with long documents), it is better to save the converted text with no formatting and then reapply formatting using defined styles. This approach usually also produces text that can be transferred to DTP programs such as InDesign with less trouble. Ignoring this particular bit of advice can lead to a lot of wasted time and grief.
Before you begin translating, it is also important to scan through the converted text and look for superfluous line breaks, excessive spaces and other formatting problems and fix these so that your translation segments will be as clean as possible. Such preparation at this stage is a very good investment of time. It may also be useful to run a source language spell check to catch errors in the text conversion.
Another reason I like to invest a bit of extra effort in cleaning up an OCR source text is that it is often part of the delivery to a client who may have lost (or never had but may need) an original, editable document. This can be part of your presentation as a professional, a little service to set you apart from the competition. In some cases I have seen persons skilled in OCR offer their conversion services to busy translators or LSPs; I don't think the need for this type of service, if done right, has decreased in real terms, though I can't say what the actual demand is these days. I used to get a lot of requests for this service, though I discouraged inquiries for languages that I don't know and eventually steered most of those asking toward developing their own capabilities.
What are your experiences with OCR? Any tips for best practice with your favorite tools?
What sorts of project challenges do you wish you could handle with your translation environment tools (Trados, DVX, memoQ, OmegaT, whatever) that you cannot today for technical reasons or for lack of adequate explanations and examples?It's only been up for a short time and the number of responses so far is modest, but some are quite interesting and may be revisited as blog posts or in other ways.
Some of the points raised so far involve the eternal topic of OCR for translation business. When my client Sansalone Technische Übersetzungen in Cologne first introduced me to the effective use of OCR for translation purposes many years ago, it was relatively rare in the world of commercial translation and too often incompetently performed, but I had been using that technology in one way or another for a decade already. But in many cases, "standard" procedures for optical character recognition are simply not well suited for our purposes, so I had a lot to learn.
Now some 9 years later, many of the LSPs and colleagues I know use OCR in some way, but unfortunately few do so efficiently or even usefully. Though sometimes there are TIFFs or JPEGs to be converted, most often these days the documents to be converted are obtained as some form of PDF. And there is enormous confusion and misrepresentation among translators as to what the various PDF formats are and how to deal with them.
I distinguish between two types of use for optical character recognition in my work: (1) quotation or count verification and (2) translation preparation. The former allows for considerable sloppiness, the latter for very little.
One of my LSP clients whom I introduced to OCR technology years ago uses it for one thing only: estimating text counts for quotation. Depending on the source, this may be very accurate or only a rough count (if there are serious contrast problems that can't be compensated, for example). I do this not only with PDFs and bitmap files such as JPEG or TIFF, but also with large, complex documents in other formats. For example, f someone sends me a 200 page document in an MS Word format and I need to prepare a cost estimate for services quickly, I will often print it to PDF, then run the PDF through an OCR engine and save the results as plain text for counting. One cannot always rely on the counts from Microsoft Word itself or various translation tools for text counting. Embedded objects, even editable ones, are generally not included in the counts. I have seen RTF documents where have the tables are ordinary RTF tables (which are counted) and others which look the same are spreadsheet objects (not counted unless you are a Star Transit user AFAIK). And PowerPoint files can have embedded Excel or Visio objects or other uncountable elements. Printing to PDF and doing an OCR subsequently avoids this problem and enables one to ensure that nothing big was missed when counting by other means. This procedure also serves as an "early warning" if there is text to translate that is not extracted by the translation tools. It really sucks to "finish" a long job only to discover that several thousand words in tables and diagrams remain untranslated.
Using OCR to prepare translations is often straightforward, but there are a number of traps that people commonly fall into. Do not, under any circumstances, be seduced by the automatic conversion settings of any commercial OCR program nor by options to save with the "original formatting". This is nearly always a disaster when working with translation tools. Problems may include bizarre text changes, disappearing chunks of text due to text box sizing problems, a plague of tags and more. About six years ago I wrote some guidelines on the ways to save and work with OCR text; these are a bit dated, but generally valid. I would also suggest getting and learning to use Dave Turner's Code Zapper macros for MS Word; these can not only clean a lot of garbage out of troublesome OCR texts but also from MS Word or RTF documents that suffer from the tag plague for other reasons.
It is usually best to go through documents to be converted and manually set OCR zones and their properties (such as text, picture, orientation, inversion, etc.). The extra time spent doing this will be saved later when translating or making final edits to your work. And even with long documents (or especially with long documents), it is better to save the converted text with no formatting and then reapply formatting using defined styles. This approach usually also produces text that can be transferred to DTP programs such as InDesign with less trouble. Ignoring this particular bit of advice can lead to a lot of wasted time and grief.
Before you begin translating, it is also important to scan through the converted text and look for superfluous line breaks, excessive spaces and other formatting problems and fix these so that your translation segments will be as clean as possible. Such preparation at this stage is a very good investment of time. It may also be useful to run a source language spell check to catch errors in the text conversion.
Another reason I like to invest a bit of extra effort in cleaning up an OCR source text is that it is often part of the delivery to a client who may have lost (or never had but may need) an original, editable document. This can be part of your presentation as a professional, a little service to set you apart from the competition. In some cases I have seen persons skilled in OCR offer their conversion services to busy translators or LSPs; I don't think the need for this type of service, if done right, has decreased in real terms, though I can't say what the actual demand is these days. I used to get a lot of requests for this service, though I discouraged inquiries for languages that I don't know and eventually steered most of those asking toward developing their own capabilities.
What are your experiences with OCR? Any tips for best practice with your favorite tools?
Aug 27, 2011
Data exchange issues for translators & TAUS
Jost Zetzsche of the International Writer's Group has written an interesting short report on data exchange standards for translation content, how they affect individual translators, why we should care and why freelancers should be involved in the development of these standards. The report can be downloaded from the link here or from the TAUS website where you'll be asked to give contact information that you may or may not want to provide for a mailing list.
Jost's paper is a good overview which explains its points clearly for nontechnical audiences as well. He has a gift for that, which is why his Toolkit newsletter and Toolbox primer for translators are so enormously popular. In some way I find it a shame that this latest information is distributed via TAUS, and organization regarding which I hold no little suspicion, but it is important that we keep an eye on those who pursue their agenda, and some limited collaboration can in fact be a good way to do this.
Why am I suspicious of TAUS? Two things.
First, I find the organization's case for sharing all TMs rather weak. In certain areas like standard error messages for software, I can see the point. Without even considering copyright and privacy issues, I simply find the idea foolish for much of the work I do. I don't care to see most of the trash TMs that LSPs accumulate, fail to maintain properly and try to "leverage" on the backs of their translating teams. Why would I be interested in greater quantities of linguistic sewage? Even my own TM content gets stale after a while and needs an overhaul as language and usage evolve. Those who plan to leverage their 100% matches for the next decade or two should hope that their customers and users like the taste of cardboard and old shoes or they may find themselves with communication and image problems at some point.
The second problem I have with TAUS is the organization's silly, shameless shilling for machine translation. Horsefeather-stuffed essays like "Want to ride the machine translation tidal wave?" or the intimidation set piece "What options do translators really have?" with its Darwinistic principles for how translating monkeys must evolve should give TAUS very little credibility with those in the industry who do not exhibit disturbing characteristics presumed to be part of a lemming's DNA.
This is not to say that I do not support TAUS. I think all my customers' competitors should hang on their every word and pursue the full program of data leveraging and process automation, eliminating as much of the human element from translation as possible. In Germany, I fully support initiatives by the Arbeitsamt, which previously retrained displaced coal miners as occupational therapists, to offer career path alternatives to call centers by certifying the long-term unemployed as MT post-editors (part of the "evolution" touted by TAUS), perhaps even providing their services to industry in the form of the beloved One Euro Jobs in a tradition of slave labor anchored in the middle of the last century.
I am perfectly content to be sidelined by history here, to stand lonely on a high hill, a translation creationist foolishly resistant to the industry's evolution, and miss the thrill of the MT tidal wave as it washes away common sense and quality and leaves consumers and business people picking through the strewn detritus of meaning.
Where will you be? The surf is up!
Jost's paper is a good overview which explains its points clearly for nontechnical audiences as well. He has a gift for that, which is why his Toolkit newsletter and Toolbox primer for translators are so enormously popular. In some way I find it a shame that this latest information is distributed via TAUS, and organization regarding which I hold no little suspicion, but it is important that we keep an eye on those who pursue their agenda, and some limited collaboration can in fact be a good way to do this.
Why am I suspicious of TAUS? Two things.
First, I find the organization's case for sharing all TMs rather weak. In certain areas like standard error messages for software, I can see the point. Without even considering copyright and privacy issues, I simply find the idea foolish for much of the work I do. I don't care to see most of the trash TMs that LSPs accumulate, fail to maintain properly and try to "leverage" on the backs of their translating teams. Why would I be interested in greater quantities of linguistic sewage? Even my own TM content gets stale after a while and needs an overhaul as language and usage evolve. Those who plan to leverage their 100% matches for the next decade or two should hope that their customers and users like the taste of cardboard and old shoes or they may find themselves with communication and image problems at some point.
The second problem I have with TAUS is the organization's silly, shameless shilling for machine translation. Horsefeather-stuffed essays like "Want to ride the machine translation tidal wave?" or the intimidation set piece "What options do translators really have?" with its Darwinistic principles for how translating monkeys must evolve should give TAUS very little credibility with those in the industry who do not exhibit disturbing characteristics presumed to be part of a lemming's DNA.
This is not to say that I do not support TAUS. I think all my customers' competitors should hang on their every word and pursue the full program of data leveraging and process automation, eliminating as much of the human element from translation as possible. In Germany, I fully support initiatives by the Arbeitsamt, which previously retrained displaced coal miners as occupational therapists, to offer career path alternatives to call centers by certifying the long-term unemployed as MT post-editors (part of the "evolution" touted by TAUS), perhaps even providing their services to industry in the form of the beloved One Euro Jobs in a tradition of slave labor anchored in the middle of the last century.
I am perfectly content to be sidelined by history here, to stand lonely on a high hill, a translation creationist foolishly resistant to the industry's evolution, and miss the thrill of the MT tidal wave as it washes away common sense and quality and leaves consumers and business people picking through the strewn detritus of meaning.
Where will you be? The surf is up!
Subscribe to:
Posts (Atom)