- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Jul 2021 17:35:58 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == Short_but_informative_title_here == 6.4.2. Language and Direction Encoding https://www.w3.org/TR/webauthn-2/#sctn-strings-langdir > The second consists of a single code point which is either U+200E (“LEFT-TO-RIGHT MARK”), U+200F (“RIGHT-TO-LEFT MARK”), or U+E007F (“CANCEL TAG”). The first two can be used to indicate directionality but SHOULD only be used when neccessary to produce the correct result. (E.g. an RTL string that starts with LTR-strong characters.) The value U+E007F is a direction-agnostic indication of the end of the language tag. The mechanism for indicating base direction has multiple flaws: * This is a unique and thus unproven encoding mechanism. It requires string introspection that would likely produce errors. * RLM/LRM are strongly directional characters and should precede the string, as they would result in many cases in the correct rendering. * Separate bidi metadata is preferred to in-line controls. * RLM/LRM cannot be distinguished from normal bidi controls so there is potentially danger that implementations would add extra characters. It would be better to encode bidi metadata unambiguously as metadata. An alternative to RLM/LRM would be to provide guidance to implementations to provide proper bidi control character sequences and to present strings in an isolating context. --- Instructions: This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html 1. **CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** Then ask the i18n WG to review your comment. 2. Set a label to identify the spec. This starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staffer to help. 3. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment. 4. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '. 5. Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. 6. Remove the 'pending' label. **This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:** § link_to_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1397 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 July 2021 17:36:00 UTC