Designing Buildings - User contributions [en]

User:Pierre Fuentes

2018-04-11T08:40:19Z

Pierre Fuentes:

Translation of building contracts

2014-01-14T16:04:27Z

Pierre Fuentes:

'''CONTRACT''' '''TRANSLATION'''

== '''Translation: how it works''' ==

Translation is at the centre of an age-old debate that opposes 'word-for-word' and 'sense-for-sense'. The strategy generally recommended to translate building contracts lies somewhere in between.

In his ''English Reader's guide to the French Legal System'' (1991), Martin Weston, Senior Translator of the European Court of Human Rights, prescribes 'functional equivalence', a translation strategy that refers to 'dynamic equivalence', a concept developed by the famous American Baptist minister Eugene Nida (Nida and Taber, 1969/1982). Weston recommended functional equivalence as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (Venuti, 1995:22). In other words, his equivalence strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (ibid).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as 'literal translation'. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". 

He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (Newmark, 1988:76).

== What does it mean for building contracts? ==

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. 

In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. 

It is therefore vital that the person who translates them understands the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

Weston's 'Functional equivalence' is therefore a strategy that is functionally driven by '''''purpose'''''. 

While is it based on the same approach as Nida's dynamic equivalence - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

== Some examples ==

=== '''RIBA work stages''' ===

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called Developed Design.

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

=== '''Document names''' ===

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (Uff, 2002).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

=== '''Standards ''' ===

British Standards are often preferred to heavy technical information in architectural specifications. But BS can sometimes be considered as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

== References ==

Alcaraz, E. and Hughes, B. 2002. ''Legal Translation explained''. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. ''Drafting Legal Documents: Principles and Practices'', 2d ed. West Publishing Co.

''Code de la construction et de l'habitation'', septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. ''Réflexions sur le discours juridique''. Meta 24, pp. 26-34.

Dickson, B. 1994. ''Introduction to French Law''. London: Pitman Publishing.

