As I have said before, I am not really positive against using subdomains, and the portability arguments convinced me that this was a bad idea after all. I would prefer then if the code would only support one way of handling access points (via path and not subdomains). Maintaining both seems to be a bad idea.
This will make the code much easier to maintain, IMHO. I was having problems with detecting which scheme to use. I will work towards paths-only, but will not yet commit.
Also due to the mixed code I was unable to find out whether your solution supports arbitrary entry points like:
http://docweb.example.com/en
http://docweb.example.com/php
http://docweb.example.com/en/php
http://docweb.example.com/php/en
It COULD support this, but does not. Scheme: http://docweb.example.com/project/language/resource
This will also be simpler without the hosts schema.
The general idea was that you can browser projects by language and languages by project. So both directions need to be supported in the URL. Like I am a PHP Documentation editor and I would like to get an overview of the different languages of the PHP Documentation. But one French translator might need an overview of all French projects (ie. he is working on multiple translation projects in peardoc, phpdoc, etc).
Goba