Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Web pages & Jp. text
- To: tlug@example.com
- Subject: Re: Web pages & Jp. text
- From: Jonathan Q <jq@example.com>
- Date: Sun, 27 Aug 2000 02:43:35 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <39A72389.D9F@example.com>; from davidt@example.com on Sat, Aug 26, 2000 at 11:55:22AM +1000
- References: <39A72389.D9F@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <bno7eB.A.ARH.fOAq5@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: jq@example.com
David Thompson (davidt@example.com) wrote: David> they handled the HTML code. I've tried a number of metatags such as: David> David> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=x-sjis"> David> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=EUC-JP"> David> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; David> CHARSET=iso-2022-jp"> OK, which of those actually matches the encoding you are using? Running every page through NKF and setting them all to the same encoding (if you've eliminated FTP problems; it won't fix corrupted files) is also advisable in a situation like this. I hate to ask this, but the encoding in the browser is set for Japanese auto-detect, right? Jonathan
- References:
- Re: Web pages & Jp. text
- From: David Thompson <davidt@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Web pages & Jp. text
- Next by Date: Re: Web pages & Jp. text
- Prev by thread: Re: Web pages & Jp. text
- Next by thread: Parallel port query
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links