| Re: FILTER_SANITIZE_NUMBER_FLOAT non/sense [message #177034 is a reply to message #177024] |
Fri, 17 February 2012 11:25   |
Captain Paralytic
Messages: 204
Registered: September 2010
Karma:
|
Senior Member |
|
|
On Feb 16, 5:02 pm, "M. Strobel" <sorry_no_mail_h...@nowhere.dee>
wrote:
> Am 16.02.2012 17:32, schrieb Thomas Mlynarczyk:
>
>> Denis McMahon schrieb:
>>> On Thu, 16 Feb 2012 14:22:08 +0100, Thomas Mlynarczyk wrote:
>
>>>> On the other hand I seriously question the concept of a server side
>>>> locale in the context of the world wide web. If locale must be, then it
>>>> ought to be the client's locale.
>
>>> Perhaps, but that just means you should use the client's locale when validating
>>> things like dates and numbers on the server. Of course this assumes you know the
>>> client's locale.
>
>> True. The only reliable way to do this would be to simply ask the client and then
>> maybe store their locale in a cookie. My point was that any "server locale" is
>> completely useless since there is in general no reliable correlation between the
>> server's and the client's location.
>
> ---cut
>
>> Greetings,
>> Thomas
>
> That's a good point, the question about the client side locale seems to be unsolved,
> but not discussed very often. You could use the HTTP Accept-Language header, but I
> did not see it mentioned very often in the web.
How does Language help with Locale?
When I am VPNed into a server that is located in Belgium, Google keeps
asking me if I want to switch the google I am using. I am still in the
UK and I still want English, but the IP address from which my request
is coming is still a Belgium one.
When I am remoted into an actual machine that is in Belgium, the
language of the machine is set to French, but I am in the UK.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]