[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Public WebGL] String support in DataView
- To: [email protected]
- Subject: [Public WebGL] String support in DataView
- From: John Tamplin <[email protected]>
- Date: Fri, 4 Nov 2011 11:08:15 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record; bh=PJ2LqU0YWAER8o5ZQUU+4BXP0RvBig2YpYswM0H8EIY=; b=PMzHtstcrqxZEPYU18GMw6NeaTA1vEf0Ml3YzDgw/d/hnRhymb8S5ZQoBRSAuzoA2E uNgs9NWvIXsfr6ScLwrA==
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- Sender: [email protected]
Has there been any discussion on this since
http://www.khronos.org/webgl/public-mailing-list/archives/1104/msg00043.html
Right now, to extract UTF8 text from a ArrayBuffer, you have to do the
decoding in JS, which is slow and error prone.
>From the linked discussion, there was a suggestion that arbitrary
character sets would be required. However, that could require a lot
of effort on the implementors and be hard to agree on what character
sets should be supported -- I would suggest just supporting
UTF8/UTF16LE/UTF16BE initially as they require no tables to implement,
and maybe if there is interest/demonstrated need more could be added
later.
--
John A. Tamplin
Software Engineer (GWT), Google
-----------------------------------------------------------
You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------