- From: James via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Oct 2023 17:17:03 +0000
- To: public-i18n-archive@w3.org
JamesTheAwesomeDude has just created a new issue for https://github.com/w3c/i18n-drafts: == [questions/qa-css-charset] "Default" encoding for CSS? == [source] (https://www.w3.org/International/questions/qa-css-charset) [en] Is there any official guidance on how browsers should interpret **CSS documents** that lack any encoding declaration? For example, the latest version _\[117.0.2045.47\]_ of Microsoft Edge yields mojibake when rendering this page: https://www.devever.net/~hl/omi - The (X)HTML page declares its encoding to be UTF-8 in a `<meta>` tag - The external CSS file's encoding is not declared in any way - The external CSS file contains several non-ASCII byte sequences: * `{ 0xe2, 0x80, 0x93 }` (can be interpreted as “–” _or_ as “–”) * `{ 0xc2, 0xb7 }` (can be interpreted as “·” _or_ as “·”) * `{ 0xe2, 0x80, 0x93 }` (can be interpreted as “–” _or_ as “–”) * `{ 0xe2, 0x8f, 0xa9, 0xef, 0xb8, 0x8e }` (can be interpreted as “â�©ï¸Ž” _or_ as “⏩︎”) * `{ 0xe2, 0x8e, 0x8c }` (can be interpreted as “⎌” _or_ as “⎌”) * `{ 0xe2, 0x9d, 0x8f }` (can be interpreted as “â��” _or_ as “❏”) * `{ 0xe2, 0x96, 0xbd }` (can be interpreted as “â–½” _or_ as “▽”) Obviously, the administrator of this website SHOULD be declaring his encoding (whether it be UTF-8 or Windows-1252). But, *given* that he hasn't, is Edge's behavior here at least ALLOWABLE? Please view or discuss this issue at https://github.com/w3c/i18n-drafts/issues/547 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 October 2023 17:17:05 UTC