Enrique Zanardi <ezanardi@noah.dfis.ull.es> writes: > > no, please don't create new directories for new languages! The apache > > server is able to give back web pages in the language the browser > > requests. This mechanism is called "content negotiation". We should > > use this mechanism, because it won't break server using other httpds, > > but is very usefull for those who are using apache. Please have a look > > at the apache doc. > I know about Apache's "content negotiation" but, how do we write the > webpages to make it easy for other httpds to provide the translated ones? > We try to be server-independent, don't we? yes, we do ;-) I think that we should provide links that work manually and use "content negotiation" in addition. Example: index.html - englisch index index.de.html - german index Each file reference each other manually: in index.html: <body> ... <a href="index.de.html>deutsch</a> ... </body> and in index.de.html <body> ... <a href="index.html>english</a> ... </body> The automatic one is done via the extra type-map: URI: index.html Content-language: en URI: index.de.html Content-language: de The usage of this file has to be enable explicitly by the web server admin (one for the whole mecanism). Bye Christian -- Christian Leutloff, Aachen, Germany leutloff@sundancer.oche.de http://www.oche.de/~leutloff/ Debian/GNU Linux 1.3.1! Mehr unter http://www.de.debian.org/
Attachment:
pgpFzw9TQwj2e.pgp
Description: PGP signature