Hi,
Recently, I've tried to publish some UTF-8 encoded XHTML documents (containing
text in Devanagari script) on web (not my web server). These webserver, follow
HTTP/1.1 specification, and according to that specification, ISO-8859-1 is the
default content encoding, until unless document
Hi,
Here is the URL of the UTF-8 multilingual doc:
http://unixclan.no-ip.org/~21287/index-utf8.html
Here is the ISO-8859-1'ed doc entitified :-( :
http://unixclan.no-ip.org/~21287/index-utf8.html
Ashish Shukla
--
आशीष शुक्ला alias Wah Java !!
http://wahjava.blogspot.com/
The only key to
--- à¤à¤¶à¥à¤· शà¥à¤à¥à¤²à¤¾ \Wah Java !!\
[EMAIL PROTECTED] wrote:
Hi,
Recently, I've tried to publish some UTF-8 encoded XHTML documents
(containing text in Devanagari script) on web (not my web server).
[...]
Since, I don't have privilege to execute anything on server, I'm
Hi Gora G,
Gora Mohanty wrote:
--- आशीष शà¥à¤•à¥à¤²à¤¾ \Wah Java !!\
[EMAIL PROTECTED] wrote:
Hi,
Recently, I've tried to publish some UTF-8 encoded XHTML documents
(containing text in Devanagari script) on web (not my web server).
[...]
Since, I don't have privilege to
--- à¤à¤¶à¥à¤· शà¥à¤à¥à¤²à¤¾ \Wah Java !!\
[EMAIL PROTECTED] wrote:
[...]
I think this is the problem with HTML specification which says, HTTP
header emitted by server should be given priority in deciding
content-type.
That is probably exactly the problem. When I was faced with this
Hi Gora G,
Gora Mohanty wrote:
That is probably exactly the problem. When I was faced with this issue,
this is what I figured out. However, BOM should work independent of
any HTTP specifications. Maybe I am wrong, but I thought that BOM
should override the HTTP specification. In any case,
