Machine translation and legal translation

Every time I think I might write about this it seems a drop in the ocean, but then the topic comes up again. Machine translation has become very much better since it was first based on neural networks. In fact, I thought we had departed from rule-based MT and arrived at statistical MT, but we are now on neural MT, excuse my ignorance.

In my experience of using DeepL and DeepL Pro and Google Translate a few times, these systems are very good but not 100% reliable. Which means that sometimes a negative sentence may be rendered as a positive. I have no experience of revising MT output or preparing texts for MT.

But what strikes me specifically about legal texts is that when I put a German text through DeepL, the standard or ‘official’ translations of court names and statute titles are missing, although in Linguee they are present. In the old days, a law firm wanting to use rule-based MT was able to adapt its MT system by filling it with the standard translations into English. Now it is not so, and I would spend a lot of time revising the versions.

This was remarked on in a short article in MDÜ 6/2019 by hans Christian von Steuber. He refers to a talk by Patrick Mustu “Was DeepL & Co. im Zeitalter von 4.0 (noch) nicht können”:

Ein Beispiel aus eminer Erfahrung: Die beliebte “Datenschutzgrundverordnung” wird als “basis data protection regulation” übersetzt, “DSGVO” überhaupt nicht”.

This is the GDPR. It’s always surprising when this is not recognized. And when the translation of a statute title varies within one text.

Another reference was mentioned by colleagues this week. The Swiss Federal Chancellery (Bundeskanzlei) was going to buy licences for 2000 DeepL users in 2019 (UEPO December 2018) and had a review of the effectiveness done (PDF Bericht DeepL-Test). Here an example:

Original text: loi fédérale sur les prestations
de sécurité privées fournies à
l’étranger (LPSP)

DeepL translation: Federal Law on Private Security
Services Abroad (LPSP)

Post-edited text: Federal Act on Private Security
Services Provided Abroad
(PSSA)

I always wonder when I see English versions of abbreviations of statute names recommended. Leaving it in German is odd and so is creating an English version such as PSSA (obviously the work of a human post-editor).

That’s all I have to say about MT and legal translation, but the Swiss test contains a classification of MT problems.

Goodbye to Palandt

Bye-bye, Palandt! – post at the Dispute Resolution Germany blog, on July 27th:

C.H. Beck, Germany’s leading legal publisher, today announced that several of its publications will finally be renamed in light of the Nazi past of the jurists whose names they currently bear. All of these publications are household names for law students and practitioners alike.

The campaign for these names to be changed was pretty much a niche thing for many years and gained traction and public visibility only fairly recently.

I didn’t realize that Palandt was a member of the Nazi party. According to German Wikipedia, Beck Verlag chose him as the editor (of the BGB commentary) at short notice in 1938. Palandt (1877-1951) wrote the foreword and introduction until the tenth edition in 1952. In 1945 he removed the pro-Nazi bits. He was allegedly not responsible for the overall editing.

I haven’t got a Palandt at the moment, but I have sometimes bought reduced-price older editions in Germany and found them very useful, but not predictably frequently. Probably there are ways of consulting it online – it was never very easy as a full-time freelance translator to go to a library to consult it, as time was scarce.

After much criticism, Beck Verlag has eventually decided to change the name from Palandt to Grüneberg. The same fate befalls Maunz, Schönfelder (killed in Italy in 1944) and Blümich (I don’t think I’ve encountered Blümich).

‘Shall’ in English contracts

I recently heard a webinar by Christin Dallmann and Richard Delaney on translation problems in contract law. I highly recommend these webinars. It reminded me of that old chestnut: do we use ‘shall’ in a contract (when drafting or translating)?

Richard Delaney has now written a guest post on the use of ‘shall’ in Kevin Lossner’s Translation Tribulations blog, https://www.translationtribulations.com/2021/05/richard-delaney-on-shall.html. Kevin writes that this text was originally part of a social media discussion, but I don’t know where that was and didn’t see it. I am not going to argue point-by-point with Richard’s summary, just set out my own.

I think the mandatory verb in a contract can be shall, will or must. It ought to be used exclusively (some English contracts mix shall and will). I do not think the choice of verb form is likely to confuse any reader. The reader will realize that the verb imposes an obligation.

I posted on this on March 1 2013, since when I have surely changed my mind in some ways.
Shall I or shan’t I? Shall, must and the plain language brigade. The comments are interesting though.

Thornton on legislative drafting is relevant too, although it’s about legislation, not contracts.

  1. I use shall in the imperative or mandatory sense when I translate from the German (as Richard does). I use it even when it is not clear from the German original who the duty is imposed on.

One of the commenters on Kevin’s blog, Stephen Rifkin, writes:


According to the legal experts I have consulted in books and person, “shall” is very simple – legal obligation. A body, personal or legal, can have an obligation. Therefore, it is correct to say: The Tenant shall pay the rent on the 1st of the month but incorrect to say that “The rent shall be paid on the 1st of the month.”

