Download Luận văn The translation of technical texts in shipbuilding
Translation is a very complicated process, it is complicated because it involves many aspects that need to be solved and decided by the translator during the translating process. The translator will have to create in the target language the equivalent context. Concerning to translation of technical text, in general, and technical text in shipbuilding, in specific, what seems to be one of the most difficult problems for the translator is the technical document is written for the expert(the engineer and the ones take part in building a ship) not for the lay people. That causes so many problems for the translator. Let us consider the following extract from D411101000-R1- Main engine specification:
Để tải bản DOC Đầy Đủ xin Trả lời bài viết này, Mods sẽ gửi Link download cho bạn sớm nhất qua hòm tin nhắn.
Ai cần download tài liệu gì mà không tìm thấy ở đây, thì đăng yêu cầu down tại đây nhé:
Nhận download tài liệu miễn phí
5.1. Technical style
Newmark (1988) suggests “unless its non-technical language is jazzed up and popularized, it is usually free from emotive language, connotations, sound-effects and original metaphor, if it is well-written”. However, not all the technical texts are well – written, thus, it’s the translator’s job to rephrase poorly written language.
Regarding to technical style, Parpcke (1975) distinguished four kinds of technical language: scientific, workshop level, every day usage level, and publicity/ sales. Yet, according to Newmark (1988), the division Parpcke is “likely to be valid only for one or two terms in a few fields”. He suggests the following scales: academic, professional and popular.
5.2. Technical terms
Newmark (1988) states that “ Technical translation is primarily distinguished from other forms of translation by terminology”. Thus, the core characteristic of a technical text in any field is terms; terms are also the main factor to distinguish a technical text from other kinds of texts. And, the central difficulty in technical translation is usually new terminology.
It is due to the fact that some technical terms appear only once in the source language and the context is not clear to the translator. Furthermore, the technical terms are distilled knowledge and written for specialists in that field.
It is also because that even standardized terms may have more than one meaning in one specific field, as well as in the other fields.
5.3. Technical terms and descriptive terms
One matter in technical translation is to distinguish technical and descriptive terms.
According to Newmark (1988), the original SL writer may use a descriptive terms for a technical object for three reasons:
The object is new, and has not yet got a name
The descriptive term is being used as a familiar alternative, to avoid repetition;
The descriptive term is being used to make a contrast with another one.
Also, he suggests that technical terms and descriptive terms should be translated by their counterparts, and the translator should resist the temptation of translating a descriptive terms by a technical terms for the purpose of showing off his/ her knowledge. However, he points out that if the SL descriptive term is being used either because of the SL writer’s ignorance, or because the appropriate technical term does not exist in the SL, and if an object strange to the SL but not to the TL culture is being referred to, the translator is justified in translating a descriptive term by a technical term.
Further to technical and descriptive terms, Newmark (1988) claims it is a trend that professional translators make “a mystique out of their craft” by denying any descriptive terms where a TL technical term exists. He points out the reason that because technical terms are standardized language and more precise (narrower in semantic range) whereas, descriptive terms are non-standardized language.
5.4. Translation method
5.4.1. Beginning technical translation
Idiom says that “practice makes perfect”. Technical translation is similar. The more the translator get practice, the better he/ she translates. However, the challenge or the difficult thing for the technical translator is that the translator is not well – informed about the topic of the technical text, is lack of knowledge about technicality. And as Newmark (1988) advises the translator is “more interested in understanding the description, the function and the effect of a concept such as entropy rather than in learning laws, particularly axioms, theorems, theories, systems in some of which entropy is involved”. Or to put it more clearly, “to translate a text you so not have to be an expert in its technology or its topic; but you have to understand that text and temporarily know the vocabulary it uses”.
He suggests as a translator working in technical translation, when translating a text, the translator has to be able to stand back and understand roughly what is happening in the real life or he/ she has to convince himself/ herself that the sentence which has just been translated makes sense. Although many technical terms can be translated “literally”, the translator has to check the present validity with the register and dialect.
Thus, in order to begin a technical text, according to him, the translator should, at first, read it to understand what the text is about (underline difficult words) and then assess its nature ( proportion of persuasion to information), its degree of formality, its intention (attitude to topic), the possible cultural and professional differences between the readership and the original one. Next, the translator should give the translation a framework of recognized house-style. The translator has to take into account everything, every word, every figure, letter, every punctuation mark…..
5.4.2. Translating the title
Newmark (1988) classifies title either is descriptive or allusive. According to him, a descriptive title names the subject succinctly while allusive title is suitable for some imaginative literature and popular journalism and may be changed.
The title states the subject but it does not always mention the purpose or intention of the process which is described.
Besides, Newmark (1988) also states two other points of title. Firstly, the title of the SL text is often two long by English standards. Secondly, the title has a transparent collocation.
And according to him, almost errors in technical translation are caused by misleading adjective plus noun collocations for standardized terms. And for non-standardized terms, the errors can be caused by transparent or motivated verb plus object, or subject plus verb collocations.
5.4.3. Going through the text
It is suggested by Newmark (1988) that The translator, then, should read the text through to get the gist of the main idea and underline all words and structures that appear to contain problems: new technical terms, special expressions, syntactic ambiguity…. After that, the translator can translate sentence by sentence, making grammatical shifts to for natural language. In technical translation, the translator can be as bold and free in recasting grammar (cutting up sentences, transposing clauses, converting verbs to nouns, etc.) as in any type of informative text, provided the original is defective. Lexically, the main characteristic of technical language is its actual richness and its potential infinity. The translator has to ensure the equivalent level of register to TL (he/ she may separate new terms and compare to the context, sometimes actual practice to deal with the meaning). And last, the translator has to adjust the translated sentence as per the technical style.
Chapter 2: An investigation into translation of technical texts in shipbuilding
1. Text characteristic in shipbuilding
1.1. Kinds of texts
Texts, as many other fields, are the main way to connect the builder, the engineers and the owner. Through the texts, all the necessary written information is transferred. Thus, they are very important. And in shipbuilding, texts are shown in the followings types:
Specification
For the vessel, specification is the thing that introduces, describes the main particulars, equipment as well as necessary related matters the vessels must have when going in service. Outline specification of 260 TEU container vessel is an example.
General description
Type of ship
Single crew, slow speed diesel engine driven container vessel with bulbous bow, transom stern and five (5) box-shaped cargo holds for transportation of container in holds with cell guides, and on deck with lashing
Type of cargo
Containers (TEUs and FEUs)
Classification
NK or ABS
Navigation area
Ocean going
Flag
Singapore
Technical manual
This kind of document is the one, besides specification, that the supplier, the maker and owner and builder get information about the operation of the equipment in the vessel. Without it, we can not build a ship, we can not càior assemble any equipment.
Procedures
Another kind of text the translator must deal with is the procedures. In terms of its nature, the procedures are the working sequences when we carry out any testing, installation, assembly onboard, in site, etc…
Fly sheet
This kind of document is the short, concise text which is used to discuss a problems occurring during any stages in shipbuilding. It can be the working modification in which the reason and measure are pointed out.
Let us take an example:
VINASHIN
NASICO
technical information
Job No. (Signal) : F56/NT01
Hull No. (Signal) : 5092
Part (Signal) :HULL
BM-TKCN-02
No:R032\F56-NT01
Date: 27/4/2009
P/Ps: 1/4
`
Tªn chi tiÕt /h¹ng môc:
Block 3Đ31
Sè / Tªn...
Download miễn phí Luận văn The translation of technical texts in shipbuilding
Translation is a very complicated process, it is complicated because it involves many aspects that need to be solved and decided by the translator during the translating process. The translator will have to create in the target language the equivalent context. Concerning to translation of technical text, in general, and technical text in shipbuilding, in specific, what seems to be one of the most difficult problems for the translator is the technical document is written for the expert(the engineer and the ones take part in building a ship) not for the lay people. That causes so many problems for the translator. Let us consider the following extract from D411101000-R1- Main engine specification:
Để tải bản DOC Đầy Đủ xin Trả lời bài viết này, Mods sẽ gửi Link download cho bạn sớm nhất qua hòm tin nhắn.
Ai cần download tài liệu gì mà không tìm thấy ở đây, thì đăng yêu cầu down tại đây nhé:
Nhận download tài liệu miễn phí
Tóm tắt nội dung:
empty verbs, present tenses) and it technical format (technical report).5.1. Technical style
Newmark (1988) suggests “unless its non-technical language is jazzed up and popularized, it is usually free from emotive language, connotations, sound-effects and original metaphor, if it is well-written”. However, not all the technical texts are well – written, thus, it’s the translator’s job to rephrase poorly written language.
Regarding to technical style, Parpcke (1975) distinguished four kinds of technical language: scientific, workshop level, every day usage level, and publicity/ sales. Yet, according to Newmark (1988), the division Parpcke is “likely to be valid only for one or two terms in a few fields”. He suggests the following scales: academic, professional and popular.
5.2. Technical terms
Newmark (1988) states that “ Technical translation is primarily distinguished from other forms of translation by terminology”. Thus, the core characteristic of a technical text in any field is terms; terms are also the main factor to distinguish a technical text from other kinds of texts. And, the central difficulty in technical translation is usually new terminology.
It is due to the fact that some technical terms appear only once in the source language and the context is not clear to the translator. Furthermore, the technical terms are distilled knowledge and written for specialists in that field.
It is also because that even standardized terms may have more than one meaning in one specific field, as well as in the other fields.
5.3. Technical terms and descriptive terms
One matter in technical translation is to distinguish technical and descriptive terms.
According to Newmark (1988), the original SL writer may use a descriptive terms for a technical object for three reasons:
The object is new, and has not yet got a name
The descriptive term is being used as a familiar alternative, to avoid repetition;
The descriptive term is being used to make a contrast with another one.
Also, he suggests that technical terms and descriptive terms should be translated by their counterparts, and the translator should resist the temptation of translating a descriptive terms by a technical terms for the purpose of showing off his/ her knowledge. However, he points out that if the SL descriptive term is being used either because of the SL writer’s ignorance, or because the appropriate technical term does not exist in the SL, and if an object strange to the SL but not to the TL culture is being referred to, the translator is justified in translating a descriptive term by a technical term.
Further to technical and descriptive terms, Newmark (1988) claims it is a trend that professional translators make “a mystique out of their craft” by denying any descriptive terms where a TL technical term exists. He points out the reason that because technical terms are standardized language and more precise (narrower in semantic range) whereas, descriptive terms are non-standardized language.
5.4. Translation method
5.4.1. Beginning technical translation
Idiom says that “practice makes perfect”. Technical translation is similar. The more the translator get practice, the better he/ she translates. However, the challenge or the difficult thing for the technical translator is that the translator is not well – informed about the topic of the technical text, is lack of knowledge about technicality. And as Newmark (1988) advises the translator is “more interested in understanding the description, the function and the effect of a concept such as entropy rather than in learning laws, particularly axioms, theorems, theories, systems in some of which entropy is involved”. Or to put it more clearly, “to translate a text you so not have to be an expert in its technology or its topic; but you have to understand that text and temporarily know the vocabulary it uses”.
He suggests as a translator working in technical translation, when translating a text, the translator has to be able to stand back and understand roughly what is happening in the real life or he/ she has to convince himself/ herself that the sentence which has just been translated makes sense. Although many technical terms can be translated “literally”, the translator has to check the present validity with the register and dialect.
Thus, in order to begin a technical text, according to him, the translator should, at first, read it to understand what the text is about (underline difficult words) and then assess its nature ( proportion of persuasion to information), its degree of formality, its intention (attitude to topic), the possible cultural and professional differences between the readership and the original one. Next, the translator should give the translation a framework of recognized house-style. The translator has to take into account everything, every word, every figure, letter, every punctuation mark…..
5.4.2. Translating the title
Newmark (1988) classifies title either is descriptive or allusive. According to him, a descriptive title names the subject succinctly while allusive title is suitable for some imaginative literature and popular journalism and may be changed.
The title states the subject but it does not always mention the purpose or intention of the process which is described.
Besides, Newmark (1988) also states two other points of title. Firstly, the title of the SL text is often two long by English standards. Secondly, the title has a transparent collocation.
And according to him, almost errors in technical translation are caused by misleading adjective plus noun collocations for standardized terms. And for non-standardized terms, the errors can be caused by transparent or motivated verb plus object, or subject plus verb collocations.
5.4.3. Going through the text
It is suggested by Newmark (1988) that The translator, then, should read the text through to get the gist of the main idea and underline all words and structures that appear to contain problems: new technical terms, special expressions, syntactic ambiguity…. After that, the translator can translate sentence by sentence, making grammatical shifts to for natural language. In technical translation, the translator can be as bold and free in recasting grammar (cutting up sentences, transposing clauses, converting verbs to nouns, etc.) as in any type of informative text, provided the original is defective. Lexically, the main characteristic of technical language is its actual richness and its potential infinity. The translator has to ensure the equivalent level of register to TL (he/ she may separate new terms and compare to the context, sometimes actual practice to deal with the meaning). And last, the translator has to adjust the translated sentence as per the technical style.
Chapter 2: An investigation into translation of technical texts in shipbuilding
1. Text characteristic in shipbuilding
1.1. Kinds of texts
Texts, as many other fields, are the main way to connect the builder, the engineers and the owner. Through the texts, all the necessary written information is transferred. Thus, they are very important. And in shipbuilding, texts are shown in the followings types:
Specification
For the vessel, specification is the thing that introduces, describes the main particulars, equipment as well as necessary related matters the vessels must have when going in service. Outline specification of 260 TEU container vessel is an example.
General description
Type of ship
Single crew, slow speed diesel engine driven container vessel with bulbous bow, transom stern and five (5) box-shaped cargo holds for transportation of container in holds with cell guides, and on deck with lashing
Type of cargo
Containers (TEUs and FEUs)
Classification
NK or ABS
Navigation area
Ocean going
Flag
Singapore
Technical manual
This kind of document is the one, besides specification, that the supplier, the maker and owner and builder get information about the operation of the equipment in the vessel. Without it, we can not build a ship, we can not càior assemble any equipment.
Procedures
Another kind of text the translator must deal with is the procedures. In terms of its nature, the procedures are the working sequences when we carry out any testing, installation, assembly onboard, in site, etc…
Fly sheet
This kind of document is the short, concise text which is used to discuss a problems occurring during any stages in shipbuilding. It can be the working modification in which the reason and measure are pointed out.
Let us take an example:
VINASHIN
NASICO
technical information
Job No. (Signal) : F56/NT01
Hull No. (Signal) : 5092
Part (Signal) :HULL
BM-TKCN-02
No:R032\F56-NT01
Date: 27/4/2009
P/Ps: 1/4
`
Tªn chi tiÕt /h¹ng môc:
Block 3Đ31
Sè / Tªn...