W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2014

I18N-ISSUE-375 (BUG26256): API: TextEncoder encode()'s 'stream' option appears useless [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 10 Jul 2014 04:10:37 +0000
Message-Id: <E1X55gr-00018d-RW@stuart.w3.org>
To: public-i18n-core@w3.org
I18N-ISSUE-375 (BUG26256): API: TextEncoder encode()'s 'stream' option appears useless [encoding]

http://www.w3.org/International/track/issues/375

Raised by: Addison Phillips
On product: encoding

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26256

This issue tracks the bug listed above and was created as part of the WG LC process. The bug was created prior to the WG LC.

---

Given that:

(a) the input to encode() is defined as a ScalarValueString (i.e. no incomplete surrogate pairs), and 

(b) encode() only supports UTF-8/UTF-16, which do not maintain any encoder state across input tokens

...then it does not appear that the 'stream' option has any meaningful behavior for encode().

Am I missing something?
Received on Thursday, 10 July 2014 04:10:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:09 UTC