Mailing List Archive
Support 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: Yamagata Hiroo <hiyori13@example.com>
- Date: Thu, 21 Jun 2001 01:49:19 +0900
- Content-Type: text/plain; charset="us-ascii"; format=flowed
- In-Reply-To: <20010620174645.B22545@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <gcIFZB.A.j7B.yJNM7@example.com>
- Resent-Sender: tlug-request@example.com
At 17:46 01/06/20 +0200, you wrote: >The real problem is posting messages. >I could not find a way to determine which encoding the browser is using >in the posted form data. The usual trick is to pipe the input through a filter. If you want to use utf-8, (and of course you'll need auto detection of the input encoding) I think your only choice would be lv http://www.ff.iij4u.or.jp/~nrt/lv/ I hope this helps.
- Follow-Ups:
- Re: html post method && content-encoding
- From: Tobias Diedrich <ranma@example.com>
- Re: html post method && content-encoding
- References:
- html post method && content-encoding
- From: Tobias Diedrich <ranma@example.com>
- html post method && content-encoding
- Prev by Date: html post method && content-encoding
- Next by Date: RE: Problems with tlug list
- Prev by thread: 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 |