This is the place to explore gaps in support for Korean on the Web and in eBooks, and to document requirements.
We aim to address the problem that local users don’t know how to tell the W3C what problems exist for support of their language on the Web, and the W3C doesn’t know how to contact people who can help when questions arise.
Topics for discussion are suggested by the gap-analysis template. This work feeds into the language matrix which provides a heat-map for language issues on the Web.
GitHub repo • Discussion threads
We’re looking for information about this writing system. Follow the link for specific questions.
The document contains both English and Korean versions of the text. Use the buttons at the top of the document window to select a single-language view.
Please use the GitHub issue list to report issues for language support, for discussions, and to send feedback about documents. (Learn how GitHub issues work.)
Note that the public-i18n-korean mailing list is used to send notification digests & meeting minutes. It is not for technical discussion.
You can participate in the work at various levels. In order of increasing commitment, these include List subscriber, Participant, Editor, and Chair. Explore the options.
To just follow the work: Rather than ‘Watch’ this repository, subscribe to the public-i18n-korean mailing list. That list is notified (no more than once a day, and in digest form), about changes to issues in this repository, but also about other W3C Working Group issues related to the Korean writing systems.
If you prefer to receive notifications of all discussions for Chinese, Japanese, and Korean languages, subscribe to the public-i18n-cjk mailing list.
To contribute content: All contributors should read and agree with CONTRIBUTING.md.
To become a participant, editor, or chair: contact Richard Ishida. We welcome participation requests.
To get an idea about what’s involved, see Get involved with Language Enablement!.
The following information describes work going on at the W3C to support languages on the Web.
If you end up creating a document, you should be familiar with and use the following: