- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Oct 2019 05:46:53 +0000
- To: public-web-nfc@w3.org
> Actually the other way around (thanks to missing CSS styles) > ![image](https://user-images.githubusercontent.com/1101339/66890946-18db7f00-efe8-11e9-8fb7-0ea1708ccdda.png) > > It actually depends on whether NFC stores the byte order mark (BOM) or not > > ![image](https://user-images.githubusercontent.com/1101339/66891022-488a8700-efe8-11e9-838b-6de7fe34394a.png) Why not have "utf-16" as a valid encoding for NDEFRecordInit and let implementation figure out the appropriate one? When reading back though, record.encoding is "utf16-be" or "utf16-le" and matches TextDecoder. WDYT? -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/366#issuecomment-542528542 using your GitHub account
Received on Wednesday, 16 October 2019 05:46:54 UTC