Re: [web-nfc] Well known type T status bit 7 (#660)

I think you're right, the WebNFC spec should be updated to reflect NFC spec:

![image](https://github.com/w3c/web-nfc/assets/634478/d958c801-afb3-4119-a418-78b6d35854f5)
 
FYI here's the [Chromium code](https://source.chromium.org/chromium/chromium/src/+/main:services/device/nfc/android/java/src/org/chromium/device/nfc/NdefMessageUtils.java;l=281;drc=71bd8f1596b301a842247d3488f901d7ae3dfad2):

```java
        // According to NFCForum-TS-RTD_Text_1.0 specification, section 3.2.1 Syntax.
        // First byte of the payload is status byte, defined in Table 3: Status Byte Encodings.
        // 0-5: lang code length
        // 6  : must be zero
        // 7  : 0 - text is in UTF-8 encoding, 1 - text is in UTF-16 encoding.
        nfcRecord.encoding = (text[0] & (1 << 7)) == 0 ? ENCODING_UTF8 : ENCODING_UTF16;
```



-- 
GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/660#issuecomment-2098273356 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 7 May 2024 12:17:52 UTC