French Ordre des architectes, 2013, ''Outils et documents ''[online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. ''La linguistique comme science auxiliaire dans les disciplines juridiques''. Meta, 24 pp. 9-17

Munday, J. 2008 ''Introducing Translation Studies, Theories and applications'', 2nd Edition. London: Routledge.

Newmark, Peter 1988. ''A Textbook of Translation''. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. ''The theory and practice of Translation''. Leiden, The Nederlands: Brill Academic Publishers.

Trosborg, A. 1997. ''Rhetorical strategies in legal language: discourse analysis of statutes and contracts''. Tübingen: Narr.

Uff, J. 1974/2002. ''Construction Law''. London: Sweet and Maxwell.

Venuti, L. 1995, ''The Translator’s Invisibilit''y, London: Routledge.

Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess.

Weston, Martin. 1991. ''An English Reader's guide to the French Legal System''. Oxford: Berg Publishers.

Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T03:21:53Z

Pierre Fuentes:

'''CONTRACT''' '''TRANSLATION'''

== '''Translation: how it works''' ==

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

== What does it mean for building contracts? ==

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

== Some examples ==

=== '''RIBA work stages''' ===

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

=== '''Document names''' ===

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (7).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

=== '''Standards ''' ===

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

== NOTES: ==

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit. 

7. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T03:01:36Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

== '''Translation: how it works''' ==

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

== What does it mean for building contracts? ==

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

== Some examples ==

=== '''RIBA work stages''' ===

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

=== '''Document names''' ===

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (7).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

=== '''Standards ''' ===

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

== NOTES: ==

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit. 

7. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T03:00:54Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

== '''Translation: how it works''' ==

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

== What does it mean for building contracts? ==

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

== Here are a few examples. ==

=== '''RIBA work stages''' ===

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

=== '''Document names''' ===

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (7).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

=== '''Standards ''' ===

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

== NOTES: ==

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit. 

7. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:52:02Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (7).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit. 

7. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

User:Pierre Fuentes

2013-12-20T02:47:38Z

Pierre Fuentes:

French translation is my speciality, but I also write and edit articles on translation and architecture for magazines, newsletters and academic architectural publications. 

I write a [http://pierrefuentes.info French-language blog] about architecture, cultural clichés and French translation.

 

<div>@ArcTranslations</div>

Translation of building contracts

2013-12-20T02:43:02Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is --[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:11, 20 December 2013 (UTC)therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail" (7).

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit. 

7. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition'''''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:40:18Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System (1)'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida (2). Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism" (3). In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response" (4).

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word" (5).

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 1983) (6). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is --[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:11, 20 December 2013 (UTC)therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail"8.

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System.''

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, p22

4. Ibid.

5. Newmark, Peter, 1988, A Textbook of Translation, p76.

6. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit.

== References ==

Alcaraz, E. and Hughes, B. 2002. Legal Translation explained. Manchester: St Jerome.

Butt, P. and Castle, R. W. 2006. ''Modern legal drafting: a guide to using clearer language ''''2d edition''. Cambridge University Press: Cambridge.

Cao, Deborah. 2007. ''Translating Law''. Clevedon: Multilingual Matters.

Child, B. 1992. Drafting Legal Documents: Principles and Practices, 2d ed. West Publishing Co.

Code de la construction et de l'habitation, septième édition. 1994. Paris: Dalloz.

Darbelnet, J. 1979. Réflexions sur le discours juridique. Meta 24, pp. 26-34.

Dickson, B. 1994. Introduction to French Law. London: Pitman Publishing.

Jacobson, M. H. S. 2008. "A Checklist for Drafting Good Contracts". ''Journal of the Association of Legal Writing Directors ''[online] Vol. 5 pp 79-117

Mounin, G. 1979. La linguistique comme science auxiliaire dans les disciplines juridiques. Meta, 24 pp. 9-17

Munday, J. 2008 Introducing Translation Studies, Theories and applications, 2nd Edition. London: Routledge.

Newmark, Peter 1988. A Textbook of Translation. London: Prentice Hall.

Nida, E. 1975. ''Language Structure and Translation'', Stanford CA: Stanford University Press.

Nida, E. and Taber, C. 1969/1982. The theory and practice of Translation. Leiden, The Nederlands: Brill Academic Publishers.

Ordre des architectes, 2013, Outils et documents [online] [http://www.architectes.org/outils-et-documents&nbsp http://www.architectes.org/outils-et-documents&nbsp]; [accessed 18 Decembre 2013]

Trosborg, A. 1997. Rhetorical strategies in legal language: discourse analysis of statutes and contracts. Tübingen: Narr.

Uff, J. 1974/2002. Construction Law. London: Sweet and Maxwell

Weston, Martin. 1991. An English Reader's guide to the French Legal System. Oxford: Berg Publishers.

--[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:13:54Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System1'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida2. Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism"3. In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response"4.

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark5, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word"6.

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 19837). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is --[[User%3APierre%20Fuentes|Pierre Fuentes]] 02:11, 20 December 2013 (UTC)therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail"8.

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System'', Oxford: Berg Publishers.

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation, Leiden, Nederlands: Brill Academic Publishers.

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, London: Routledge. p22

4. Ibid.

5. Sadly, both of these highly influential linguists died last year.

6. The most famous quote of translation studies? Newmark, Peter, 1988, A Textbook of Translation, London: Prentice Hall, p76.

7. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit.

8. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

 

--[[User:Pierre Fuentes|Pierre Fuentes]] 02:13, 20 December 2013 (UTC)

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:11:43Z

Pierre Fuentes:

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System1'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida2. Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism"3. In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response"4.

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark5, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word"6.

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 19837). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is --[[User:Pierre Fuentes|Pierre Fuentes]] 02:11, 20 December 2013 (UTC)therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail"8.

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni'''''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System'', Oxford: Berg Publishers.

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation, Leiden, Nederlands: Brill Academic Publishers.

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, London: Routledge. p22

4. Ibid.

5. Sadly, both of these highly influential linguists died last year.

6. The most famous quote of translation studies? Newmark, Peter, 1988, A Textbook of Translation, London: Prentice Hall, p76.

7. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit.

8. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:08:27Z

Pierre Fuentes: Protected "Translation of building contracts": Not finished ([edit=author] (indefinite))

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System1'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida2. Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism"3. In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response"4.

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark5, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word"6.

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 19837). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is vital therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail"8.

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System'', Oxford: Berg Publishers.

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation, Leiden, Nederlands: Brill Academic Publishers.

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, London: Routledge. p22

4. Ibid.

5. Sadly, both of these highly influential linguists died last year.

6. The most famous quote of translation studies? Newmark, Peter, 1988, A Textbook of Translation, London: Prentice Hall, p76.

7. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit.

8. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]

Translation of building contracts

2013-12-20T02:05:47Z

Pierre Fuentes: Created page with " '''TRANSLATING BUILDING CONTRACTS''' Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommende..."

'''TRANSLATING BUILDING CONTRACTS'''

Translation is at the centre of an age-old debate that opposes "word-for-word" and “sense-for-sense”. The strategy generally recommended to translate building contracts lies somewhere in between.

In his 1991 ''English Reader's guide to the French Legal System1'', Martin Weston prescribes "functional equivalence", a translation strategy that refers to "dynamic equivalence", a concept developed by the famous American Baptist minister Eugene Nida2. Weston recommended "functional equivalence" as the ideal translation method for construction law, while word-for-word was to be regarded as the basic method.

But another famous American linguist, Lawrence Venuti argued that Eugene Nida's work was essentially motivated by the exigencies of Bible translation and that the "values that inform his theory of translation [are] Christian evangelism and cultural elitism"3. In other words, his “equivalence” strategy had a different ''purpose'' than that of the translation of construction and legal translation more generally. Moreover, Eugene Nida was "masking a basic disjunction between the source and target-language texts, which puts into question the possibility of eliciting 'similar' response"4.

In short, dynamic equivalence is illusory, so one might as well stick to what is often described as “literal translation”. Indeed, Martin Weston insisted that "so long as they are natural in the target language, [word-for-word translations] should not be shunned merely because they are literal translations". He echoed another famous British linguist, Peter Newmark5, insisting that "a good translator abandons a literal version only when it is plainly inexact or […] badly written. A bad translator will always do his best to avoid translating word for word"6.

In the context of building developments, the parties involved often request the inclusion of foreign documentation in the contract, e.g. to establish the cost of construction.

However, most legal translation scholars agree that contracts are system-bound (see for instance Cao 2007, Zweigert and Kötz 1992, Weisflog 1987 and Weston 19837). Indeed, like all contracts, building contracts reflect the history, evolution and culture of their specific legal system. In practice, this means that a British JCT contract must not be translated as if it were a French ''contrat de louage d'ouvrage''.

But if the translator decides to go for a word-for-word version, or a literal translation, a French contractor might not understand the original message and the French translation will not elicit the right response.

The dilemma is that building contracts are a hybrid genre. The boundaries between the legal instructions and the technical information are fuzzy. It is vital therefore vital that the person who translates them understand the context, knows who the text is addressing and what function the translation is meant to fulfil. Legal aspects or not, the translator must produce a text that conforms to the '''''functional '''''conventions known to the foreign audience.

"Functional equivalence" is therefore a strategy that is functionally driven by '''''purpose'''''. While is it based on the same approach as Nida's “dynamic equivalence” - seeking a domestic equivalence to which the reader can relate - '''''it avoids references to the target legal system and sticks to the function of the given order'''''.

Here are a few examples.

'''RIBA work stages'''

Architect contracts are based on work stages. A main reference used in the UK is that of the Royal Institute of British Architects. The 2013 RIBA work stages include several stages, among them the so-called "Developed Design".

If French translators were to translate it word-for-word, they would probably write "''Design Détaillé"''. This would be worse than meaningless. It would be linguistically treacherous because ''Design'' is a false friend in French - it refers to the design of industrial objects, not to that of buildings.

On the contrary a dynamic approach would be "''Avant-projet détaillé (APD)"'' (lit. Detailed Pre-Project). This is meaningful because it is the name of an approximate equivalent in the French legal system. But it would be legally treacherous as Developed Design refers to the English context of building contracts.

The functional equivalence could consist in using the ''function'' of the work stage (the provision of developed or even technical design before proceeding to pre-construction phase) : "''phase de projet détaillé''" (detailed project phase) for instance, could be meaningful but not legally treacherous.

'''Document names'''

A common document of building contract information is architectural specifications. It is a "document that describes the work to be carried out, often in great technical detail"8.

The French literal translation could be "''spécifications architecturales''". It may be faithful but it is nowhere near the corresponding French documents: c''ahiers des clauses techniques générales et particulières ''for instance (books of general and particular technical specifications).

Again the latter could be a good dynamic equivalence, but it would be legally dangerous. Instead, functional equivalence could provide "clauses techniques" (technical specifications), a name that would makes sense to French readers without referring explicitly to their legal system.

'''Standards '''

British Standards are often preferred to heavy technical information in architectural specifications. But BS can be regarded as a reference to the jurisdiction of the law of England and Wales.

This is why BS that originate from European regulations are referenced as EN. For instance "BS 12620" (aggregates for concrete), is actually a European standard. In French, it has a valid equivalent: NF 12620 (where NF, or BS, should actually be followed by the initial EN).

But some BS are purely British and have no equivalents. For instance, BS 4800:2011 (schedule of paint colours for building purposes) is solely British. In such case, a translator's note is helpful, for instance:

''NdT: ''''norme britannique comportant une nomenclature de couleurs de peinture, utilisée pour convenir du choix de couleurs dans le cadre de permis de construire, de travaux de rénovation ou de grands travaux. Ces couleurs sont conformes aux exigences des règlementations en vigueur au Royaume-Uni''.

[Translator’s note: British standard that provides a schedule of colours of paint used for planning application, conservation or major works. These paint colours meet the local regulations requirements of the UK].

NOTES:

1. Weston, Martin, 1991, ''An English Reader's guide to the French Legal System'', Oxford: Berg Publishers.

2. Nida, Eugene and Taber, Charles, 1969/1982, The theory and practice of Translation, Leiden, Nederlands: Brill Academic Publishers.

3. Venuti, Lawrence, 1995, ''The Translator’s Invisibilit''y, London: Routledge. p22

4. Ibid.

5. Sadly, both of these highly influential linguists died last year.

6. The most famous quote of translation studies? Newmark, Peter, 1988, A Textbook of Translation, London: Prentice Hall, p76.

7. Cao, Deborah, 2007, ''Translating Law'', Clevedon: Multilingual Matters. Zweigert, Konrad and Kötz, Hein, 1992, ''Introduction to comparative law, ''Oxford: Clarendon Press. Weisflog, Walter, 1987, "Problems of legal translation", in ''Swiss reports presented at the 12th International Congress of comparative law'', Zürich: Schultess. Weston, Martin, 1991. op cit.

8. Uff, John, 1974/2002, Construction Law, London: Sweet & Maxwell

[[Category:Contracts_/_payment]]
[[Category:Other_legislation]]
[[Category:Regulations]]
[[Category:Appointments]]
[[Category:Client_procedures]]
[[Category:Procurement]]
[[Category:Public_procedures]]
[[Category:Roles_/_services]]