On Thu, 09 Aug 2012 19:42:07 +0200, Joshua Bell jsb...@chromium.org
wrote:
http://wiki.whatwg.org/wiki/StringEncoding has been updated to restrict
the
supported encodings for encoding to UTF-8, UTF-16 and UTF-16BE.
I'm tempted to take it further to just UTF-8 and see if anyone complains.
I think the main reason would be if there are modern formats which use
UTF16 which we want to allow people to create documents in. I asked on
twitter for such formats and got some responses:
https://twitter.com/SickingJ/status/234060964058763264
/ Jonas
On Tue, Aug 14, 2012 at 7:42 AM, Simon
On Tue, Aug 14, 2012 at 9:42 AM, Simon Pieters sim...@opera.com wrote:
On Thu, 09 Aug 2012 19:42:07 +0200, Joshua Bell jsb...@chromium.org
wrote:
http://wiki.whatwg.org/wiki/**StringEncodinghttp://wiki.whatwg.org/wiki/StringEncodinghas
been updated to restrict the
supported encodings
Sorry if this is a dupe; I replied to this from my phone and an incorrect
address, and my earlier reply isn't showing in the archives.
On Fri, Aug 10, 2012 at 9:16 PM, Jonas Sicking jo...@sicking.cc wrote:
The spec now contains the following text:
NOTE: Because only UTF encodings are
On Thu, Aug 9, 2012 at 10:42 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Aug 8, 2012 at 9:03 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Aug 8, 2012 at 2:48 AM, James Graham jgra...@opera.com wrote:
On 08/07/2012 07:51 PM, Jonas Sicking wrote:
I don't mind supporting
On Thu, Aug 9, 2012 at 10:42 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Aug 8, 2012 at 9:03 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Aug 8, 2012 at 2:48 AM, James Graham jgra...@opera.com wrote:
On 08/07/2012 07:51 PM, Jonas Sicking wrote:
I don't mind supporting
On Wed, Aug 8, 2012 at 9:03 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Aug 8, 2012 at 2:48 AM, James Graham jgra...@opera.com wrote:
On 08/07/2012 07:51 PM, Jonas Sicking wrote:
I don't mind supporting *decoding* from basically any encoding that
Anne's spec enumerates. I don't
On 08/07/2012 07:51 PM, Jonas Sicking wrote:
I don't mind supporting *decoding* from basically any encoding that
Anne's spec enumerates. I don't see a downside with that since I
suspect most implementations will just call into a generic decoding
backend anyway, and so supporting the same set of
On Wed, Aug 8, 2012 at 2:48 AM, James Graham jgra...@opera.com wrote:
On 08/07/2012 07:51 PM, Jonas Sicking wrote:
I don't mind supporting *decoding* from basically any encoding that
Anne's spec enumerates. I don't see a downside with that since I
suspect most implementations will just call
On 8/7/2012 12:39 AM, Jonas Sicking wrote:
Hi All,
I seem to have a recollection that we discussed only allowing encoding
to UTF8 and UTF16LE, UTF16BE. This in order to promote these formats
as well as stay in sync with other APIs like XMLHttpRequest.
However I currently can't find any
On Mon, Aug 6, 2012 at 11:39 PM, Jonas Sicking jo...@sicking.cc wrote:
I seem to have a recollection that we discussed only allowing encoding
to UTF8 and UTF16LE, UTF16BE. This in order to promote these formats
as well as stay in sync with other APIs like XMLHttpRequest.
Not an objection,
On Tue, Aug 7, 2012 at 8:32 AM, Glenn Maynard gl...@zewt.org wrote:
On Mon, Aug 6, 2012 at 11:39 PM, Jonas Sicking jo...@sicking.cc wrote:
I seem to have a recollection that we discussed only allowing encoding
to UTF8 and UTF16LE, UTF16BE. This in order to promote these formats
as well as
On Tue, Aug 7, 2012 at 11:48 AM, Joshua Bell jsb...@chromium.org wrote:
It doesn't appear we reached consensus - there was some desire expressed
to scope to UTF-8, then perhaps expand to include UTF-16, definite
consensus that any encoding supported should be handled by both encode and
On Tue, Aug 7, 2012 at 9:48 AM, Joshua Bell jsb...@chromium.org wrote:
Not an objection, but where does XHR limit sent data to those encodings?
send(FormData) forces UTF-8 (which is even more restrictive);
send(Document) seems to allow any encoding *except* for UTF-16 (presumably
web compat
On Tue, Aug 7, 2012 at 10:47 AM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Aug 7, 2012 at 11:48 AM, Joshua Bell jsb...@chromium.org wrote:
It doesn't appear we reached consensus - there was some desire expressed
to scope to UTF-8, then perhaps expand to include UTF-16, definite consensus
On 8/7/2012 12:48 PM, Joshua Bell wrote:
When Anne's spec appeared I gutted mine and deferred wherever possible
to his. One consequence of that was getting the other encodings for
free as far as the spec writing goes. If we achieve consensus that we
only want to support UTF encodings we can
On Tue, Aug 7, 2012 at 12:55 PM, Jonas Sicking jo...@sicking.cc wrote:
I'm hoping that browsers in general will be able to converge on the
encoding databases that they have. Both as far as which encodings are
supported, and as far as what encoding tables those encodings support.
Anne's spec
Hi All,
I seem to have a recollection that we discussed only allowing encoding
to UTF8 and UTF16LE, UTF16BE. This in order to promote these formats
as well as stay in sync with other APIs like XMLHttpRequest.
However I currently can't find any restrictions on which target
encodings are supported
18 matches
Mail list logo
