Doing multiligual sites presumes you can somehow understand what the 
client expects from you. Browsers all are full of language settings, 
but... The HTTP specification is very little language negotiation 
oriented in itself (this is probably a consequence of its having started 
out in a 100% english speaking environment).

I have been checking the docs here and there, but that's the way it is. 
  If russian was my second choice there would be no way to decide 
whether I should be sent a KOI-8 doc or its cp-1251 equivalent. And 
although I am not a chinese speaker I do suspect the same problem to 
arise there. Now I finally understood what was the need for a russian 
edition of Apache.

You can check some docs here: http://www.cs.tut.fi/~jkorpela/http.html 
it's a pretty handy site.

All language negotiation specification ignores the charset issue. It 
appears as if the two things had been projected separetely, by people 
that simply did not know about each other. And since people speaking 
more than one language are a minority I would expect this issue to 
remain "as is" for a century or so...



LoRd, CaN yOu HeAr Me, LiKe I'm HeArInG yOu?
lOrD i'M sHiNiNg...
YoU kNoW I AlMoSt LoSt My MiNd, BuT nOw I'm HoMe AnD fReE
tHe TeSt, YeS iT iS
ThE tEsT, yEs It Is
tHe TeSt, YeS iT iS
ThE tEsT, yEs It Is.......

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to