Re: Encode and Decode UTF8

2016-07-02 Thread Harbs
Yes. It is. I’m going to change it. On Jul 3, 2016, at 8:29 AM, Alex Harui wrote: > > > On 7/2/16, 12:22 PM, "Harbs" wrote: > >> Thanks. The GC implementation is nice and simple. >> >> One question (I think for Peter): >> >> BinaryData is using Int8Array for the view. is there a reason th

Re: Encode and Decode UTF8

2016-07-02 Thread Alex Harui
On 7/2/16, 12:22 PM, "Harbs" wrote: >Thanks. The GC implementation is nice and simple. > >One question (I think for Peter): > >BinaryData is using Int8Array for the view. is there a reason that it’s >not using Uint8Array? I think it should probably use Uint8Array if it is available everywhere.

Re: Encode and Decode UTF8

2016-07-02 Thread Harbs
Thanks. The GC implementation is nice and simple. One question (I think for Peter): BinaryData is using Int8Array for the view. is there a reason that it’s not using Uint8Array? Harbs On Jul 1, 2016, at 8:15 PM, Alex Harui wrote: > Actually, I saw note saying that Google Closure Library has

Re: Encode and Decode UTF8

2016-07-01 Thread Justin Mclean
HI, > Thanks for the links. I looks like the unlicensed license is a derivative of > the CC0 license, so if I’m reading it right, it’s binding and about as > permissive as you can get. It looks that way but it best to get it added to the list. > What would we add to where? If we need to add so

Re: Encode and Decode UTF8

2016-07-01 Thread Alex Harui
Actually, I saw note saying that Google Closure Library has this capability, and it is under Apache License 2.0. It is in the crypt.js but doesn't seem to have any crypto code in it, so it might be easier to copy it. -Alex On 7/1/16, 7:39 AM, "Harbs" wrote: >Thanks for the links. I looks like

Re: Encode and Decode UTF8

2016-07-01 Thread Harbs
Thanks for the links. I looks like the unlicensed license is a derivative of the CC0 license, so if I’m reading it right, it’s binding and about as permissive as you can get. I’m not clear on what you are suggesting we do. I’d like to pretty much include some of the code (with minor modificatio

Re: Encode and Decode UTF8

2016-07-01 Thread Justin Mclean
Hi, > Is there any problem just adopting the part of the code relevant to UTF8? Do > we need to add a notice? Not that I can see but public domain is complex [1], but adding something to LICENSE is the current advice. It would be best to get [2] added to [3] and/or [1] by asking on legal discu

Re: Encode and Decode UTF8

2016-07-01 Thread Harbs
Just to add: There are JS APIs for this, namely TextEncoder[3] and TextDecoder[4], but browser support is incomplete. I would probably use these APIs for browsers which support them, and use the “borrowed” code as a fallback. [3]https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder#Brows