Welcome / Bienvenue / Benvinguts / Bienvenidos
For information about my translation services, please visit the main site.
Pour des informations sur mes services, merci de regarder le site principal.
Para información sobre mis servicios de traducción, visite el web principal.

How to remove an initial cap from glossary entries

Posted on 19 July 2017 by Timothy Barton

Many online glossaries start every term with a capital letter, such as in this example:

Comptes d’accumulation
Accumulation accounts

Since these terms would only be capped at the start of a sentence, translators ought to import them without the initial caps.

Use the following formula in Excel to remove leading caps. The formula below assumes the first term is in cell E1, but to change it to wherever your first term is, then paste it down all the rows containing terms.

=IF(EXACT(UPPER(MID(E1,2,1)),MID(E1,2,1))=TRUE,E1,LOWER(LEFT(E1,1))&RIGHT(E1,LEN(E1)-1))

Please note that if you don’t use Excel in English, you will need to translate the formula words. Also, if you have your system set to use decimal commas, replace the commas in the formula with semi-colons.

The reason the formula is so long is because it initially checks to see whether the second character is capped. If the second character is also capped, it assumes the term is an acronym, and therefore does not change the first character to lower case.

Configuration de l’orthographe traditionnelle dans Word

Posted on 18 July 2017 by Timothy Barton

Word vous souligne le mot “oignon”, ou il ne vous signale pas que vous avez oublié l’accent circonflexe sur le mot “parait”? C’est parce que par défaut Word utilise l’orthographe réformée de 1990.

Si, comme moi, vous préférez l’orthographe traditionnelle, ou c’est ce que votre client exige, il suffit de changer les options dans Word. Cette vidéo vous expliquera comment le faire.

Una mala traducción comprensible, pero rectificable

Posted on 27 June 2017 by Timothy Barton

El New York Times publicó, hace 4 días, un editorial en el cual instó el gobierno español a buscar una solución política a su conflicto con el gobierno catalán. El último párrafo dice en inglés:

“The best outcome for Spain would be to permit the referendum, and for Catalan voters to reject independence — as voters in Quebec and Scotland have done. Otherwise, Madrid’s intransigence will only inflame Catalan frustrations.”

La primera frase se tradujo o se interpretó erróneamente en varios medios de comunicación (El Periódico, Antena 3, El Confidencial, La Vanguardia, El Economista, ABC), que aseguraron, correctamente, que el editorial instaba al gobierno español a convocar un referéndum, pero que también aseguraron, incorrectamente, que decía que rechazar la independencia sería el mejor resultado para los votantes catalanes.

En realidad, la frase dice que el rechazo de la independencia por parte de los votantes catalanes sería el mejor resultado para el gobierno español; no dice cual sería el mejor resultado para los catalanes.

La mala interpretación de la frase es comprensible. Un lector que no es de habla inglesa fácilmente podría entender que dice “The best outcome…for Catalan voters [would be] to reject independence”, así que no creo que sea una manipulación. Pero pregunta a cualquier persona de lengua materna inglesa – sea a favor o en contra de la independencia de Cataluña – y te explicará que lo que realmente dice el editorial es: “The best outcome for Spain would be…for Catalan voters to reject independence”, es decir “El mejor resultado para España sería…que los votantes catalanes rechazaran la independencia”.

La razón por la cual esta última interpretación es la correcta, y por la cual hay que convertir “for + infinitivo” en “que + subjuntivo” lo explica muy bien Albert Pla en este artículo en Catalán en el diario Ara (ya sé que es un diario catalanista, pero si no te lo crees, puedes preguntar a cualquier persona de lengua materna inglesa).

Y si hubiera alguna duda (que no la hay, pero si la hubiera), esta interpretación la confirma la última frase: “Otherwise, Madrid’s intransigence will only inflame Catalan frustrations”. Aquí, la palabra “otherwise” significa “Si el gobierno no permite un referéndum” no “Si los catalanes no rechazan la independencia”. Si no fuera así, la última parte de la frase – “Madrid’s intransigence will only inflame Catalan frustrations” – no tendría sentido.

Como ya dije, la mala interpretación es comprensible. En cambio, lo que es inadmisible es que los diarios no rectifiquen.

