Closed addiment closed 1 year ago
@microsoft-github-policy-service agree
any maintainers want to check this? @aeschli
Resolved the merge conflict (wasn't much to do), can I get another review?
Gonna mention since this might get lost in notification hell otherwise @sandy081
Thanks @addiment!
Certain CSS snippets were broken due to using unicode special characters, specifically the
unicode-range
property of the@font-face
at-rule. The schema had some inconsistencies in using special characters and regular ASCII, so I replaced those instances with their respective ASCII counterparts.“
”
) with U+0022 (quotation mark"
)‘
’
) with U+0027 (apostrophe'
)–
) with U+002D (hyphen-minus-
)While the ASCII swap on quotation marks and parenthesis is mostly preference, the unicode hyphens don't work when used in the browser, which I believe warrants the change. From the W3C CSS fonts specification:
4.5. Character range: the 'unicode-range' descriptor 7.1. The \<urange> type