This is a discussion on Apache 2.0.47 - Content negotiation - Charset problems. within the Windows Web Servers forums, part of the Web Server and Related Forums category; Okay, I'm running two virtual hosted sites, one of which has recently decided to put a Japanese translation of ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Okay, I'm running two virtual hosted sites, one of which has recently
decided to put a Japanese translation of itself up online. My problem is that Apache doesn't serve the file in the requested charset (shift_jis - ISO-2022-JP), it instead returns the file in the default charset (western - ISO-8859-1) and thus this means that the user ends up with binary instead of Japanese displayed to their screen. If the user actively chooses the correct character charset from the view menu, it looks fine, but until then, it displays with the default one. However, this is unacceptable, as as soon as they refresh the page, or click on a link, it reverts to the original character set. The correct meta tags are already in the html, and simply opening the pages from a local drive displays them correctly. I've been looking through the mod_negotiation doco, but when I actually threw up a test site with a var-mapped choice based on the prefered language given by the browser, the same thing happened, even after I specified the charset in the var map. Can anyone point me in the right direction? Cheers, - T. |
| Thread Tools | |
| Display Modes | |
|
|