Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: html post method && content-encoding
- To: tlug@example.com
- Subject: Re: html post method && content-encoding
- From: Tobias Diedrich <ranma@example.com>
- Date: Wed, 20 Jun 2001 19:50:29 +0200
- Content-Disposition: inline
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <4.3.2-J.20010621014639.0300aa50@example.com>; from hiyori13@example.com on Thu, Jun 21, 2001 at 01:49:19AM +0900
- Mail-Followup-To: Tobias Diedrich <ranma@example.com>, tlug@example.com
- References: <20010620174645.B22545@example.com> <4.3.2-J.20010621014639.0300aa50@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <0E4svC.A.HIC.4JOM7@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.3.12i
Yamagata Hiroo wrote: > (and of course you'll need auto detection of the input encoding) I think your > only choice would be lv Cool, that seems to be just the thing I need. (^_^) I also looked at the html-specs at w3c.org and there is an accept-charset option for forms, but I tried setting it to "utf-8" and it did not work ^^;; But if lv works well, all is good ^_- -- Tobias nya~ni ?
- Follow-Ups:
- Re: html post method && content-encoding
- From: Tobias Diedrich <ranma@example.com>
- References:
- html post method && content-encoding
- From: Tobias Diedrich <ranma@example.com>
- Re: html post method && content-encoding
- From: Yamagata Hiroo <hiyori13@example.com>
Home | Main Index | Thread Index
- Prev by Date: RE: NIC problem
- Next by Date: Re: html post method && content-encoding
- Prev by thread: Re: html post method && content-encoding
- Next by thread: Re: html post method && content-encoding
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links