Si yo descubriera que una traducción mía contenía un error grave como este, contactaría a mi cliente de seguida para pedir la rectificación. Los diarios tienen que hacer lo mismo: rectificar las traducciones o interpretaciones erróneas del editorial que todavía tienen publicadas en sus páginas web.

Y para evitar que eso vuelva a pasar en el futuro, podrán consultar a un traductor profesional en caso de duda sobre el sentido de un texto en una lengua extranjera. ¡Estamos a su disposición!

Translator productivity – video 3: Verbatim Google searches

Posted on 19 May 2017 by Timothy Barton

Google used to allow the plus symbol to be used for verbatim searches, forcing Google to search for exactly what we type in, rather than trying to guess what we might mean. When Google introduced Google+, they removed this usage of the plus sign, and informed users that they should use quotation marks instead. Only problem is, as shown in the video, this new method is not reliable.

In the video, I demonstrate how using the plus symbol and the quotation marks don’t work, and show you how to make sure you perform a verbatim search.

Link mentioned in the video for performing verbatim searches: Translator productivity – video 2: https://www.google.com/webhp?tbs=li:1

File to add Google verbatim searches to Intelliwebsearch: IWS Google verbatim.

Translating graph and table labels from Spanish/Catalan to English

Posted on 16 May 2016 by Timothy Barton

It is easy to fall into the trap of using literal translations when labelling graphs and tables, but we should try to look for translations that sound more natural. Here are a few quick thoughts on translating some of the expressions that often come up in Spanish (Catalan) texts:

Illustración/Gráfico (Il·lustració/Gràfic)

Usually followed by a number. These labels usually refer to some kind of graph. I would suggest translating it as Figure.

Evolución de… (Evolució de…)

My current project has the following label for one of the graphs:

Evolució del dèficit d’habitatge a Seül, 1926 – 2009

If the project had been in Spanish it would have read:

Evolución del déficit de vivienda en Seúl, 1926 – 2009

Evolución (Evolució) is always a tricky word to translate. The English cognate, evolution, is not used nearly as frequently as the Spanish (Catalan) word.

In the context of graphs, the Spanish and Catalan words usually refer to the fact that the graph shows information over a period of time. My suggestion here is simply to leave it out in the English, since the date in the label already makes it clear that the data refer to a period of time (if the date range is not in the Spanish or Catalan label or title, we could add it).

So, my translation of the Catalan was as follows:

Housing shortage in Seoul, 1926-2009

Elaboración propia (Elaboració pròpia)

Anyone who translates from Catalan to English will, at some point, have had the headache of having to translate the phrase llengua pròpia. Part of the problem is that in English we can’t normally use the word own next to a noun without an accompanying possessive pronoun such as his or my.

An additional problem with the designation elaboración propia (elaboració pròpia) is that elaboración (elaboració) and elaboration are false cognates. The English word implies adding more detail to something, rather than producing something.

Based on my experience of texts written in English, my suggestion is to translate the phrase as Author’s work, or if the document has more than one author, Authors’ work (NB: make sure you double check whether you need the singular or plural possessive if it comes up as an “exact” match from your translation memory, as your previous project might have had a different number of authors!)

Do you agree with my proposed translations? What other tricky terms do you often see next to tables and graphs?

Don’t overuse connectors when translating into English

Posted on 1 March 2016 by Timothy Barton

One of things that can make an English translation look like an English translation is overuse of connectors, or linking expressions, between sentences. Such expressions are much more common in Romance-language texts than they are in English. Here is an example from a text I was working on this morning, used with the author’s permission.

Hay quien afirma que la traducción automática es simplemente una herramienta más de traducción. Otros, en cambio, defienden que estamos ante un cambio de paradigma en la profesión. En cualquier caso, los defensores de ambas concepciones de la traducción automática la utilizan con reticencias.

I have marked the two connectors in bold. My first draft read as follows:

Some say that machine translation is just another translation tool. Others, meanwhile, argue that it represents a paradigm shift in the profession. However, neither view is expressed without reservations.

When revising my translation, I was uncomfortable with the result, which didn’t seem to flow well. My solution was to remove the adverb “meanwhile”, which is unnecessary in English, since the words “some” and “others” already provide the necessary contrast in English. I also moved the position of “however” away from the beginning of the sentence, which is another useful technique to make English translations sound more authentic.

