The Link Between Global Markets and Translation

(from PRWeb)

"L'industria della traduzione: realtà e prospettive del mercato italiano", a book by Gianni Davico, "focuses on the impact that globalization has made on the translation industry in Italy, while stressing the importance of communication across borders and cultures".

For a short review of the book, see this previous entry.

The downside of project memories

I find project memories fairly useless: it is true that they include fuzzy matches, and permit a translation company to limit the size of the memories sent to translators, but they are of very limited usefulness as regards terminology, since the concordance feature will only find terms that are in either the 100% or fuzzy matches, but will miss any term that appears in segments where the fuzzy threshold is not reached.

Post script:
One thing that was probably not clear in my original post: I think that project memories are almost useless, but cerainly not translation memory. Project memories are created by analyzing a project against an existing (full) translation memory, so that they may contain only the segments from the full memory that match (either 100% or as fuzzy matches) the segments contained in the text to be translated.
My issue with project memories is that any term contained in a segment of the full translation memory that is not similar enough to a segment in the text to be translated as to be included in the project memory is not going to appear in the project memory, and will, therefore, not appear in a concordance search.

...for example, like...

The ubiquitous "like" has, long taken over most illiterate conversation here in the United States.

Now it's rearing its ugly head even in technical writing, where the writers (one would think) are supposed to know better:

"There are a few things, for example, like some editing functions and the Help files, that are only available in the xxx program on the desktop."

Either use "...for example, some editing functions...", or "...like some editing functions...".

"...for example, like..." is redundant.

One reason I believe the sooner Trados disappears, the better...

...is the very poor quality of their matching engine. For example, I'm currently translating a list of software strings for a telephony system.

For the following string:

468:"Enable DUALmode"

I get a 62% fuzzy match, the original SL of which was:

451:"New building"

Very useful: the number "4", the colon and both quotes are, indeed, identical.

Even better:

For the string:

519:"Value"

I get a 74% fuzzy match, the original SL of which was:

142:"Permanent"

Hopefully, SDLX will be a change for the better.

Interesting Book on the Italian Translation Market

Gianni Davico has written an interesting book: L'industria della traduzione, Realtà e prospettive del mercato italiano.
This is the first book on the Italian translation market. High spots of the book are interviews with Rodrigo Vergara of Logos, and other players in the Italian translation industry. Also interesting is Davico's analysis of the emerging division of the translation market between high-end and low-end, with a shrinking share of the market left in the middle.
The book is very useful as an up-to-date introduction to a subject that has not been dealt with at book length before.
Even though aimed at the Italian market, most of its contents and conclusions hold true for other markets as well.
Among the trends examined in the book there is the continuing expansion of the translation market, which is closely linked, however, to a trend towards lower and lower rates.

New York Times' Review of Gregory Rabassa's Memoir

The Interpreter, by William Deresiewicz

An interesting review of "IF THIS BE TREASON, Translation and Its Dyscontents. A Memoir", By Gregory Rabassa.

"If translators are the anonymous heroes of contemporary literature, its anonymous superhero is Gregory Rabassa.
[...]
The contempt for translation partly reflects a desire to keep literature away from the grubby hands of the great unwashed, who don't know how to appreciate it anyway.
It is also a gesture of monumental bad faith. Has there ever been a writer who actually preferred not to be translated?"

Interesting article on Google Translator

Google Blogoscoped (Philipp Lenssen) has an interesting article on the current state of the Google machine translation system: Google Translator: The Universal Language.

The article was followed by some lively discussion, and was followed by another interesting article on the Qwikly.com blog.

How to use wildcard and format searches in MSWord to make sure all your numbers are formatted correctly

(c) Riccardo Schiaffino, 2005

Introduction: The Problem

A known drawback of translating using Trados is that segments which contain only numbers cannot be opened in the translation memory tool.
This can be a problem when the document to translate contains tables of numbers: for example, you might be translating English into Italian, and you want to make sure that all numbers are formatted correctly, with a comma to separate decimals and a dot to separate thousands.

Makeshift or wrong solutions

Of course, once you have completed your translation, you can go back and manually change all those dots into commas, and the commas that separate the thousands into dots... but unless it's only a question of just a few numbers, this is a very boring and error-prone activity (are you sure you are not leaving anything behind? ... there were several pages with numeric tables: are you really sure?)
Next you might think that a simple search and replace may solve your problem: Search for ".", replace with "," and... wait a minute: this would really mess-up punctuation everywhere, wouldn't it?

A better approach: regular expressions

