On Tue, February 12, 2008 3:32 pm, Jason Pruim wrote:
>
> On Feb 12, 2008, at 4:24 PM, Daniel Brown wrote:
>
>> On Feb 12, 2008 2:53 PM, Nathan Rixham <[EMAIL PROTECTED]> wrote:
>>> Browsers generally send the the HTTP_ACCEPT_LANGUAGE header in a
>>> request.
>>>
>>> $_SERVER[HTTP_ACCEPT_LANGUAGE]
On Feb 12, 2008, at 4:24 PM, Daniel Brown wrote:
On Feb 12, 2008 2:53 PM, Nathan Rixham <[EMAIL PROTECTED]> wrote:
Browsers generally send the the HTTP_ACCEPT_LANGUAGE header in a
request.
$_SERVER[HTTP_ACCEPT_LANGUAGE] => en-gb,en;q=0.5
thus with mine, preference is en-gb, failing that an
On Feb 12, 2008 2:53 PM, Nathan Rixham <[EMAIL PROTECTED]> wrote:
> Browsers generally send the the HTTP_ACCEPT_LANGUAGE header in a request.
>
> $_SERVER[HTTP_ACCEPT_LANGUAGE] => en-gb,en;q=0.5
>
> thus with mine, preference is en-gb, failing that anything en; failing
> that whatever you've got.
>
> Jason Pruim wrote:
On Feb 12, 2008, at 2:09 PM, Aleksandar Vojnovic wrote:
Could you explain this a little better - "...into using a database[1]
for storing the
pages and using browser sniffing to find out what language preference
they currently had
selected to display in that language"?
Jason,
If you don't mind I may give you an email off the list in a moment to
brain storm up a quick list of questions to ask clients and indeed
client "gotchas".
For the time being as this seems to be going down the line of how to
handle multilingual sites here's my two pennies.
XML, store
On Feb 12, 2008, at 2:09 PM, Aleksandar Vojnovic wrote:
Could you explain this a little better - "...into using a
database[1] for storing the
pages and using browser sniffing to find out what language
preference they currently had
selected to display in that language"?
Aleksandar
I'll t
Could you explain this a little better - "...into using a database[1]
for storing the
pages and using browser sniffing to find out what language preference
they currently had
selected to display in that language"?
Aleksandar
Quoting Jason Pruim <[EMAIL PROTECTED]>:
On Feb 12, 2008, at 1:0
Jason Pruim wrote:
>
> On Feb 12, 2008, at 1:03 PM, Nathan Rixham wrote:
>
>> Jason Pruim wrote:
>>> Hi Everyone,
>>> I know this isn't 100% on topic... But when is any post to this list
>>> 100% on topic? :)
>>> I've been doing some googling trying to find info on how to plan for
>>> what a webs
Jason Pruim <[EMAIL PROTECTED]> wrote:
>
> On Feb 12, 2008, at 1:03 PM, Nathan Rixham wrote:
>
> > Jason Pruim wrote:
> >> Hi Everyone,
> >> I know this isn't 100% on topic... But when is any post to this
> >> list 100% on topic? :)
> >> I've been doing some googling trying to find info
On Feb 12, 2008, at 1:03 PM, Nathan Rixham wrote:
Jason Pruim wrote:
Hi Everyone,
I know this isn't 100% on topic... But when is any post to this
list 100% on topic? :)
I've been doing some googling trying to find info on how to plan
for what a website needs. Stuff like Does it need a foru
Jason Pruim wrote:
Hi Everyone,
I know this isn't 100% on topic... But when is any post to this list
100% on topic? :)
I've been doing some googling trying to find info on how to plan for
what a website needs. Stuff like Does it need a forum, live support,
database driven etc. etc. Does any
11 matches
Mail list logo