Macro to replace smart quotes and smart apostrophes with straight quotes and straight apostrophes in Word

Posted on 23 February 2016 by Timothy Barton

UPDATE: I no longer recommend this macro because it does not look at footnotes and text boxes. Instead, you should use the macro available here.

Many users of CAT tools like to convert smart quotes and apostrophes to straight ones before translating their documents, because if the straight versions are always used, it means concordance searches for words including apostrophes will always work.

The problem is that it takes quite a while to do this in MS Word. You can’t just find/replace the apostrophes, because even if you put a straight apostrophe in the replace box, Word will interpret it as a smart apostrophe if you have set Word up to use straight apostrophes and quotes.

Of course, you could change that setting, but then it is more complicated to convert the straight varieties to the smart varieties after exporting from your CAT tool.

The solution is to use a macro that will automatically switch smart quotes and apostrophes off, then perform the search, then switch them back on.

Here’s a macro that will do just that.

Option Explicit Sub ReplaceQuotes() ' ReplaceQuotes Macro, by Timothy Barton, Anglo Premier Translations ' Application.Options.AutoFormatAsYouTypeReplaceQuotes = False Selection.find.ClearFormatting Selection.find.Replacement.ClearFormatting


With Selection.find

.Text = ChrW(8220)

.Replacement.Text = """"
.Forward = True

.Wrap = wdFindContinue

.Format = False

.MatchCase = False

.MatchWholeWord = False

.MatchWildcards = False

.MatchSoundsLike = False

.MatchAllWordForms = False
End With

Selection.find.Execute Replace:=wdReplaceAll
Selection.find.ClearFormatting

Selection.find.Replacement.ClearFormatting

With Selection.find

.Text = ChrW(8221)

.Replacement.Text = """"
End With

Selection.find.Execute Replace:=wdReplaceAll
Selection.find.ClearFormatting

Selection.find.Replacement.ClearFormatting

With Selection.find

.Text = "´"

.Replacement.Text = "'"
.Forward = True

.Wrap = wdFindContinue

.Format = False

.MatchCase = False

.MatchWholeWord = False

.MatchWildcards = False

.MatchSoundsLike = False

.MatchAllWordForms = False
End With

Selection.find.Execute Replace:=wdReplaceAll
Selection.find.ClearFormatting

Selection.find.Replacement.ClearFormatting

With Selection.find

.Text = "‘"

.Replacement.Text = "'"
.Forward = True

.Wrap = wdFindContinue

.Format = False

.MatchCase = False

.MatchWholeWord = False

.MatchWildcards = False

.MatchSoundsLike = False

.MatchAllWordForms = False
End With

Selection.find.Execute Replace:=wdReplaceAll
Selection.find.ClearFormatting

Selection.find.Replacement.ClearFormatting

With Selection.find

.Text = "’"

.Replacement.Text = "'"
.Forward = True

.Wrap = wdFindContinue

.Format = False

.MatchCase = False

.MatchWholeWord = False

.MatchWildcards = False

.MatchSoundsLike = False

.MatchAllWordForms = False

End With

Selection.find.Execute Replace:=wdReplaceAll

Application.Options.AutoFormatAsYouTypeReplaceQuotes = True
Dim oShell As Object

Dim iResponse As Integer

Set oShell = CreateObject("Wscript.Shell")
iResponse = MsgBox("Procedure complete. Code provided by Timothy Barton, Anglo Premier Translations. Would you like to visit the website?", _

vbYesNo, "Procedure complete")
If iResponse = vbYes Then

oShell.Run ("http://www.anglopremier.com?utm_campaign=apostrophesmacro&utm_medium=referral&utm_source=blog")

Else

Exit Sub

End If

End Sub

Automatically move footnotes after punctuation, rather than before, in Word

Posted on 10 October 2014 by Timothy Barton

Texts in Romance languages usually place footnote markers before punctuation. In English we place them after the punctuation. I usually change this on the fly while translating, but I’ve just received a text I outsourced because it was Italian-English and the translator hasn’t moved the footnote markers. No worries! There’s no need to go through the footnotes one by one, as a quick find-and-replace routine in Word will put the footnote markers in the right place (if you prefer, you’ll find a macro at the bottom of the page). Open up the find/replace box, select “Use wildcards”, and enter the following:

