Re: localization folder for web site
| From: | Jochem Maas | Date: | Sun, 14 Sep 2008 17:48:07 +0000 |
| Subject: | Re: localization folder for web site | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-280121@lists.php.net to get a copy of this message | ||
Stut schreef:
On 14 Sep 2008, at 17:47, Alain R. wrote:the poor man's equivalent is to set the 404 error handler to /index.php and have it send out a 200 HTTP header if it can actually match the request to some content. ... this is also easily findable on the intertubes.Jochem Maas wrote:You need to find out if your host has mod_rewrite installed and allows it to be overridden in .htaccess. If it can then that's how you can do it. If not then I suggest you find another host because the one you're with clearly doesn't match your requirements. Bottom line is that this really isn't hard. Please Google mod_rewrite to understand what it does and how it works. There is no browser involvement whatsoever.Alain R. schreef:sorry but i miss the point here... if we have http://ww.mywebsite.com/en/index.php, you mean that in fact it can be http://ww.mywebsite.com/index.php?lang=en. but in this case why and how is it possible to see http://ww.mywebsite.com/en/index.php in the adress bar of my browser ? i mean if i do not have access to apache :-)Hi, mostly (90%) websites are designed to include localization (made in php) folder like following: www.mywebsite.com/en/ www.mywebsite.com/de/ www.mywebsite.com/fr/ why do they not use only 1 folder and use dynamically PHP to change localization of website ?who says the 'folders' (directories) en, de, fr et al actually exist?has this something to do with search engine rating ?amongst other things, it's also a way of passing along the requested translation with requiring cookiesthanks a lot, Al.
-Stut