Wading through molasses...
Jan. 20th, 2014 10:27 pmI went back to where I found the luffa yesterday—this time without the dogs, so I could pay closer attention—and concluded that nothing in the vicinity resembled any stage of luffa that I am familiar with. It'd be cool if the seeds that I found along with the fibrous shell germinate, but I'll not lose any sleep if they don't.
Work progress was "nominal," which is to say I got as far as I expected to, today. I'm not particularly ahead or behind.
* * * One of the hazards of taking on assignments with an "editing" component is finding stuff that looks like the following:
All in all, this is not a bad way of displaying relevant information, except that—in fact—what the Russian actually means is "heat energy." And while there are a number of feasible equivalents (e.g., "thermal energy"), what is proposed as a 97% match here should, actually, have never been included in the package of work I am expected to complete.
In the end, the net result is to reduce my overall invoice for the job (very slightly, to be sure), because of necessity, I must provide the correct translation at the "editing rate," which is significantly less than the "translation rate." That noted, I should add that this sort of thing is fairly rare with this client, so it's not even worth mentioning to my project manager. But I have known agencies that make liberal use of poor translations to turn translation jobs into translation jobs paid at the editing rate, and have learned to avoid such work offerors like the plague.
* * * Tai chi went well this evening. I took a few spills (sifu calls it "flying"), and while I feel okay now, I am looking forward to seeing what the morning will bring after a night of shuteye.
Speaking of which...
Work progress was "nominal," which is to say I got as far as I expected to, today. I'm not particularly ahead or behind.
{0>The displayed information appears roughly the way my TM software shows it on the screen. The {0> denotes the start of a Russian "segment"; <}97>{> denotes the end of the Russian segment, states that this particular Russian and English pair are considered to be 97% "matched," and denotes the start of the corresponding English segment; and <0} denotes the end of the English segment.
тепловая энергия
<}97{>
Household and potable water
<0}
All in all, this is not a bad way of displaying relevant information, except that—in fact—what the Russian actually means is "heat energy." And while there are a number of feasible equivalents (e.g., "thermal energy"), what is proposed as a 97% match here should, actually, have never been included in the package of work I am expected to complete.
In the end, the net result is to reduce my overall invoice for the job (very slightly, to be sure), because of necessity, I must provide the correct translation at the "editing rate," which is significantly less than the "translation rate." That noted, I should add that this sort of thing is fairly rare with this client, so it's not even worth mentioning to my project manager. But I have known agencies that make liberal use of poor translations to turn translation jobs into translation jobs paid at the editing rate, and have learned to avoid such work offerors like the plague.
Speaking of which...