The Design Superhero

The dirty truth about Infographics! http://awsm.in/u/h7h...

A guide to multilingual blogging

Posted on May 6th, 2010 by Christian Arno | 17 Responses Share

You might be an aspiring blogging superstar or well on course for your 500,000th unique monthly visitor, but the one thing all bloggers have in common is that they are writing for a global audience.

Even if you do only share your unique knowledge and insight with the world in English, the fact is that anyone from Miami to Mozambique can end up perusing your carefully crafted pages…and this is why there is a strong argument for adopting a multilingual blogging strategy.

Of course, if you are just a casual blogger with no intention of making money from your hobby, then you’ll probably get by just fine in English. But if revenue is the name of the game, then it might just be worth your while going down the multilingual route.

75% of the Earth’s population speak no English which is a lot of people for monolingual bloggers to be missing out on. English is the most widely spoken second language, which is why you’ll often see a European blog with a side-by-side translation of the content – the original post in German, French, Italian…whatever the native language is, and one in English. With that in mind, would a similar setup benefit your English-language blog?

Multilingual blogging may sound like a rather daunting prospect at first. If you – like most native English speakers – don’t speak any other languages, then that’s your first problem. If you happen to speak one or two other languages, you probably don’t want to spend all your time translating your posts.

The rise of the machines…

Everyone’s probably copy/pasted a paragraph or two into Google translate at some point, either out of curiosity or because they genuinely want to know what something says on a foreign website. The truth is, Google translate isn’t actually all that bad if you’re not too fussy about grammatical correctness and the nuance of meaning. In other words, Google can get the general gist of a foreign language message fine.

But before you consider using this to translate your precious blog posts, you need to enhance your changes of hitting a good machine translation. And this all begins with how you write your English post in the first place.

Control your language…

Google translate is good, but it can’t decipher slang, colloquialisms or words that have multiple meanings. So rather than ‘going bonkers’, perhaps it’s best ‘going mad’…and you’re best using ‘food’ over ‘chow’ or ‘grub’.

A controlled English language model may restrict your creativity, but it will help to ensure that any subsequent machine translation is accurate.

English often has what is known as an ‘excess of words’ for one concept (e.g. ‘dog’, ‘mutt’, ‘hound’) as well as allowing nouns to be used as verbs (e.g. ‘race’ – ‘to race’ and ‘in a race’).

Through using a controlled language approach, each word can only have one meaning. Once you learn what words Google translate likes and what it doesn’t, you can build a glossary of the best terms to use.

Blogging platforms such as WordPress also have translation plugins available, so that when the plugin is installed, it generates a series of national flag icons which the user can click to automatically translate the content into their desired language.

Humans to the rescue…

If you’re not entirely comfortable with a user-generated translation approach and would rather have the content machine-translated yourself, you can pay for the services of a native-speaking translator who will essentially proofread and edit the text. Given that the machine translation will be reasonably accurate, all the human has to do is check for errors and help avoid any potentially embarrassing lexical slipups. This means you can maintain the creative dexterity of your English blog content.

Doing it this way makes it far cheaper than having a full translation carried out by a professional translator or translation company, though if you’re serious about making inroads into global markets, then full translation could be money well spent.

17 Awesome Responses.

  • @Christian Arno: Through using a controlled language approach, each word can only have one meaning. Once you learn what words Google translate likes and what it doesn’t, you can build a glossary of the best terms to use.

    A controlled language and customised machine translation give good translations. Unfortunately, with Google Translate, your method has some problems.

    Although you use a word with only one meaning, Google Translate does not know your intentions. For example, imagine that your text is about civil engineering. You use the word ‘crane’ to mean a tool for lifting heavy objects. If you write, “the crane is large”, Google Translate cannot know that you mean a tool instead of a bird.

    How do you learn the words that Google Translate ‘likes’?

    Possibly, for translation to some languages, the preferred term gives good translations, but for translations to other languages, the term gives bad translations.

    Although Google Translate is popular, Google Translate is only one of many machine translation tools. Instead of trying to optimise for Google Translate, optimise for all machine translation tools. I recommend that you read ‘The Global English Style Guide’ by Kohl (http://www.globalenglishstyle.com). For my review of Kohl’s book, see http://www.techscribe.co.uk/ta/global-english-style-guide.htm.

  • If you’re not entirely comfortable with a user-generated translation approach and would rather have the content machine-translated yourself, you can pay for the services of a native-speaking translator who will essentially proofread and edit the text. Given that the machine translation will be reasonably accurate, all the human has to do is check for errors and help avoid any potentially embarrassing lexical slipups. This means you can maintain the creative dexterity of your English blog content.
    +1

  • Given that the machine translation will be reasonably accurate, all the human has to do is check for errors and help avoid any potentially embarrassing lexical slipups. This means you can maintain the creative dexterity of your English blog content.
    +1

  • Hi Chris,
    Nice post. But I think it’s also important to think about your audience and what language do they use. I doubt there are large number of visitors to my website that uses a translation service. So I generally disregarded this issue. But still, I could be wrong. Interesting to find out. Thanks!

  • Interesting post but I do not think it works that way. Better stick to the language you know and control, let other people blog in their native language, right? :)

  • Very interesting post my friend. What are your thoughts on using tool bars like wibiya that offer translation of the page into other languages.

    Also for design blogs using pictures or video, perhaps a picture breaks the language bearer?

    75% don’t speak english is astounding to me and made me really think!

    Thanks again for sharing!

    OBI

  • Some really thoughtful stuff. I try to keep language simple on my blogs and avoid phrases and references only a minority would avoid. I find it staggering that 75% of the world’s population speak no english, I thought it would be much less than that!

  • hello Christian Arno, amazing knowledge that you have spread to the world trough this post. I never knew that 75% of the world web users are from on-english countries. I think, I must use some translation script like Google translate to translate content of my blog for other users.

  • Really , all language ? can show chinese ? I think my website can be show ! which is anttask.com

  • Good site! Develop further as :)
    Cool design at a site:)

  • For me Google translator is good enough among any other translation tools .But its not really that accurate ,If you’re badly serious to enter the global marketof blogging I would totally agree to hire for the services of a native-speaking translator.

  • Had never thought of the language scenario, Thanks for share

Leave a Reply

Proudly Powered by HTML5 and CSS

Switch to our mobile site