manldapEasyInterface - Cookbook: recipe #111, Providing an internationalized...

 
 
Show feedback again

recipe #111, Projects Homepage: Providing an internationalized homepage

(We assume that you already used your homepage area, managed via CVS, that everything worked well. If it is not the case, please read the related recipes first)

The homepage server is configured to use content negotiation, something pretty standard with apache nowadays.

To add a translation, you just have to add a file called like $filename.$lang.html. For instance, the German translation of the index file would be named index.de.html. When a German user will browse your index page, when asking for /index, the apache server will return him the German page, index.de.html.

It means that you should advertise pages with .lang.html only if you want to point to a specific translation, and advertise pages like /blabla (for blabla.$lang.html) the rest of the time.

http://www.debian.org/ is an example of content negotiation usage for internationalization: all the internal links are like /social_contract, always redirecting you to the translated file. But you can access translated versions with direct pointers like /social_contract.es.html (Spanish) and /social_contract.de.html (German).

Apart from that, we advise you to take care of outdated translations. You can can use the CVS tags like $Date: $ or $Id: $ to print inside your pages version information, in a warning to users.

Last update: Tue 31 Oct 2006 05:05:06 PM UTC
This recipe comes from Gna! User Docs

 

 

 

 

 

Audience and Context

Audience:
   All Project Members
Feature:
   Project Homepage

(As there is at least one of the Audience/Feature/Action context information not set, this recipe will not show up in related recipes links)

Show feedback again

Back to the top


Powered by Savane 3.1-cleanup