- From: Bert Bos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Mar 2024 00:14:46 +0000
- To: public-i18n-archive@w3.org
bert-github has just created a new issue for https://github.com/w3c/i18n-activity: == lspace/rspace have confusing names == 3.2.4 Operator, Fence, Separator or Accent <mo> https://www.w3.org/TR/mathml-core/#operator-fence-separator-or-accent-mo From the algorithm in [3.3.1.2 Layout of <mrow>](https://www.w3.org/TR/mathml-core/#layout-of-mrow) it follows that the lspace and rspace attributes of an element add space before, respectively after the element. In an rtl formula, that means lspace is on the right and rspace on the left. The names suggest otherwise and when the attributes were created, some 28 years ago, they actually did mean left and right. To avoid confusion, maybe the spec should explicitly say, in a note, that ‘l’ does *not* mean ‘left’. (There is an image, [figure 10](https://www.w3.org/TR/mathml-core/#figure-box-mrow) that contains the words ‘leading’ and ‘trailing’, but doesn't explicitly link them to lspace and rspace.) Another way to avoid the confusion would be to make sure lspace is always added on the left and rspace on the right. But that is not what browsers implement… --- **WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered. **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/1837 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 March 2024 00:14:47 UTC