On Sat, Sep 10, 2005 at 11:17:37AM -0700, Bryce Harrington wrote:
From the apache documentation, it sounds like the way to handle translations is to have copies of the page in the same directory, but with a language extension (E.g., index.html, index.html.es, etc.) rather than having them in a subdirectory. Personally, I'd think it'd be cleaner to have the translated sites in a separate subdir, but if there's a convention for doing this, we should follow it. An advantage to having the files together is that it would be easier to spot inconsistencies. Anyway, can someone look into how translated files are traditionally stored when using apache, so we can organize the translation efforts accordingly?
The convention is to keep all the files together in the same directory. To make this work, we need to add a section to our .htaccess file that looks like:
AddLanguage en .en AddLanguage fi .fi AddLanguage fr .fr etc
And then cow.txt URLs will map to cow.txt.en, etc.
_however_... we use PHP. So I have no idea how to handle that. :P Maybe we can use the publishing script to do our "includes" for us, and go back to just using straight .html files?