Should there be a UTF-8 health warning?

未关闭
  • 哪里不对？
#335 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
html
领域
documentation

调研方向

Read the PushMessageData interface section in the Push API specification, especially its references to UTF-8 decoding and encoding. Decide whether the specification should warn authors about non-UTF-8 message encodings; done means the issue’s question is resolved in the specification. The issue has had no comment for years, so check the discussion context before starting.

由索引模型根据 Issue 内容生成。

描述

editorial i18n-needs-resolution

PushMessageData interface
https://www.w3.org/TR/push-api/#pushmessagedata-interface

In w3c/push-api#276 we asked about the inherent UTF-8 requirement for the text (and to a far lesser extent json) methods. These method's default implementation assumes that the encoding of the message's bytes are, in fact, UTF-8 if the message is to be treated as text. The I18N WG is happy that UTF-8 is the default encoding and that it is the only supported encoding. But we note that there is no mention outside of the message data interface of UTF-8 or Unicode. Other data can be sent down the wire and retrieved using arrayBuffer or blob, but there is no mention of character encodings aside from the references to utf-8 decode and utf-8 encode in this section. So our ask is:

Should there be a health warning about using non-UTF-8 encodings?

[Note: this came out of I18N WG reviewing our previous comments in our periodic review cycle]

主要语言
HTML
星标
158
派生
43
平均合并
2 天 6 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

w3c/push-api 的其他 Issue

查看 w3c/push-api 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。