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:40:04 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <000a01c00ef6$c1be6d00$1000a8c0@example.com>; from ohba@example.com on Sat, Aug 26, 2000 at 09:43:33AM +0900
- References: <39A6B29C.E2C@example.com> <000a01c00ef6$c1be6d00$1000a8c0@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <c3sdrB.A.8PH.WOAq5@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: jq@example.com
Hiroyuki Ohba (ohba@example.com) wrote: Hiroyuki> <meta http-equiv="Content-Type" content="text/html; charset=x-sjis"> ^^^^^^^^ this is evil. charset=s-jis is correct. Start with http://www.w3c.org/ (the World Wide Web Consortium) for more. Those who say it is not an Apache problem are correct. This is either an encoding problem, or a files-mangled-in-upload problem. Also, the most accepted standard for web page encoding is iso-2022-jp. Plus, of course, it's kind of embarrassing to be serving up SJIS from a *NIX box. Jonathan
- Follow-Ups:
- Re: Web pages & Jp. text
- From: "Hiroyuki Ohba" <ohba@example.com>
- References:
- Web pages & Jp. text
- From: David Thompson <davidt@example.com>
- Re: Web pages & Jp. text
- From: "Hiroyuki Ohba" <ohba@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: /dev/null settings
- Next by Date: Re: Web pages & Jp. text
- Prev by thread: Re: Web pages & Jp. text
- Next by thread: Re: Web pages & Jp. text
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links