运用变译方法中摘译

运用变译方法中摘译、编译、译述、缩译、综述、述评、译评、译写、改译、

阐译、参议、仿作结束翻译事实

一、摘译

摘译，顾名思义，指先摘后译的变译方法。

例：Blame beer gut on genes

A beer-gut gene that gives fellas flabby tummies has been discovered by scientists. The medical breakthrough proves that guzzling ale is not the only reason why men develop saggy stomachs. They can also inherit from their parents a body make-up much more likely to run to fat. The beer-gut gene was tracked down by Italian experts. They found that men with a particular variant of it called DD were twice as likely to get fat. And they are also significantly more likely to put on the pounds around their midriff. Dr. Carol Copper said : “This sounds like a New Year’s gift for all those guys who are tubby round the middle but aren’t ready to give up the trips to the boozer. You’re stuck with the genes you’re born with, which could by just the excuse lardy lads who like a drink are looking for.” Dr. Pasquale Strazzullo warned the findings might not apply to British men-because the research was based entirely on Italians.

意大利科学家发现，体内携带一种被称做DD的啤酒肚基因变体的男子发胖的几率是常人的两倍。

上文是一则科技新闻报道。科学家最新发现，男子啤酒肚的产生源于体内一种叫做DD 的特殊基因变体。段中第5句正是这一科学新发现的核心内，因此将其作为摘译对象。这是单句摘译。要注意的是，原句中代词they, it指代不清，摘译时要还原为其所指代的具体对象。

二、编译

编译，指对原作加工整理然后翻译的变译方法。

例：She found herself minus the leg one week after consulting for a doctor about a persistent swelling she attributed to hard work and play in New York City – it was an inoperable bone tumor. While it saved her life, an ensuing year of chemotherapy reduced the once stunning model to a bald shadow of her former self.

原译：在询问医生为什么持续肿胀一个星期之后，她失去了一条腿。她曾认为是由于工作劳累和在纽约市游玩造成的。这是一个不宜手术的骨瘤。虽然手术挽救了她的生命，但接踵而来的长达一年的化疗使这位一度艳丽销魂的时装模特儿秀发脱落，枯瘦如柴，失尽昔日风采。

改译：她腿上出现了一个持续不消的肿块，原以为是在纽约又工作又游玩累的，看医生之后才知道是骨瘤，而且不宜手术。一周之后她便截去了那条腿。截肢虽然挽救了她的生命，但接踵而来的长达一年的化疗使这位一度艳丽消魂的时装模特儿秀发脱落，枯瘦如柴，失尽昔日风采。

译文理解准确，表达流畅，但有一个问题，就是照搬原作的内在逻辑结构，使汉语读者对所述事件的因果关系难以把握。滋生许多疑问。李运兴说，“这位译者没有注意到汉语更重自然时序的临摹性强的特点，致使译文多处发生连贯失调。比如，‘失去一条腿’的原因是什么?既然‘不宜手术’，怎么’手术挽救了她的生命’?”。因此，译者必须对原文句序进行调整，以符合汉语自然时序的思维逻辑。

三、译述

译述，指译者用自己的语言转述原作主要内容或部分内容的变译方法。

例：The unit of p.d., like that of e.m.f., is the volt, which is that p.d. existing between two points in a circuit where one unit of electrical energy has been changed to some other form of energy as consequence of one coulomb passing between the points.

原译:电位差的单位同电动势的单位一样，是伏特。伏特就是存在于电路两点之间的电位差。在这两点之间一个单位的电能转换成了另一种形式的能量，这是由于一库伦的电荷通过这两点所致。

改译:电位差的单位同电动势的单位一样，是伏特。电路中某两点之间由于一库伦电量通过时引起单位电能向其他能量形式转换，则此两点之间的电位差为1伏特。原译按照原文顺序译出，其表述“伏特就是存在于电路两点之间的电位差”与物理学中的有关概念不符。伏特是电位差的单位，但并不等于电位差。另外，顺序译法直接将英语的逻辑表达方式移人汉语，难以把原文的物理概念和逻辑联系表达清楚，因此需要对原文的后半部分进行调整，理顺逻辑关系。

四、缩译

缩译，即压缩性翻泽，指以较小的篇幅再现原作的主干内容的变译方法。

例：Writing Quality Requirements

By Kail E. Wiegers

…(1-30段略)

Guidelines for Writing Quality Requirements

There is no formulaic way to wtite excellent requirements. It is largely a matter of experience and learning from the requirements problems you have encountered in the past. Here are a few guidelines to keep in mind as you document software requirements.

Keep sentences and paragraphs short. Use the active voice. Use proper grammar, spelling, and punctuation. Use terms consistently and define them in a glossary or data dictionary.

To see if a requirement statement is sufficiently well defined, read it from the developer’s perspective. Mentally add the phrase, “call me when you’re done’ to the end of the requirement and see if that makes you nervous. In other word, would you need additional clarification from the SRS author to understand the requirement well enough to design and implement it? If so, hat requirement should be elaborated before proceeding with construction.

Requirement authors often struggle to find the right level of granularity. Avoid long narrative paragraphs that contain multiple requirements. A helpful granularity guideline is to write individually testable requirements. It you can think of a small munber of related tests to verify correct implementation of a requirement, it is probably written at the right level of detail. If you envision many different kinds of tests, perhaps several requirements have been lumped together and should be separated.

Watch out for multiple requirements that have been aggregated into a single statement. Conjunctions like “and”and “or”in a requirement suggest that several requirements have been combined. Never use “and/or” in a requirement statement.

Write requirements at a consistent level of detail throughout the document. I have seen requirements specifications that varied widely in their scope. For example, “A valid color code shall be R for red” and “A valid color code shall be G for green” might by split out as separate