Find: (^2)([.,:;\?\!]) Replace: \2\1

It should be safe to use Replace All, but if you want to play safe you can click the Find button once and then keep clicking Replace.

Explanation:
^2 = Footnote reference (same as ^f without wildcards)
[ ] = Look for any character contained in the square brackets. The ? and ! are preceded by a backslash because they normally have special meanings. The backslash tells Word to ignore the special meaning and look for a literal ? or !.
\2 = Replace with the contents of the second parenthesis
\1 = Replace with the contents of the first parenthesis

If you wish to do the opposite conversion, to convert the English format to that used by the Romance languages, run the following procedure, also with wildcards:

Find: ([.,:;\?\!])(^2) Replace: \2\1

If you have to perform either of these regularly you may want to create a macro. Here’s the code for converting to the English format:

Sub MoveFootnotesForEnglish() ' ' Macro by www.anglopremier.com (thanks to Simon Turner for converting to macro format) ' Moves footnote markers to after punctuation Selection.Find.ClearFormatting Selection.Find.Replacement.ClearFormatting With Selection.Find .Text = "(^2)([.,:;\?\!])" .Replacement.Text = "\2\1" .Forward = True .Wrap = wdFindContinue .Format = False .MatchCase = False .MatchWholeWord = False .MatchAllWordForms = False .MatchSoundsLike = False .MatchWildcards = True End With Selection.Find.Execute Replace:=wdReplaceAll End Sub

For those of you working from English to Romance languages, here’s the macro for you:

Sub MoveFootnotesFromEnglish() ' ' Macro by www.anglopremier.com (thanks to Simon Turner for converting to macro format) ' Moves footnote markers to before punctuation Selection.Find.ClearFormatting Selection.Find.Replacement.ClearFormatting With Selection.Find .Text = "([.,:;\?\!])(^2)" .Replacement.Text = "\2\1" .Forward = True .Wrap = wdFindContinue .Format = False .MatchCase = False .MatchWholeWord = False .MatchAllWordForms = False .MatchSoundsLike = False .MatchWildcards = True End With Selection.Find.Execute Replace:=wdReplaceAll End Sub

Bookmarklet tweaks

Posted on 26 January 2014 by Timothy Barton

I’ve corrected some of the bookmarklets I made available on my main website. All the bookmarklets now lead to the correct site, and the Oxford English Dictionary one now works with all words. There is also a link to a site explaining how to disable speed dial in Firefox, since the bookmarklets don’t work if you are on the speed dial page.

Website testing

Posted on 7 December 2013 by Timothy Barton

When translating a website one important aspect translators should include in their budget is website testing. It is the equivalent of reading the proofs of a book before it goes to print. In the publishing industry, translators can spot errors introduced by typesetters who are unfamiliar with conventions in a certain language, such as decimal commas in French, Spanish and other languages vs. decimal points in English.

On a website, clients often overlook menu items when sending website content to the translator for translation. Since the menu items are seemingly simple words, web designers and webmasters may decide to translate the items themselves. Unfortunately things can go wrong, as exemplified below in a screenshot from a website that, otherwise, has a good French translation.

The French word for “French” is “français”, not “française”. The latter is the feminine form of the adjective, as in “une entreprise française” (a French company). When used as a noun to refer to the language it should always be spelt “français”, pronounced with a silent s.

Similar mistakes often encountered on websites, but also on hotels and signposts, include “wellcome” instead of “welcome” and “bienvenu” or “bienvenus” instead of “bienvenue”. In Spanish the word “bienvenido” when used as exclamation agrees with the gender and number of the people being addressed, but in French the exclamation is invariable.

However tempting it may be to translate small words yourself, always check with a professional translator to avoid embarrassing mistakes that spoil your company’s image.

Try to work with a translator who is experienced in translating and localising websites. A good website translator can save you time and money by working with the source code, rather than in a Word document that you then have to reconvert to the format of your website, and will thus ensure that all the menu items and headers and footers are also correctly translated. I would recommend arranging a meeting between the person responsible for the web content, the web designer and the translator to discuss the best strategy.

Anglo Premier blog

Category Archives: Translation & linguistics