[nica]

I’m starting work on a web site that will have content in English, Italian and Spanish.
But I’m concerned with the directory structure to separate the content in the 3 languages.

Question: Should it be

name.com/en/
name.com/es/
name.com/it/

or

name.com/eng/
name.com/esp/
name.com/itl/

The separation structure is for language not country. I have the correct Meta Tag for HTLM docs.

<META HTTP-EQUIV="Content-Language" content="EN-US">
<META HTTP-EQUIV="Content-Language" content="ES">
<META HTTP-EQUIV="Content-Language" content="IT">


Any input would be greatly appreciated, thanks

[larkost]

I would actually put everything into one directory, and then use content-negotiation to get the proper content. Somethink like this:


document root:
&nbsp;&nbsp;&nbsp;contentFolder --- whatever you want to call it
&nbsp;&nbsp;&nbsp;en --- this is a folder with a .htaccess over-riding the content negotiation to english and a sym-link to the contentFolder
&nbsp;&nbsp;&nbsp;es --- this is a folder with a .htaccess over-riding the content negotiation to spanish and a sym-link to the contentFolder
&nbsp;&nbsp;&nbsp;it --- this is a folder with a .htaccess over-riding the content negotiation to itlian and a sym-link to the contentFolder

Take a look at apache.org's documentation on content negotiation and then stick to the usual codes. The your file name would look like:

name.en.html
name.it.html

etc... This makes handling multi-language content much more manageable (especially failover).

[nica]

Interesting approach larkost sounds interesting. I’m going to look into it and read more.

Thanks for the link and reply.