Re: [tlug] html editor :) IBM Homepage Builder

[Tod McQuillin <devin@example.com>]

On Fri, 31 May 2002, Jim Breen wrote:

> >> I changed the charset value to shift-jis instead of shift_jis and now it
> >> displays correctly in my browser.
>
> Possibly only because "shift-jis" is not recognized, so once you put that, the
> autodetect cut in.
>
> PS, the standard is "Shift_JIS" AFAIK.

Hm, interesting  --

I loaded the html source into emacs and it recognised the japanese
characters.  M-x describe-current-coding-system says:

Coding system for saving this buffer:
  S -- japanese-shift-jis-dos

But I think you are right about Shift_JIS being the standard name.

OK, I have looked into it some more.

When I load the page in mozilla, from
http://ww6.tiki.ne.jp/~mecooper/index.ja.jis.html, the "Page Info" window
says Encoding: ISO-2022-JP, and the page is displayed as mojibake.

When I save it to a file and read it again, it displays ok (regardless of
the charset setting ih the meta tag).

But this is perhaps what's really going on:

% telnet ww6.tiki.ne.jp 80
Trying 202.214.149.69...
Connected to mx6.tiki.ne.jp.
Escape character is '^]'.
HEAD /%7Emecooper/index.ja.jis.html HTTP/1.0

HTTP/1.1 200 OK
Date: Fri, 31 May 2002 12:26:09 GMT
Server: Apache
Last-Modified: Thu, 30 May 2002 03:14:30 GMT
ETag: "155d7-b14-3cf59916"
Accept-Ranges: bytes
Content-Length: 2836
Connection: close
Content-Type: text/html; charset=iso-2022-jp
Content-Language: ja


The httpd gives an http header of
"Content-Type: text/html; charset=iso-2022-jp"

Maybe that overrides the meta http-equiv.

If so perhaps the only recourse is to write the document in iso-2022-jp.

-- 
Tod McQuillin