I understand his point, but I would use shall here too, despite the lack of a subject. It does annoy me when German contracts appear to impose duties without indicating who is responsible, but I wonder what the alternative translation would be – varying the verb when the German doesn’t?

One objection to shall I have read recently is that since it is used in a variety of ways, it is more confusing than must for non-native speakers of English who nevertheless have to make do with English translations (rather than Arabic or whatever). That seems possible.

As often mentioned, Bryan Garner is an advocate of avoiding shall altogether (in original English contracts, of course). I think he got this from a movement in Australia and Canada. He lists something like 16 uses of shall, most of them unsatisfactory.

Writers who advocate plain English in law also condemn shall. One argument I’ve read is that if shall is used in different ways within one contract, a court might query whether it has a mandatory meaning at all. I would certain advise against using shall in more than one sense (for example, ‘If the landlord shall…’). Of course, I am not drafting a contract, but always translating a contract where the German version is defined as binding, so I doubt that a messily translated contract would be challenged in court, but you never know.

  1. Instead of shall, will can be used. If either party will do something, this is a promise by a party to the contract that has a binding effect. Some English contracts I have seen use both will and shall, for example, ‘the insurer will’ and ‘the insured shall’. This mixture is likely to confuse readers and so it is better to use either one or the other consistently when translating into English. Geoffrey Leech, see below, calls it a ‘quasi-imperative’.
  2. A third possibility is must. This is perfectly possible and avoids any unclarity. My only objection is that it sounds a bit unnatural to me.
  3. English grammar books not specifically about legal texts: when I first wrote about the use of shall, will and must for legal translation students, I was also teaching English grammar to a wider group. My understanding of English verb forms – tenses and modals – was based on the second edition of Geoffrey Leech’s book ‘Meaning and the English Verb’. I can’t agree with some writers who describe will and shall as ‘simple future’, because both verbs have a variety of uses and there is no simple future.

I will quote the third edition of Leech on will in contracts.

There is a difference between the will of insistence above and a QUASI-IMPERATIVE will found with second- and third-person subects: You will do as I say. The Duty Officer will report for duty at 0700 hours. This will is a stronger equivalent of must, and expre000sses the will of the originator of the message, rather than of the subject. It also differs from the will of insistence in that it is not strongly stressed. The quasi-imperative will seems to be a special use of the future will of ‘prediction’, the implication being that the speaker or writer has so much authority over the addressee that failure to perform the predicted action is out of the question. Hence it has military and despotic associations.

The verbs shall and will can be used to refer to the future but also as modal verbs (there is some overlap between future and modal uses). There is no ‘simple future’. For example, the German ‘morgen fahre ich nach Hause’ is not translated as ‘I will go home tomorrow’, but usually as ‘I am going home tomorrow’. ‘I will go home tomorrow’ might be said at the moment of decision or as a promise. Without going into more detail, in a contract I have always seen ‘The insurer will…reimburse’ as a promise made in a contract and therefore binding. (But Geoffrey Leech calls it ‘quasi-imperative’, see above).
When giving examples of usage, it is a good idea to stick to the affirmative use, excluding negatives and questions, which only confuse the description.

And on shall:
RULES AND REGULATIONS (with second-person or third-person subjects)
A player who bids incorrectly shall forfeit fifty points {rules of a card game. The hood shall be of scarlet cloth, with a silk lining of the colour of the faculty {rules for academic dress}.
This usage is found only in legal or quasi-legal documents. Here shall could be replaced by must (=’obligation’), or by the ‘quasi-imperative’ will.

  1. Use of present tense in German contracts.
    Something Richard Delaney mentioned in the webinar that I have never commented on but that is a constant problem is that the present tense in German contracts is usually used to mean an obligation, but it can also be a statement of fact.

Bryan A. Garner, Garner’s Dictionary of Legal Usage, 3rd ed. 2011

Bankers boxes

Following on from the previous post, it seems that US/UK banker’s boxes are similar to the German ones.

Assembling a bankers box – Youtube video. This isn’t quite the same as the German boxes, but a similar principle.

And Thomson Reuters legal blog has a post Why do they call them Bankers Boxes?

It seems that the inventor, Walter Nickel, sold these boxes to banks to store records. He sold the rights when he was called up for WWI in 1917 (did he survive?). The buyer, Harry Fellowes, named his company the Bankers Box Company. It later became Fellowes.

Legal stationery – the topic that keeps on giving.

Thanks to Tom West.

Removal boxes Germany and England

The German Bücherkarton uses a cunning folding system that holds it together without tape. Are other German removal boxes the same?

The British removal box first has to be taped all round the base, then after it is filled it has to be taped round the top. Query whether the box can be reused after the effort of taping and then cutting open.

LATER NOTE: Tom West tweeted me about the existence of banker’s boxes in the USa – and seemingly in the UK too – see following entry.