Re: [whatwg] Requiring the Encoding Standard preferred name is too strict for no good reason

2013-08-03 Thread NARUSE, Yui
framework. It needs a new way for example a new meta specifier like META i-want-to-truly-specify-charset-as=Shift_JIS and browser recognize the document's encoding as true Shift_JIS. But such people should use UTF-8 instead of introducing such new one. -- NARUSE, Yui nar...@airemix.jp

Re: [whatwg] API for encoding/decoding ArrayBuffers into text

2012-03-22 Thread NARUSE, Yui
/library/system.text.encoder(v=vs.110).aspx#Y1873 http://msdn.microsoft.com/en-us/library/system.text.Decoder(v=vs.110).aspx#Y1873  enc = new Encoding(gb18030)  bytes1  = enc.getBytes(string1)  string2 = enc.getChars(bytes2) -- NARUSE, Yui  nar...@airemix.jp

Re: [whatwg] API for encoding/decoding ArrayBuffers into text

2012-03-21 Thread NARUSE, Yui
, const char **restrict src, size_t nmc, size_t len, mbstate_t *restrict ps); http://pubs.opengroup.org/onlinepubs/9699919799/functions/mbsrtowcs.html Anyway, they need error if the byte sequence is invalid for the encoding. -- NARUSE, Yui  nar...@airemix.jp

Re: [whatwg] API for encoding/decoding ArrayBuffers into text

2012-03-21 Thread NARUSE, Yui
. And if there are concreate use case, provide streaming API as another one. -- NARUSE, Yui  nar...@airemix.jp

Re: [whatwg] Encodings and the web

2012-01-08 Thread NARUSE, Yui
(2012/01/08 23:32), Anne van Kesteren wrote: On Sun, 08 Jan 2012 01:37:14 +0100, NARUSE, Yui nar...@airemix.jp wrote: = Legacy multi-octet Chinese (traditional) encodings Mozilla supports another Big5 variants, Big5-UAO. http://bugs.ruby-lang.org/issues/1784 As part of the big5 encoding

Re: [whatwg] Encodings and the web

2012-01-08 Thread NARUSE, Yui
Hi, thank you for quick reply, (2012/01/09 0:38), Lin Jen-Shin (godfat) wrote: On Sun, Jan 8, 2012 at 11:20 PM, NARUSE, Yui nar...@airemix.jp wrote: (2012/01/08 23:32), Anne van Kesteren wrote: On Sun, 08 Jan 2012 01:37:14 +0100, NARUSE, Yui nar...@airemix.jp wrote: = Legacy multi-octet

Re: [whatwg] iso-2022-jp and octets over 0x7E

2012-01-08 Thread NARUSE, Yui
(2012/01/09 4:49), Anne van Kesteren wrote: On Sun, 08 Jan 2012 15:32:47 +0100, Anne van Kesteren ann...@opera.com wrote: On Sun, 08 Jan 2012 01:37:14 +0100, NARUSE, Yui nar...@airemix.jp wrote: == iso-2022-jp === The to Unicode algorithm Based on iso-2022-jp state = ASCII state

Re: [whatwg] Encodings and the web

2012-01-07 Thread NARUSE, Yui
. Otherwise, emit the fallback code point. Just FYI, IE and Opera show these bytes as Katakana. If octet is greater than 0xA0 and less than 0xE0, value is octet + 0xFEC0. Moreover IE shows any shift_jis characters here. It seems that IE uses the same converter both iso-2022-jp and shift_jis. -- NARUSE

Re: [whatwg] Default encoding to UTF-8?

2011-12-06 Thread NARUSE, Yui
in HTML. Such verification should be done by developer tools, not production browsers which is widely used by real users. -- NARUSE, Yui nar...@airemix.jp

Re: [whatwg] Question about the application/x-www-form-urlencoded encoding algorithm

2010-03-21 Thread NARUSE, Yui
Hi, (2010/01/21 16:29), NARUSE, Yui wrote: In 4.10.19.4 URL-encoded form data, The application/x-www-form-urlencoded encoding algorithm, it says: For each character in the entry's name and value, apply the following subsubsteps: If the character isn't in the range U+0020, U+002A, U+002D, U

Re: [whatwg] [hybi] US-ASCII vs. ASCII in Web Socket Protocol

2010-01-31 Thread NARUSE, Yui
/iso/catalogue_detail.htm?csnumber=4777 -- NARUSE, Yui nar...@airemix.jp

[whatwg] Question about the application/x-www-form-urlencoded encoding algorithm

2010-01-20 Thread NARUSE, Yui
SIGN character (+). This means, U+9670, encoded as ¥x89¥x41 in Shift_JIS, must be encoded as %89%41, and shouldn't be %89A? thanks, -- NARUSE, Yui nar...@airemix.jp

Re: [whatwg] Superset encodings [Re: ISO-8859-* and the C1 control range]

2009-10-23 Thread NARUSE, Yui
to RFC1345 as described above); This is talking about character encodings, not character sets. JIS_C6226-1983 is a registered character encoding in the IANA registry. Yes, I can understand this, but... On Fri, 23 Oct 2009, NARUSE, Yui wrote: Authors should not use JIS-X-0208 (JIS_C6226-1983

Re: [whatwg] Superset encodings [Re: ISO-8859-* and the C1 control range]

2009-10-22 Thread NARUSE, Yui
-1983, JIS_X0212-1990, and EBCDICs are not ASCII compatible. So they are out of discouraged; mustn't use. Finally, Why ISO 2022 series is discouraged is not clear. Anyway, most of charsets defined RFC 1345 are not clear. Conversion table between Unicode is needed. -- NARUSE, Yui nar...@airemix.jp

Re: [whatwg] Superset encodings [Re: ISO-8859-* and the C1 control range]

2009-10-22 Thread NARUSE, Yui
Øistein E. Andersen wrote: On 22 Oct 2009, at 17:15, NARUSE, Yui wrote: First, JIS-X-0208 and JIS-X-0212 are not in IANA Charsets, I am not sure what you mean; they are both listed at http://www.iana.org/assignments/character-sets: Name: JIS_C6226-1983

Re: [whatwg] Web Address and its escape

2009-09-09 Thread NARUSE, Yui
Anne van Kesteren wrote: On Tue, 08 Sep 2009 21:40:22 +0200, NARUSE, Yui nar...@airemix.jp wrote: First is about 4.10.16.4 URL-encoded form data. http://www.whatwg.org/specs/web-apps/current-work/#application/x-www-form-urlencoded-encoding-algorithm In this algorithm at 6.2.1, SP

[whatwg] Web Address and its escape

2009-09-08 Thread NARUSE, Yui
characters. For example, w is http://www.example.org/D%C3%BCrst, on step 2, w comes to be http://www.example.org/D%25C3%25BCrst. And on step 5, w is broken. Regards. -- NARUSE, Yui nar...@airemix.jp