- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Sat, 13 Mar 2021 11:43:58 +0000
- To: public-i18n-archive@w3.org
xfq has just created a new issue for https://github.com/w3c/i18n-activity: == Encoding of CSS files == CSS files in an EPUB package [MUST be encoded in UTF-8 or UTF-16](https://w3c.github.io/epub-specs/epub33/core/#sec-shared-attrs). I think we support the idea of using UTF-8 only, but what about legacy documents that declare the CSS file to be in other encodings? --- 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/1353 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 13 March 2021 11:44:00 UTC