Category Archives: In English

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.

Invalid Swedish VAT numbers – how to correct them

Posted on by
5

I have recently arranged a job with a client based in Sweden. I asked the client for the company’s VAT number, and he sent me a number with the format SE123456-7890. I tested the number (without the hyphen, since you should always remove hyphens and spaces when entering a VAT number) on the VIES website and was told the number was invalid. The VIES website lists the formats of VAT numbers for each EU member state, and says that Swedish numbers contain 12 digits. Mine, as you can see, only had 10.

Fortunately the Wikipedia’s list of formats gives additional information. It says that all Swedish numbers end in 01, and gives a link to a Swedish website. Although I don’t speak Swedish, I do understand enough words to see that it’s saying that you add 01 to convert a national number to an international VAT number. I tried adding 01 to the number, and sure enough the VIES website gave me the name of my client’s company, thus confirming that I had the correct number.

So, if a Swedish-based client sends you a 10-digit, rather than a 12-digit, VAT number, just add 01 to the end of it.

Anglo Premier Translations provides translation and editing services. For more information, click here to visit our main website.

Share:

How to say “Camp Nou” (and “Salou”)

Posted on by
1

Anglo Premier Translations provides translation and editing services from Catalan, Spanish and French to English. For more information, click here to visit our main website.

When a foreign word is used in the media, journalists are normally advised to pronounce it as closely as possible to the original pronunciation, but using English phonemes. So when Real Madrid is said in the English-speaking media, the word Real (which means royal) is pronounced as two syllables and not like the English word real.

But journalists never seem to have got the hang of the name of FC Barcelona’s stadium. Apart from the fact that the words Camp and Nou are often switched round in the English-speaking media, the word Nou is invariably pronounced noo.

Some journalists realise this is not the correct pronunciation and try to pronounce it the proper way, but end up pronouncing it like the English word now. English speakers often produce the same vowel sound when pronouncing other Catalan words, like the name of the popular beach resort Salou. You even hear the same sound for Catalan words ending in eu, like Bernabeu in the name of Real Madrid’s stadium, probably due to influence from German, in which the eu is pronounced this way.

However, this ow vowel sound would be written au in Catalan, and appears in words like palau (palace).

The correct pronunciation of ou contains English phonemes, but it is the combination of phonemes that feels unnatural to English speakers. To pronounce the word nou properly, first pronounce the short o sound that appears in words like hot or cod. Now pronounce the sound written as oo in English, as in boo and coo. Now pronounce one straight after the other quickly, and you’ve got it!

Since this combination of sounds feels unnatural to English speakers, we could use a compromise pronunciation. But I would suggest the best compromise would be to pronounce the word nou as no, rather than as noo or now.

Finally, in the word Camp, the letter p is silent in the variety of Catalan spoken in Barcelona, although it is pronounced in some other varieties of Catalan.

If you’re still confused, why not listen to a couple of natives pronounce it.

And if you’re still confused, just pretend it says “Cam No”, as that’s a pretty close approximation.

Share:

Anglo Premier now translates LaTeX documents

Posted on by
Reply

In addition to the dozens of formats Anglo Premier already works with, we are now able to translate LaTeX files. We use a special filter that protects the code used in the LaTeX document, which means we can guarantee that we won’t spoil any of the code so that you will be able to compile the final document in the target language. Contact us if you need a LaTeX document translating.

Share:

Termcat databases with 73,016 entries

Posted on by
1

Download 73,016 terminology entries from Termcat’s database for the price of £12 or €14.50.

You can download a free sample of the first 1,000 entries (which covers the entire database on Video games and part of the Telecommunications database) here. Apart from the CSV format for importing into a CAT tool, the sample file also includes a version in Excel format so that if you don’t know how to import a CSV file into Excel you can visualise the data more easily.

On its website, Termcat provides 27 terminology databases in an open, xml format. Although it is an open-source format, the xml format used is not easy to import into a terminology database. Previous posts describe how to use Excel to convert the format, but even using that method is very complicated and takes many hours to do. It also requires Excel 2007, since Excel 2003 and earlier versions does not have enough rows (it is limited to just over 60,000) to enable the method to be used.

The databases contain 73,016 entries. All of the entries contain Catalan, and the vast majority also contain Spanish, English, and to a slightly lesser extent French. Termcat’s XML databases also have some entries in other languages. You can see the domains covered and which languages are covered for each domain here.

Since it is so difficult to import the XML files into computer-assisted translation tools, we at Anglo Premier are offering our converted version – which took us many hours to produce – for the price of just £10 or €12.

Our version contains all the entries available in Catalan, Spanish, English and French. Since the file is aimed at translators rather than terminologists, the data includes only the terms in each language (including all synonyms), as well as the domain (or subject), and the database from which it was extracted. The domain and database names are always in Catalan. They are usually the same, but some databases have various domains, for example, the “Videojocs” database has some records labelled as “Dispositius de joc” and others labelled as “Interacció i comunitat”. I would therefore recommend importing the database name into your CAT tool’s domain/subject field rather than the “domain”.

If you would be interested in having the entries that Termcat has produced in other languages (such as German and Italian) please contact us. If there is sufficient demand we will make a version with the other languages.

Buying the database

To purchase the product, please write to us using the contact form on our main site with your name in the subject line. In the body, please include your name, e-mail address, full address and, if applicable, your VAT number. Please also state your preferred payment method. We accept wire transfer to a British or Spanish account or Paypal or Skrill (formerly Moneybookers). We will reply with the necessary details to make the payment and a reference number for you to use. Once payment has been received you will receive a link to download the full file within 48 hours.

