[thelist] Multilingual Sites: Best approach?

Jan Brasna discuss at alphanumeric.cz
Fri Nov 4 14:19:07 CST 2005


Our multilingual web sites have structure like

http://www.example.com/en/
http://www.example.com/en/about-us/
http://www.example.com/en/about-us/contact/

http://www.example.com/es/
http://www.example.com/es/sobre-nosotros/
http://www.example.com/es/sobre-nosotros/contacto/

http://www.example.com/cz/
http://www.example.com/cz/o-nas/
http://www.example.com/cz/o-nas/kontakt/

etc.

or sometimes *.com/pt/* or *.com/fr/* and similar can be replaced by 
entire regional domains (*.pt and *.fr) instead of the "language 
folders" on one server/domain.

If someone enters the root (http://www.example.com/), she is redirected 
by RFC negotiation[2] (beware of issues[3]) to appropriate "language 
folder" by their Accept-Language HTTP header[1].

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4
[2] 
http://pear.php.net/package/HTTP/docs/latest/HTTP/HTTP.html#methodnegotiateLanguage
[3] http://ppewww.ph.gla.ac.uk/~flavell/www/lang-neg.html

-- 
Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com



More information about the thelist mailing list