Maybe a more refined search?
We are on the right track, now: a good solution would be to use a regular expression search (which, in MS Word, is called a "wild card" search).
Regular expressions are wild card on steroids: When we think of wild cards, we normally think of "*" to mean "multiple characters", and "?" to mean "any single character" (for instance, if you search for file in Windows and your search string is *.doc, you'll find all files with a "doc" extension, while if you search for "?and.doc" you may find "wand.doc", "land.doc", etc.). With regular expressions you can do that, and much more.

A simple regular expression search

As an example of a regular expression (or "wildcard") search, if we go back to our original problem, we can perform the following search:

1. In the Find field type "([0-9]).".

This means "any digit, followed by a dot".

2. In the Replace field type "\1,".

This means "replace whatever digit you have found with the same digit, but followed by a comma instead than by a dot".

A few necessary refinements

First of all, we don't want our search to also find numbers in the source language segments or in segments that we translated: the source language segments should be left as they are, and in the translated ones we have presumably already taken care of correctly formatting the numbers embedded in the text.

Add color to your search

One good way to achieve this is to add color to your search: if we have set Trados up so that different types of segments use different colors (for instance blue for source language text, dark green for 100% matches, etc.) we can limit our search and replace operation to text that uses the default ("automatic") font color: this would be the part of the documents that have not been opened by Trados, i.e., our numeric tables.

1. In order to do this, in both the Find and the Replace field, add a Format search:
2. Click the More button, if your Find and Replace is not already expanded
3. Click the Format button
4. Select Font in the drop down list
5. In the Find Font dialog, click on the Font color drop down list and select "automatic" as the color
6. Click OK

Refine the wildcard search

Besides changing the decimal dot used in English into the comma used in Italian, we also need to change the English thousands separator (the comma) into the Italian one (the dot), in order not to end up with something like "1,411,12".
If for example a line of the numbers we need to reformat is as follows:

123.11

1,411.12

321.03

1,241,345.41

In order to do this, we need to perform our search and replace in three stages:
First search for all the thousands separators, and replace them with an arbitrary symbol (not yet a dot):

1. In the Find field type ",([0-9]{3})", i.e., "search for a comma, followed by three digits"
2. In the Replace field type "##\1", i.e. "two '#' characters, followed by the three-digit number we found" (you can, of course, use other symbols instead of "##", so long as they are not likely to be used in the document where you are performing your search.)

At this point our example line will be as follows:

123.11

1##411.12

321.03

1##241##345.41

Then search for the decimal dots, and replace them with commas, as we did in our simple regular expression search above:

3. In the Find field type "([0-9]).".
4. In the Replace field type "\1,".

Our example line will have changed to:

123,11

1##411,12

321,03

1##241##345,41

Finally, search for our arbitrary character "##" and replace it with the correct thousands separator (the dot):

5. In the Find field type "##([0-9]{3})", i.e., "search for two '#'s, followed by three digits"
6. In the Replace field type ".\1", i.e. "a dot, followed by the three-digit number we found".

Our example line is now correct for Italian:

123,11

1.411,12

321,03

1.241.345,41

It is fairly easy to change the above searches so as to format your number to suite your target country's standards.

Another wildcard search: how to exclude 100% matches from editing

Another occasion when I find wildcard searches useful is when I have edit some file that my customer sens me already pre-translated in Trados (but not X-Translated), with the indication that 100% should not be touched (and will not be paid).
In this case I use the following search string to find only 0% or fuzzy matches and skip the 100% matches:

\<\}[0-9]{1,2}\{\>

This tells Word to search for a "<}", followed by a one- or two-digit number (but not a three-digit number), followed by "{>"
With this search string Word will find all the delimiters between SL and TL, but only in segments up to 99% match, while skipping all 100% matches.

Note:

If you decide to use this search string (or a similar one) while editing files translated with Trados with Workbench open, be aware of a bug: if you open the segment in Workbench before first closing the Find window, the segment will be opened with corrupt characters ("-{}-") at the beginning, and it will not be possible to close it (error message: "no segment appears to be open").
My workaround for this is:

1. Do all corrections possible without opening the segments in WOrkbench
2. When a segment has to be opened, be sure to close the Find window first.

Conclusion

I hope to have given you an idea of the kind of things you can do with regular expression searches, and of how useful they can be.
There is a lot more that you can do with regular expression searches in MS Word (and in other tools). You can find a good introduction to wildcard searches in MS Word on the following web page: http://word.mvps.org/FAQs/General/UsingWildcards.htm. A good introductory book is "Regular Expressions in 10 minutes", by Ben Forta (Sams teach Yourself series); it covers regular expressions in general, of which Word wild card searches are only a subset.

Agnew Tech-II Awarded Contract to Translate for Middle East Entrepreneur Training Program

from PRNewswire

A word to the wise: any translator is always advised to check the various payment practices fora and boards.

New translation portal launched

from PR Leap

Babelport.com Is a new translation portal, launched in February 2005. It has been developed and is maintained by cpi service of Leipzig, Germany.
I have visited the site. It looks professional and interesting. however, I have some doubts about how many such portals may remain viable, especially given the huge lead that such portals as ProZ seem to have as regards the number of members already signed.