W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] Text Encoding used to decode Web Worker's script.

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 19 Mar 2009 16:00:03 -0700
Message-ID: <63df84f0903191600n3a6fd162pea56417696fbe9a0@mail.gmail.com>
On Thu, Mar 19, 2009 at 3:54 PM, Anne van Kesteren <annevk at opera.com> wrote:
> On Thu, 19 Mar 2009 23:49:53 +0100, Jonas Sicking <jonas at sicking.cc> wrote:
>>
>> The problem is if we want to allow people to use already existing
>> scripts then they are likely often not in UTF-8.
>>
>> Most scripts will probably not work out-of-the box anyway since there
>> is no access to DOM. But purely computational libraries should work.
>
> Would such libraries have a lot of non-UTF-8 characters?

It's the web so yes, I would assume there are some amount of non-UTF-8
characters. Hard to say how much of course.

> Also, it's not that
> hard to encode something as UTF-8 these days and the reduced complexity
> would be a nice benefit.

Do such tools always insert a BOM as well? So that it's safe to reuse
the script both for <script> and for workers?

/ Jonas
Received on Thursday, 19 March 2009 16:00:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT