Yes but there ware sevral replies speaking about HTTP headers (the first one from Juka Korpela). Which are unrelated. This was a necessary clarification. The HTTP protocol itself is not concerned by localisation of the headers related to the management of caches and conditional requests to refresh caches from its source, which may have been modified only because of technical changes (including surrounding decorations, or a reencoding, or some site-global design changes, or local changes of embedded URLs for the same related contents, if they come from other external sources), without affecting the effective contents embedded and published in that page.
As well, there are good reasons why a date displayed in a page could be formatted differently from other dates in the same page, when they are in fact part of different contents each one using its language. Multilingual pages are frequent, and this is why we can tag each part of the displayed content with its language tag, independantly of the default site language, or the user preferred locale parameters. Le 4 avril 2012 20:36, Asmus Freytag <asm...@ix.netcom.com> a écrit : > On 4/3/2012 3:59 PM, Philippe Verdy wrote: > > Yes but HTTP headers are still not part of the page content itself. It > is unrelated and only needed for the HTTP protocol and management of > caches inclding in proxies. Those headers are by definition not > translatable by the server. Only the brower may opt to display these > headers outside of the page content, using the user's preferences in > his browser. > > This is supremely beside the point. > > When data is displayed on a page, the user doesn't (shouldn't) care where it > originates. There should be no difference in formatting between dates that > are manually entered or dates that are dynamically generated. As far as the > user is concerned, both are simply dates. > > (If your page echoes the HTTP header for web developers, that may be a > different issue - here we are talking about pages for end users). > > A./