On Sun, Sep 11, 2005 at 12:33:11AM +1000, Peter Moulder wrote:
On Sat, Sep 10, 2005 at 06:46:25AM +0200, Daniel Stiefelmaier wrote:
I talked to bbyak and he told me, to ask here if it is possible to have a localized version of www.inkscape.org, like www.inkscape.org/de/
It would be nice if we let the browser's Language preferences determine the language shown, so that pages appear in the best language automagically. This means that people can use existing URLs, or follow a link from a news article in a different language.
I'm told inkscape.org is using apache 1.3; here are some docs:
http://httpd.apache.org/docs/1.3/content-negotiation.html
(The corresponding 2.0 page is interesting in that it uses content negotiation to choose the language, so
http://httpd.apache.org/docs/2.0/content-negotiation.html
appears in French for me.)
Mmm, I like this idea. A few thoughts though...
Having this be detected by the browser would be advantageous in that the translators would not need to alter any of the links within the site. By and large I've tried to keep all the links relative, so they should "just work" for the most part. Those that aren't relative mostly use the site_root variable so those should also work in theory. However, I think there are still going to be some exceptions here and there.
We don't have access to the Apache config file, except through SourceForge admins. I took a quick look at httpd.conf and it appears that it is configured for doing content negotiation, and mod_negotiation is loaded, although I couldn't verify that this was actually enabled for project web areas. Also, I don't know if sourceforge's apache actually runs off of shell.sf.net or some other machine, so this might not even be the right config file anyway.
I wonder if we may be able to control this through our .htaccess file. Could someone experiment with this? Log into shell.sf.net and see what you can do with this file:
/home/groups/i/in/inkscape/inkscape_web/.htaccess
Initially the translations of the website are not going to be complete, or will not always be in sync. Will it be easy for people to switch back and forth between english and their native language?
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?
Bryce