The reason I'm asking is that my company is considering adding more languages to our site, all manually content, where I would suggest just using Google Translate for those occasional users that requiere this. Most people in my country (Denmark) speak and read English just fine.
For SEO purposes, you need to add additional languages
For example, if you want to rank on keywords that are not in English, you will need content in order to get a high postion on search results
Yes. Please poll people who will never use your site.
Because doing proper user testing and actually communicating with people who do use the site is against internet law. ...Besides, talking with your customer/user is just plain creepy.
Seriously, your audience doesn't read English at the same level. Most read at a more advanced level in a native language. What's more, reading brute force translated English is awkward and at times annoying -- a usability flaw.
It's an intoxicating idea to point to the few people who can circumnavigate a site's mystery meat navigation and say everyone can. Just the same with text: Just because most can read English doesn't mean they prefer to or find it easier to.
Or is this the "what can we get away with" game? Because a great many like to play that game with customers.
Is brute force translated text obsolete? Possibly. It would be a refreshing change to go from word-for-word translation to localization: Literally re-writing and article for a foreign locale using a foreign perspective.
It really depends. I think English has become the universal language of the internet and pretty much every site is in English and maybe the language of origin. For example I have had clients with websites in other countries. When I go to their site in order to find information for the articles requested, I will notice they have the English version and the local language version. Anything more than that can be a lot of work and perhaps even counterproductive.
I would simply say to keep it simple and a maximum of two languages! Hey, that is just my opinion!
There are billions of people out there who don't speak a word of English, so it all depends if you want to communicate with them or not. Most software developers speak some level of English (at least so they can read the docs), but your average user might not.
The cost benefit is going to come into it. 37signals just announced the other day that they've added a lot (6 I believe) of new languages to the Basecamp interface.
If 95% of your audience are fluent in English it's probably not worth the expense of localising. It may be best to poll them to get an idea of how helpful native language content would be (no difference, a bit better, much better, critical) and use that to guide your decision.
Like other have said, it depends on who your visitors are and what global markets your company is in.
Since you are based in Denmark, would it be beneficial for the site to be in Danish? Note that it does take a fair amount of overhead to maintain what would essentially be the content of separate sites.
From my experience most people prefer to read content in their native language.
If we are talking about a Danish company which deals with people from Denmark then if you would have just one language that should be Danish, not English.
Additional languages for content could need a lot of additional resources to maintain (depending on the amount of content you produce), but if you are going to have a multi-language site then make sure you do it right. Do not use auto-translators and make sure all content is provided in both languages. Otherwise do not bother. Auto-translators and partially translated sites could do more harm than good. If your users want to use an auto-translator they can do it themselves.
We offer a couple of forums for users of other languages and have had limited success. Overall I would say it was worth it to us, but google translate is getter better and better, and if I had to guess I would say the adoption rate of google translate has increased in the last year.
I've had some exposure to Spanish and French and used to think I was fairly aware. I've since learned that I was very American-English centered in my thinking. My awakening? I decided to I18n L10n my WordPress plugins. So far I've gotten translations in
More than enough to realize that Google translate and Babelfish can't yet replace a person for doing translations 100% correctly. What they miss is assessing the context and the mood of the content. They "best guess". They're close enough so it could pass in a pinch I guess. But if you want a really professional reading site, IMHO it's best to have someone fluent in the language do the translations. You don't want to risk a faux paus. For example in American English "poof" is a neutral word. In Australian English it isn't.
At work we've built up a language dicitonary which contains words and phrases.
When we develop a new part of the system we can add new items in English with a simple API like Translate("LANGUAGE_KEY") and then later on down the track when we need support for a language we(or the client) can hire a translator to populate a column for a specific language.
And it just works.
It's great to do the work up front on a framework - then you dont have to think about language until its required.
Yes, I guess that's about how gettext works in WordPress. Each "phrase" is mapped to a translation file. Then depending on which language is opted for, the app replaces the English with that language.
No duplication of code, only the text.
We have a site which has this tagline:
huur een vakantiewoning, verhuur een vakantiewoning
I really can't find a decent way to say that in American English. For British English, we're using Hire a holiday home, Let a holiday home.
However in American English and in Spanish, there really isn't a good one-word way to say "rent" and "rent out". So there's no American English version (which is good because Hire and Let mean very different things in US English!... Let a holiday home do what?) and the Spanish version just repeats itself:
Alquile una casa de vacaciones... alquile una casa de vacaciones
which sounds really, really, really retarded. Though way back when I could speak Spanish, I don't think I ever heard anyone say they were a landlord, I only heard alquilar used by renters. Still, this is something a transation service, supposedly by human beings, did. Either they didn't realise how strange it is, or they simply couldn't find a good way to do it.
Now imagine a robot like Google doing that. Disaster x a bazillion.
Guess what google translate called "bicycle" when it encountered our Dutch site with the word "rijwiel" (another term for bike instead of the somewhat more popular "fiets")? It called it a pennyfarthing!
I thought that was a type of money, so I had to look it up. A pennyfarthing is one of those old-fashioned Victorian bicycles with the giant front wheel. I've seen them in parades and circuses, but we sure as hell don't have those things running loose in the streets!
Get humans to translate if you need more than a sentence in another language of regular content.
There should either be a human translation, or no translation at all. The result of a Google Translate translation can be painful to read.
Also, you can't count on Danes being able to read and understand English. In my experience, the majority of Danes above the age of 25 are not comfortable speaking, reading or writing English, and many will avoid doing so altogether if they can at all help it.
I'm noticing an increasing trend in Asian sites offering content in multiple languages. Mainly because the brand/company is trying to branch out into other Asian countries, and usually English speaking countries as well. I personally think it is very convenient. It also gives the impression that the translation you are getting is accurate since they (hopefully) care enough to hire a real translator rather than use an automated service like Google Translate.
Along with adding multiple languages, the content is sometimes cherry picked for the foreign language versions. On the one hand nice because you get tailored content that is significant for your region (based on language), but on the other hand you aren't getting all the info that you could if you were able to read the site's primary language. I guess it will always be a compromise.
All I have to say is that the few times I've used online translators I've been able to pick out the bits and pieces of information I needed, but I'm sure I wasn't getting the message as the author intended. Slang, proverbs, etc don't seem to translate well.
Online translators like google translator works just fine, a site with multi language support always increases site traffic and there is a popularity of website content.
It's funny I found this thread. I was about to post the same question.
Though most of our site visitors are English based (us-en, gb-en) I was going through our Google Analytics when i found that we also get quit a lot of German (de) and French (fr) visitors as well. In normally don't go though Google analytics with so much detail but we are developing a new site design to communicate simplicity and our Global presence.
BTW, our business is not design based but global investments and finance.
So, thank you guys for the thread and answers! Decided to create a multilingual website that will communicate with English, German, and French visitors. So, thats answered but I have another question. I also noticed a 30% of our traffic is from iPhone users. Should we also develop an iPhone based web version or continue with our current mobile HTML version? I guess I'll start another thread for that one.
Online translators like google translator works just fine
No offence but, no they don't. Even for translations between common languages, like German and English, the translations are absolutely rubbish. They can be used to get an idea about what the page is about (most of the time), but they are not a viable replacement for a trained translator. A site which use machine-translated text will look very unprofessional.
I agree. They don't do too bad, but the best is still what I would call "broken English". Enough so you can figure it out, but it doesn't read smoothly.
For example, I have this line in one of my plugins:
"The following options were not paired correctly. Be certain to check their information carefully before you remove them."
The (human) Dutch translator gave me this for it
"De volgende opties werden niet correct gekoppeld. Wees er zeker van de informatie zorgvuldig te controleren voordat u deze verwijderd."
And Google translate gives me this English for that Dutch
"The following options were not properly linked. Be sure to check the information carefully before you removed."
True, I don't know Dutch so maybe the translator did wrong, but I'm betting the Dutch more approximates the original English than it does the Google English.
And I have no idea how good this Google Dutch is for the original English
"De volgende mogelijkheden werden niet goed gekoppeld. Wees er zeker van om hun informatie te controleren en zorgvuldig door voordat u ze verwijdert."
But it gives me this Google English for the Google Dutch
"The following options were not properly linked. Be sure to check their information and carefully before you remove them."
Which is NOT what it started with. So something definately got a bit mangled somewhere.