- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Tue, 16 Apr 2019 19:17:20 +0200
- To: public-i18n@w3.org
WebAssembly is basically a VM spec. All communication happens through Javascript (at least, that's all we're standardizing). Javascript invokes WebAssembly functions via a symbol table which maps a UTF-8 string to an address. These strings have no interpretation beyond a sequence of Unicode scalar values. For instance, there's no Unicode Normalization, no parsing as case-foldable domain names, etc. Is there a state-approved way to say that? Because it's a VM, it may be called upon to manipulate e.g. human names, currency. In short, the subject matter may entail i18n requirements but that WebAssembly doesn't know anything about the subject matter and imposes no i18n requirements on it. My expectation is that it would be more confusing to mention that fact than to simply leave it out. Thoughts? If EcmaScript had sections for I18N and Security Considerations, I could just copy them. Can anyone think of something else I could copy from? -- -eric office: +1.617.258.5741 32-G528, MIT, Cambridge, MA 02144 USA mobile: +1.617.599.3509 (eric@w3.org) Feel free to forward this message to any list for any purpose other than email address distribution.
Received on Tuesday, 16 April 2019 17:17:25 UTC