- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Sep 2016 14:12:40 +0000
- To: public-svg-issues@w3.org
(discussed by I18N WG at TPAC) The problem here is one of terminology. A "Unicode code point" is what SVG is defining as a "character": a single Unicode value. Counting code points is ideal, since a character cannot be split. However, since SVG is based on DOMString, which itself is defined in terms of UTF-16, probably UTF-16 code units are a necessary part of SVG's implementation. A health warning should be included to ensure that Unicode code points (characters) are not split in half. UTF-8 code units (i.e. bytes) suffer from the same "addressable character" issue as UTF-16, as a character can take 1, 2, 3, or 4 bytes per character to encode. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/svgwg/issues/280#issuecomment-249203855 using your GitHub account
Received on Friday, 23 September 2016 14:12:55 UTC