[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Registration of new charset CP50220

To: "NARUSE, Yui" <naruse@airemix.jp>
Subject: Re: Registration of new charset CP50220
From: Masatoshi Kimura <VYV03354@nifty.ne.jp>
Date: Thu, 02 Sep 2010 21:19:52 +0900
Authentication-results: mauve.mrochek.com; dkim=pass (1024-bit key)header.i=@nifty.ne.jp; x-dkim-adsp=none
Cc: ietf-charsets <ietf-charsets@iana.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp;s=apr2010msa; t=1283429997; bh=QkJxk2uBz7vuDZaEIg56XFVAjbmT+roEVpovd08S15A=;h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;b=irRGb8TzbF4emyjSTQcQN9i7gPO70kkdqQTCG4ZEODFzhf6+lxT9Ttn51uKOtoY5ID99xBCrEksC6/hSNODBTcykx2HzQU3vTeiss7omi57EYm6KolpAJykoDXXVmtjaTi2FVoqqidid7dZiv64ruUUg9VI2cHBqxtSjmsd+Xps=
In-reply-to: <4C7F92E9.3020705@airemix.jp>
List-Id: <ietf-charsets.mail.apps.ietf.org>
List-Owner: <mailto:ietf-charsets-owner@mail.apps.ietf.org>
List-Subscribe: <mailto:mailserv@mail.apps.ietf.org?subject=subscribe%20ietf-charsets>
List-Unsubscribe: <mailto:mailserv@mail.apps.ietf.org?subject=unsubscribe%20ietf-charsets>
Original-recipient: rfc822;ned+ietf-charsets@mrochek.com
References: <4BCEEECB.80508@airemix.jp> <4C78D1D9.10101@airemix.jp><E14011F8737B524BB564B05FF748464A0F629ECA@TK5EX14MBXC141.redmond.corp.microsoft.com><4C7C399B.5000403@nifty.ne.jp><E14011F8737B524BB564B05FF748464A0F62C675@TK5EX14MBXC141.redmond.corp.microsoft.com><4C7F8DFE.5040903@nifty.ne.jp> <4C7F92E9.3020705@airemix.jp>
Spam-test: False ; 0.7 / 4.5 ; SPF_SOFTFAIL
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; ja; rv:1.8.0.8)Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.0

(2010/09/02 21:04), NARUSE, Yui wrote:
> This refers:
> Mozilla has ISO-2022-JP ESC(I decoder, but when sending JIS X 0201-Katakana
> Mozilla encodes them as Character reference.
No. Old encoder had sent ESC(I. The current encoder converts
hankaku kana to zenkaku kana.

> Only I wanted is decoder,
We also need the encoder. (consider about form submission.)

> so I can change the description like:
>
> * On sending JIS X 0201-Katakana, it MUST be converted to related
> character of JIS X 0208 or escaped characters on the context.
Please do not change. Otherwise Mozilla will have to change the encoder 
again. Moreover, most other browsers (at least IE, Chrome, Safari, and 
Opera for Windows) already convert hankaku to zenkaku on form submission.

-- 
VYV03354@nifty.ne.jp

Follow-Ups:
- Re: Registration of new charset CP50220
  - From: "NARUSE, Yui" <naruse@airemix.jp>

References:
- Registration of new charset CP50220
  - From: NARUSE Yui <naruse@airemix.jp>
- Re: Registration of new charset CP50220
  - From: "NARUSE, Yui" <naruse@airemix.jp>
- RE: Registration of new charset CP50220
  - From: Shawn Steele <Shawn.Steele@microsoft.com>
- Re: Registration of new charset CP50220
  - From: Masatoshi Kimura <VYV03354@nifty.ne.jp>
- RE: Registration of new charset CP50220
  - From: Shawn Steele <Shawn.Steele@microsoft.com>
- Re: Registration of new charset CP50220
  - From: Masatoshi Kimura <VYV03354@nifty.ne.jp>
- Re: Registration of new charset CP50220
  - From: "NARUSE, Yui" <naruse@airemix.jp>

Prev by Date: Re: Registration of new charset CP50220
Next by Date: Re: Registration of new charset CP50220
Prev by thread: Re: Registration of new charset CP50220
Next by thread: Re: Registration of new charset CP50220
Index(es):
- Date
- Thread