- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2025 17:29:20 +0000
- To: public-webauthn@w3.org
Not quite. The truncation is blind, removing code points at arbitrary code point boundaries. Let's consider the language tag `tlh-Cyrl-AQ`. Truncations that make the tag `tlh-Cyrl-A` or `tlh-C` or `tlh-` produce not well-formed and invalid language tags (contrary to the statement in the text that they would still be valid). Truncations like `tlh-Cy` produce a tag is is well-formed and valid and with a wholly different meaning (`cy` is the code for the region Cypress). The text currently says (bolding is mine): > Consumers of strings that may have language and direction encoded should be aware that truncation **could truncate a [language tag](https://w3c.github.io/i18n-glossary/#dfn-language-tag) into a different, but still valid, language**. The final directionality marker or CANCEL TAG code point provide an unambigous indication of truncation. But, as noted, the highlighted bits are potentially not correct. In the comment linked above, which is the result of our meeting at TPAC, I would have expected: - remove the custom language/direction encoding scheme altogether (eliminating the need for this issue) and replace with a file-level default - if you keep the custom scheme, add text to the truncation section requiring per-subtag truncation of language tags - if you keep "blind" truncation with no special handling of language tags, amend the text in the section about language tags to note that the truncated tag might have changed meaning, not be valid, or not be well-formed. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1645#issuecomment-2675144139 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 February 2025 17:29:21 UTC