Multi language website, how to approach this?

Question

I have a website (Coldfusion) on which I want to offer multi language, but no idea what is the best way to do this.

There 2 plans I have:

1:

Of course all content (text) is in a database.

If a user would want a different language, the user would click on a link/flag, this would put the requested language in a session variable, for example: session.language = "es"

In the database I would have 2 columns (every language has 1 column) and then select the text which belongs to 'es'

Every page would then do a request to the database to get the text beloging to the session.language.

PROS: Relatively simple to implement

CONS: SEO wise I don't think this could be very good. http:// www.domain.com/page.cfm would give an english text or spanish text (or other language). Google will not add duplicate URL's

2:

Do something with http:// www.domain.com/en/page.cfm for english and http:// www.domain.com/es/page.cfm for english.

With a URL rewrite rule the language value in the URL http:// www.domain.com/en/page.cfm would actually be a page http:// www.domain.com/page.cfm?language=en

The url.language variable will then select the correct language from the database.

PROS: Unique URL for each language. Good for SEO and Google indexing.

CONS: A bit more difficult to implement. (I think)

Or does anyone have other / better ideas?

Thanks!!

Answer 1

The best way i found is to use an XML to hold just that pages language stuff, one xml to cover each page, and you then vary it for language. when the page loads, just load a different XML from the database or files... many ways to do this. all other methods i have tried have their issues, and at least this one allows you to take a language XML, hand it to someone who will copy it, and then change the boxes... you put it in the DB to serve it.

one can also do this for text, and have the DB make the XML for just the text for that page by using a list of items to include in the XML for the page.

once you get the idea, the rest becomes very easy... and given CF ways of accessing such data with dot notation, easy peasy to us

say you have "Load Images"

in english xml it may be <LoadIMGS>Load Images</LoadIMGS> 
in chinese it may be <LoadIMGS>加载图像</LoadIMGS>
or <LoadIMGS>Jiā zǎi túxiàng</LoadIMGS>

regardless, in your CFM code you would just put #variablename.LoadIMGS# in the place... i would also suggest putting in the loadimages tag the size the font should be adjusted to if not normal size. that way, when translations are too large, you can shrink that font there for that... etc.

enjoy!!!

Answer 2

http://i18n.riaforge.org/ has a download for i18n. It can be used to make sure that all string labels match. That way if some one wants to change "Save" to "Update", it can all be done in one spot.

It is also important to consider the technical background of those that will being doing the translation. It is often easier to get the translation team to edit files in notepad as opposed to updating a db. Text files work well with version control.

Answer 3

To effectively do a multi-lingual site then you need set a rule for yourself that NO TEXT is ever put in the source as hard coded. It either needs to come from the database and / or a Resource Bundle.

Text from the database

You need to make sure that the column you are storing your data in is unicode otherwise you'll have issues with accented character. Also don't have a column per language as this is not scalable, do what @jan suggests and have a translations table where the items are keyed on a reference as well as a language.

Resource bundles

You are not going to want to get every last little bit of text from the database so for those you can utilise a resource bundle. This is an, admittedly old, link http://www.sustainablegis.com/blog/cfg11n/index.cfm?mode=entry&entry=FD48909C-50FC-543B-1FE177C1B97E8CC1 from Paul Hastings's blog about some solutions to resource bundles. To be honest his blog is an excellent resource on this very subject.

With regards to how you handle the URLs do not do option 1 as you quite rightly identified you will cause issues the SEO rankings of the page and it will mean that users cannot correctly share or return to the page.

Two approaches are having the language code in the URL as you identified in option 1.

Pros

• Simpler to configure

Cons

• You have one application which means that as you add more languages you add more complexity and weight on the memory of that app

Or you can have a different sub domain or domain per application e.g. es.yourdomain.com or yourdomain.es they can all be the same codebase

Pros

• Each language is a standalone application meaning it has it's own memory

Cons

• more effort to configure

Answer 4

I would go for option 2. Every translation should have its own url. Links to your website will already be in the intended translation.

To store translations in a database, I wouldn't put every translation in a seperate column, but rather put them in a seperate table:

Table Posts:
- id
- title_id
- ...

Table Translations:
- label_id
- value
- country_code
- language_code

Where title_id matches label_id

This way you won't have to alter your table structure when a new translation is added. This allows you to have infinite translations for any label or text.

Answer 5

You should always first check the browser header "Accept-Language" for the default language(s) (the correct standard way to do it), and offer links (the intuitively seemingly right way) only as an alternative.

Doing it in a database doesn't seem very standard. Let's assume you would like to use MVC architecture (model-view-controller). Most software uses keys in the presentation layer (view) (eg. html) and along with the presentation layer, you have language files (in Java, this is typically properties files) which are mapped simply by their filenames, and can be modified by regular users, without any special skills, such as professional translators with no computer skills. Certainly you could put it in a database, but then it is just more work, and moves the information out of the presentation layer.

There are various libraries for doing this. You should find the normal one for your application. Please edit your question to include what you are using to develop the application. (eg. JSP, Tapestry, Wicket, ASP, PHP, etc.) So for example, if you wanted to use JSPs, I would then suggest you use the JSTL tag library's language support. Or if you were using Tapestry, I would point you to http://tapestry.apache.org/localization.html or http://tapestry.apache.org/tapestry4.1/UsersGuide/localization.html

To look it up, you can look for the terms "internationalization" aka "i18n", or "localization". (The terms don't mean the same thing, but few use them correctly, so either works. http://www.w3.org/International/questions/qa-i18n)