- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Jul 2021 13:08:09 +0000
- To: public-i18n-archive@w3.org
I'm not persuaded that suffixing is a good idea at all. You already mentioned that including RLM/LRM at the start of the string is more efficient, and we don't want them to use language tag code points, which are the things that take up lots of initial bytes. So really we're talking about one extra character in the string, and then only where the bidi algorithm needs help. So i don't think the argument about preserving data rather than medata is convincing. And anyway, if strings are going to be truncated, either (a) it's likely to be less problematic to lose one code point at the end (since we are truncating already) than to lose directional information, and (b) this format they describe isn't JSON-LD, so i don't think it's comparable to @lang, and (c) if they intend for metadata to be post-pended, they should require the consumer to capture and apply the metadata before truncating. And, as Martin mentioned, using paired controls, such as the language tags or the RLI...PDI etc code points, where some of the metadata is effectively post-pended, is dangerous in scenarios where truncation becomes a possibility, since a missing end code point can cause problems when the text is inserted into a location. (I think we may need to make that point in string-meta, btw.) Btw, although it does say it, I think we could improve the first para to more clearly indicate that what was put in the spec drew on Addison's personal thoughts before they could be discussed by the i18n WG. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1398#issuecomment-875588153 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 July 2021 13:12:22 UTC