--- Tom Reed [EMAIL PROTECTED] wrote:
I would think using HTTP_ACCEPT_LANGUAGE to get the users browser
language/country info would be quicker and easier to implement.
This is definitely the best way to get the language. You're right about
that. However, this is not the user's question:
I
--- Filip de Waard [EMAIL PROTECTED] wrote:
Using HTTP headers to identify the country where a visitor comes from
is totally inaccurate.
That's not really very fair to HTTP. There is no header that identifies
the country, so it's not inaccurate - it doesn't exist. :-)
Trying to accurately
On Mar 21, 2004, at 10:38 PM, Chris Shiflett wrote:
--- Filip de Waard [EMAIL PROTECTED] wrote:
Using HTTP headers to identify the country where a visitor comes from
is totally inaccurate.
That's not really very fair to HTTP. There is no header that identifies
the country, so it's not inaccurate -
--- Filip de Waard [EMAIL PROTECTED] wrote:
I posted the HTTP header that my own browser is using to identify
it's language as an example to prove that Accept-Language isn't the
right source to identify the visitors language or even his home
country.
It's definitely not the way to
On 03/20/2004 06:48 PM, Enda Nagle wrote:
I have a site that will have different pricing by world region / country and
also offer different currencies.
Presently, the user has to select their country from a select menu and
submit the form, but I would like to eliminate this step if possible, and
Manuel Lemos wrote:
On 03/20/2004 06:48 PM, Enda Nagle wrote:
I have a site that will have different pricing by world region /
country and
also offer different currencies.
Presently, the user has to select their country from a select menu and
submit the form, but I would like to eliminate this
On Mar 21, 2004, at 1:01 AM, Marek Kilimajer wrote:
Manuel Lemos wrote:
On 03/20/2004 06:48 PM, Enda Nagle wrote:
I have a site that will have different pricing by world region /
country and
also offer different currencies.
Presently, the user has to select their country from a select menu
and
I would think using HTTP_ACCEPT_LANGUAGE to get the users browser
language/country info would be quicker and easier to implement.
Example:
$string = getenv('HTTP_ACCEPT_LANGUAGE');
list($language, $country) = split('[-,]', $string);
-Tom Reed
[EMAIL PROTECTED]
Enda Nagle [EMAIL PROTECTED]
On Mar 21, 2004, at 3:27 AM, Tom Reed wrote:
I would think using HTTP_ACCEPT_LANGUAGE to get the users browser
language/country info would be quicker and easier to implement.
Using HTTP headers to identify the country where a visitor comes from
is totally inaccurate. My browser identifies itself
9 matches
Mail list logo
