<h1>Italian Version</h1>
and edit the English version so that it includes a new line:
<h1>English Version</h1>
Then we give each file an appropriate extension:
Apache recognizes language variants: en-US is
seen as a version of general English, en, which
seems reasonable. You can also offer documents that serve more than
one language. If you had a "franglais" version, you could
serve it to both English speakers and Francophones by naming it
frangdoc.en.fr. Of course, in real life you
would have to go to substantially more trouble, what with translators
and special keyboards and all. Also, the Italian version of the index
would need to point to Italian versions of the catalogs. But in the
fantasy world of Butterthlies, Inc., it's all so simple.
The Italian version of our index would be
index.html.it. This is true of files in general,
but it's necessary to be aware of some index subtleties. By
default, Apache looks for a file called
index.html.<something>. If it has a
language extension, like index.html.it, it will
find the index file, happily add the language extension, and then
serve up what the browser prefers. If, however, you call the index
file index.it.html, Apache will still look for,
and fail to find, index.html.<something>.
If index.html.en is present, that
will be served up. If index.en.html is there,
then Apache gives up and serves up a list of all the files. The moral
is, if you want to deal with index filenames in either
order -- index.it.html alongside
index.html.en -- you need the directive:
DirectoryIndex index
to make Apache look for a file called
index.<something> rather than the default
index.html.<something>.
Anyway, to give Apache the idea, we have to have the corresponding
lines in the httpd.conf file:
AddLanguage it .it
AddLanguage en .en
AddLanguage ko .ko