2017 考研英语二 Translation
2017 考研英语二 Translation
Section III Translation 46. Directions: Translate the following text from English into Chinese. Write your translation on the ANSWER SHEET. (15 points) My dream has always been to work somewhere in an area between fashion and publishing. Two years before graduating from secondary school, I took a sewing and design course thinking that I would move on to a fashion design course. However, during that course I realized I was not good enough in this area to compete with other creative personalities in the future, so I decided that it was not the right path for me. Before applying for university I told everyone that I would study journalism, because writing was, and still is, one of my favourite activities. But, to be honest, I said it, because I thought that fashion and me together was just a dream—I knew that no one could imagine me in the fashion industry at all! So I decided to look for some fashion-related courses that included writing. This is when I noticed the course “Fashion Media & Promotion.”
Echo 参考译文、难点评析与错误点总结
说明:以下为 Echo 生成的非官方参考译文和学习解析,用于自测、批改和复盘;不等同于官方答案。
Echo 参考译文
我的梦想一直是在时尚和出版之间的领域工作。中学毕业前两年,我选了一门缝纫与设计课,心想以后会接着修一门时装设计课。然而,在学习那门课程期间,我意识到自己在这个领域不够出色,日后不足以与其他有创造力的人士竞争,因此我认定,这条路不适合我。申请上大学之前,我跟所有人说我要学新闻,因为写作曾经是——现在依然是——我最喜欢的活动之一。可是,说实话,当时我那么说是因为我觉得时尚和我结缘仅仅是个梦—— 我知道,别人根本无法想象我能进入时尚行业!于是,我决定找些含有写作的与时尚相关的课程。就在这个时候,我注意到了“时尚传媒与推广”这门课。
整体难点评析
本文主题可归为“教育实践与学习发展”。英语二翻译通常为整段翻译,共 15 分。复盘时要把段落连贯性、代词指代、句间转折和整体语气一起处理,而不是孤立翻每一句。
- 结构难点:重点关注名词化结构、被动与非谓语、逻辑连接、修饰后置、长句主干识别。先找主句谓语,再处理从句、分词、介词短语和插入成分,避免在中文里把修饰关系接错。
- 词义难点:不要机械使用词典第一义,尤其是抽象名词、学术动词和评价性形容词。应根据上下文确定它们是在表示事实、趋势、原因、态度还是结果。
- 逻辑难点:翻译时要显化英语中的因果、转折、让步、递进和目的关系。中文可以调整语序,但不能丢掉逻辑方向。
- 表达难点:中文译文要准确优先,再追求通顺。可以适度增补主语或承接词,但不能加入原文没有的信息。
常见错误点总结
- 主干误判:把修饰成分当主句,或漏掉真正谓语,会导致整句方向错误。
- 修饰范围错误:定语从句、分词短语和介词短语常常后置,翻译时要判断它修饰哪个名词或动作。
- 抽象名词处理生硬:如 process、approach、engagement、movement、connection 等词,要根据上下文译成“过程、方式、参与、运动、联系”等合适表达。
- 逻辑词漏译或反译:but、despite、while、so、as、with 等小词常决定句子关系,是扣分高发点。
- 中文表达不成句:逐词硬贴会让译文读不通。建议译完后用中文默读一遍,检查主语、谓语、宾语和逻辑连接是否完整。
Discussion
Comments
Thoughts, corrections, and follow-up notes are welcome here.