Re: [bp-i18n-specdev] Fix link, css, and validator errors (prep for publication) (#92)

@r12a I made changes on lines 2194 and 2212 that you suggest. I reworded and clarified on 2216 along the lines of what you're suggesting (have a look).

I agree about the problem with spaces and I'm open to suggestions. I added the half-`em` of space in the `margin-inline` to guard against problems when the space is accidentally omitted. When the space is present one gets something more like 1.5 em of space. I didn't want to fool with trying to collapse the space. Overall this is a side-effect of removing the square brackets. Should we just say "put a space before the span" and remove the `margin-inline` space?

Regarding combining marks, I agree that's a problem. Should I add text suggesting the need to include a no-break space or other base character (such as how you included a base as an example with SARA AM in the glossary recently)?

-- 
GitHub Notification of comment by aphillips
Please view or discuss this issue at https://github.com/w3c/bp-i18n-specdev/pull/92#issuecomment-1505264106 using your GitHub account


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

Received on Wednesday, 12 April 2023 13:18:27 UTC