4 Answers
4

Automatic translation should not be considered as an option. Too much will go wrong. It is possible to automate part of the translation work, of course; translation agencies do it all the time. The crucial question is: how much does it cost to maintain the site in two (or more) languages? If the Spanish version is not maintained synchronously with the English site, it was a mistake to create it. So you need to consider the organizational work and running costs. Plus of course the initial cost.

For a business decision, some estimate is needed about the expected impact of the translated site. How many prospective customers would prefer Spanish to English (when visiting the site) so much that it affects their behavior (willingness to buy, for example)?

I wouldn't recommend any kind of automatic translation, the quality is too bad. Even a cheap human-translation is risky from the UX perspective, if something is not properly translated people are not going to get it.

Many companies use students of non-linguistic courses (whatever they find) to do the translations, getting a very low quality result. Some big websites got translated by their communities but I am not that sure that that always work, I remember reading very weird things on the initial Facebook Spanish translation (I don't know what process they used to improve the quality with the time.)

I developed a bi-lingual, Microsoft Access desktop application where depending on the value of the UI_Language in the app control table, all the screen captions, messages and values selected by the user can be in English or Spanish. All applicable tables have English and Spanish descriptions. Each tables primary key, the ID AUTONUMBER column, is used in the programming logic. so as to not create any dependence on hard-coded values which could be language-specific. Before each form or report is loaded for execution, the language-specific captions are pre-loaded, therefore not requiring two versions for each form. This also makes for easier source code maintenance and modifications.

This only works if there is a direct 1:1 match between English and Spanish content though. What if the Spanish version requires specific pages just for those users, or what about if the structure of forms on the pages is different for each language (For example if Spanish contact details require a 'Region' that the English one does not). If you take this route you're locking yourself into having to have 1:1 matching content for the life of the site.
–
JonW♦Sep 25 '12 at 6:22

My design applies specifically to my target users, Pawnshops. For your app, you could provide a control on each page where users can toggle from one language to another. In my app, if a field in English does not apply in Spanish, I hide that field. I also designed the forms so as to provide sufficient room and sometimes used abbreviations if a caption, description, etc. in one language is longer in another.
–
FrankComputerAtYmailDotComSep 25 '12 at 6:35

If your app is locale-dependent, then that's a separate issue. In my app, I also change date, currency and other GLS environment variables. They key is finding what things are common in both languages, then workout the differences.
–
FrankComputerAtYmailDotComSep 25 '12 at 6:44

I have worked on a lot of very multi-lingual sites (millions of users, etc.), and one thing I can tell you is that supporting the language of a country will drastically improve your traffic from that country. Especially countries that are linguistically isolated like France or Russia or Spain.

If you already have 20% Spanish traffic and you're not offering the site in Spanish, that should jump to the top of your priority list. When you launch the Spanish version you will see those numbers skyrocket. You might be ignoring your next big market if you don't.

Automatic translation is fairly unprofessional quality-wise, but for blogs and stuff you can get away with it you let the user choose. Having a "translate this via Google" button is a possibility.