- From: himorin / Atsushi Shimono via GitHub <noreply@w3.org>
- Date: Thu, 17 Jul 2025 07:44:38 +0000
- To: public-i18n-archive@w3.org
sorry for late to jump into this (actually, wondered how to say...). MDN sets [文字コード](https://developer.mozilla.org/ja/docs/Glossary/Character_set) for character set, and [文字エンコーディング](https://developer.mozilla.org/ja/docs/Glossary/Character_encoding) for character encoding. On this point, latter (文字エンコーディング) should be suitable for this document. But actually, character set should be better written as "文字集合" (per [text within note in JLReq](https://w3c.github.io/jlreq/#h-note-1)) which is not common around engineers, and "文字コード" is also used as character code like U+20 for white space. But, actually, it depends on context, since in Japan various character encodings and character sets are both widely used, like encodings of JIS, SJIS, EUC-JP over JIS X 0213 character set (or older editions), as well as encoding of UTF-8 over Unicode character set. In old age (even before Unicode widely used in Japanese context) people called "文字エンコーディング" to switch among three encodings (usually, Web on JIS, Windows on SJIS, Unix on EUC-JP), and Chrome and Firefox kept menu as "文字エンコーディング" ([Firefox help](https://support.mozilla.org/ja/kb/text-encoding-no-longer-available-firefox-menu), [example](https://www.idcnet.co.jp/e-com/member/setup_character.html)). But in reality it is much more complex, 1) both character set and character encoding are correct for choosing between UTF-8 and JIS on browser, 2) many non experts (on characters) misused or confusingly used two words, and 3) people tend to call these as "文字コード" since it's shorter than 文字エンコーディング. So, for documents, even for introduction, i18n WG/IG should keep "文字エンコーディング" I believe. -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/i18n-drafts/issues/685#issuecomment-3082982309 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 July 2025 07:44:39 UTC