Share:

Conversion of Déjà Vu memories into MemoQ memories

Posted on by
Reply

If you export a Déjà Vu (DVX) memory or terminology database and import it into MemoQ, you lose some of the data such as the client, subject, project, user name and creation date. This is because the tmx format created by DVX does not match the tmx format created and understood by MemoQ. For example, Déjà Vu has separate creation dates and user IDs for the source and target, whereas MemoQ has a single creation date for a translation pair (which makes more sense). Also, the tmx created by DVX contains the subject and client codes, not the actual names. For example, if you used the subject “33 – Economics” in DVX, you will be importing the number “33” as the subject, not the word “Economics”. Similarly, if you used client codes, like “MST” for “Microsoft”, you’ll be importing the code rather than the full name.

Anglo Premier recently migrated from Déjà Vu to MemoQ. After much labour we succesfully converted our translation memories and terminology databases, preserving all the subject and client data and the dates. We initially described the process on this blog, but the procedure is complicated to follow and the script we created won’t run properly on all versions of Windows. It also requires the user to have Excel and Access 2003. Instead, we are offering to convert your translation memories and terminology databases for you. For a fee of €20 or £16.50 we will convert a translation memory or terminology database, and for €40 or £33 we will convert up to four databases. None of the content of your databases will be read and we will delete the databases from our system as soon as the conversion has been done and the file(s) have been sent to you.

If you wish to use this service, please contact us via the contact form on our main website.

Share:

Machine translation and context

Posted on by
Reply

A sentence I’ve just translated is an excellent example of the advantages and disadvantages of machine translation. The original sentence said this:

Los rankings se basan en indicadores sociales y económicos.

Google Translate offered this:

The rankings are based on social and economic indicators.

This is a good example of how machine translation can speed up the translation process. The translation is almost perfect. I say almost, because the translation doesn’t quite work in my context. The reader is left asking “Which rankings?”.

The original sentence is actually talking about rankings in general, rather than any specific rankings. Unfortunately Spanish does not make this distinction in the use of articles, so the word “los” is needed whether talking about rankings in general or specific rankings referred to earlier in the text. Google Translate works sentence by sentence, so it has no way of knowing whether the word “the” should appear at the beginning of the English translation.

Another similar problem comes up when I translate biographical texts. Imagine a sentence in Spanish that says the following:

Nació en Tolosa en 1960, pero desde 1970 vive en Roma.

Is Tolosa referring to the city of Toulouse in the Languedoc region (Tolosa is the traditional Spanish spelling of the city) or the small town in the Basque Country? OK, so I’ve deliberately come up with an ambiguous place name, but the other problem in this example does occur more often: is the text talking about a male or female? Google Translate has no way of knowing, since it only looks at the context of the sentence. It normally chooses a sex seemingly randomly. In this particular example it has produced a translation that does not specified the sex of the person:

Born in Toulouse in 1960, but since 1970 living in Rome.

Although it has avoided assigning a sex to the person the text is talking about, the translation is unacceptable and would need considerable editing. By changing the sentence slightly I can force Google Translate to assign a sex:

Nació en Tolosa en 1960, pero desde 1970 vive con sus padres en Roma.

Born in Toulouse in 1960, but since 1970 living with his parents in Rome.

The pronoun “his” is used, but the person we’re talking about could just as well be female. As additional evidence that Google Translate doesn’t use context I will now ask it to translate the following two sentences together:

Julia es una ilustradora francesa. Nació en Tolosa en 1960, pero desde 1970 vive con sus padres en Roma.

Google Translate provides the following translation:

Julia is a French illustrator. Born in Toulouse in 1960, but since 1970 living with his parents in Rome.

Google Translate still uses the word his, yet to any human translator it is blatantly obvious, thanks to the context of the first sentence, that the correct pronoun is her.

Share:

Running Dragon 11 on 64-bit Windows XP

Posted on by
Reply

Nuance say Dragon is not compatible with 64-bit Windows XP. The installer aborts if you try to install it on this system. But there’s a workaround! Simply follow the instructions found here, but omit the part telling you to change the properties of Audio.exe to run in XP compatibility mode, since you’re already running XP (the blog was written to explain how to run Dragon in 64-bit Vista).

Many thanks to Larry Henry for explaining this workaround.

Share:

Invertext glossaries

Posted on by
Reply

Edit on 29 March 2012

I have looked at this glossary more closely and having seen entries like this I can only conclude that it is not a reliable source.

End of edit

For professional translations, visit www.timtranslates.com.

Today I stumbled across this little beauty of a webpage. It contains a bilingual Spanish<>English glossary with 6,000 definitions in the fields of banking, stock markets, accounting, money and currencies, corporate banking, retail banking and money laundering. I’ve not really tested it yet, but it looks promising.

The glossary is produced by Ediciones Verba, who have produced what looks like a very interesting set of technical dictionaries. I’d be very interested in hearing from anyone who has bought the dictionaries.

I’m a little hesitant about buying them because I wonder whether at some point they’ll put everything online. Also, the dictionaries are not cheap (though given the number of entries, that’s not surprising). I do hope that at some point they will produce digital versions, because that’s what most translators prefer searching in. I’d rather select the terminology I’m looking for and activate a search on my computer or online than get a bulky paper dictionary and look for it manually. In fact, I’d be willing to pay more for an electronic dictionary than for a paper version.

Share: