Nope...
Zend_Locale has to handle localization and normalization... and not setting
responses or views.
Setting a response for a view or request has nothing to do with
localization.
Greetings
Thomas
I18N Team Leader
----- Original Message -----
From: "Kevin McArthur" <[EMAIL PROTECTED]>
To: "Gavin Vess" <[EMAIL PROTECTED]>; <[email protected]>
Sent: Thursday, March 01, 2007 10:01 PM
Subject: Re: [fw-general] Internationalization and the Zend Framework
Very cool; maybe a method for Zend_Locale to integrate into Zend_Response?
->setVariedResponse() or a better name?
Kevin
----- Original Message -----
From: "Gavin Vess" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, March 01, 2007 1:51 PM
Subject: Re: [fw-general] Internationalization and the Zend Framework
Perhaps some will find it valuable to elaborate a little more about the
issues of serving different content at the same URL based on the value of
the HTTP "accept-language" request header.
How many crawlers crawl the same URLs multiple times, once for every
language they want to "find" at the URL by setting the value of the
"Accept-Language" HTTP request header to each language in turn?
When viewing search results, how many search engines show multiple
versions of a web page for the same URL, with each "version" in one of
the languages supported by that website? The search engine might make
educated guesses about the language preference of the user searching, or
it might not.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html - HTTP 1.1 and the
"Vary" header
When varying content based on the request field "accept-language", make
sure to use the "vary" HTTP header in the response:
Vary: Accept-Language
This is quite important to prevent other issues with caching proxy
servers (e.g. the multitudes using AOL and similar setups):
http://webmaster.info.aol.com/vary.html - AOL's instructions
Cheers,
Gavin
