Do you speak Japanese?

Reasons for running multilingual websites

As economic globalization has led to a global market, companies need to attract people from all over the world. Finding customers online may sound easy, but it’s not enough to simply offer products and services online. Internationally successful companies need to consider many other facts, too. One of them is communicating with clients in their native language.

If you communicate in your customer’s mother tongue, they will remain on your website for twice as long and are four times more likely to purchase from you!

Of course, millions of websites are in English, and more than 20% of Internet users are English speaking. But the dominance of the English language on the web is ebbing as there are billions of people on earth that speak in a different language.

Top 10 languages

The best way to win your client’s favor is to communicate in their native language. The figure below illustrates the top 10 languages used in the Internet. English (27%) is followed by Chinese (23%) and Spanish (8%) in the list of top 10 languages that most frequently appear online.

Did you know about Japanese?

What may surprise you is that Spanish is followed closely by Japanese: There are nearly one million Japanese-speaking Internet users, which represent 5.0% of all Internet users in the world and 78% of use the Internet.

Talking to Europe

The latest Eurobarometer survey provides another reason to develop multilingual websites: 9 of 10 internet users in the European Union said, that given a choice of languages, they would always visit a website in their own language. Only a third of them is using a foreign language actively, and only 20% of Internet users in the EU would buy products from a website in a foreign language.

Hello World-Hallo Welt-Hola Mundo-Привет мир-你好世界

Billions of people speak thousands of languages, most websites only one or two. Why is that? My guess is that most developers are bilingual, English and some Native Language. But wait, shouldn’t developers building websites and translators/writers deliver the content?

I am programming for about ten years now. Most of the time as a Java developer (server and desktop projects mostly), since 2008 I switched to Ruby/Rails (web projects only). In this time I worked on quite a few projects. Despite their differences, one thing had all in common: doing and maintaining translations was always dirty and chaotic matter. I am sure you experienced some of these situations:

  • The translator edited the resource file in Word with all the fancy formatting.
  • Resource files are exchanged via email. (How would it look to have to have a “pull” and “push” command?)
  • The dialog looks good in English, but in German it sucks. Simply because the same text in German in 30% longer.
  • Missing translations, unused translations.
  • Spelling mistakes, weird texts like “Am I write?” in the application. Not everyone is an English Native (if you haven’t realized it yet, I am not an English native. So please don’t judge my posts by my writing style.), but many think their English rules.
  • And a lot more.

Analyzing these problems, I came to the conclusion that two things have to change:

  1. Translation needs much more integration in the software process. So we can use Rake,CapistranoCI, and so on to get the latest resource files, to push changes to translators, …
  2. I shouldn’t never ever have to explain to a translator/writer what a .yaml file is. Translator should only see a fancy web interface where they can do their job.

So I started to work on a project called “linguist”. The goal is to make linguist the “Github” for translations. I don’t want to give away too many details at this early stage, but I will try to publish updates on this blog regularly.

One more thing, I am looking for help/support. So if you are interested on working on the project write me an email hjuskewycz (a t) hemju.com (paid or voluntary). Of course feedback, ideas, critics are welcome too.