Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
46 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,55 +1,70 @@ | ||
| # Requirements for Hangul Text Layout and Typography (klreq) | ||
|
|
||
| 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](https://www.w3.org/International/i18n-activity/templates/gap-analysis/gap-analysis_template.html). This work feeds into the [language matrix](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) which provides a heat-map for language issues on the Web. | ||
|
|
||
|
|
||
| ### Key links | ||
| [GitHub repo](https://github.com/w3c/klreq) • [Discussion threads](https://github.com/w3c/klreq/issues) • [Issue tracker](https://www.w3.org/International/i18n-activity/textlayout/?filter=klreq) (with klreq filter) | ||
|
|
||
|
|
||
| ### Documents | ||
| - Requirements for Hangul Text Layout and Typography : 한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항 • [Editor's copy](https://w3c.github.io/klreq/) • [WG Note](https://www.w3.org/TR/klreq/) | ||
| - [**Requirements for Hangul Text Layout and Typography : 한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항**](https://www.w3.org/TR/klreq) • [*Editor's draft*](https://www.w3.org/International/klreq/) • [*Latest commits*](https://github.com/w3c/klreq/commits/gh-pages/index.html) | ||
|
|
||
| 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. | ||
|
|
||
|
|
||
| ### Related documents | ||
| - [Ready-made Counter Styles](https://www.w3.org/TR/predefined-counter-styles/) | ||
|
|
||
|
|
||
| ### Feedback | ||
| Please use the [GitHub issue list](https://github.com/w3c/klreq/issues) to send feedback about this document. | ||
| Please use the [GitHub issue list](https://github.com/w3c/klreq/issues) to report issues for language support, for discussions, and to send feedback about documents. (Learn [how GitHub issues work](https://www.w3.org/International/i18n-activity/guidelines/issues.html).) | ||
|
|
||
| ### Following | ||
| Rather than just 'Watch' this repository, it is best to subscribe to the [public-i18n-korean](https://lists.w3.org/Archives/Public/public-i18n-korean/) mailing list. That list is notified once a day (in digest form) about not only changes to this repository, but also about other W3C Working Group issues related to the Hangul writing systems. (Please use github issues rather than the mailing list to send feedback.) Meeting minutes are also sent to public-i18n-korean. | ||
| Note that the public-i18n-korean mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion. | ||
|
|
||
| You can find a list of open issues, including those from W3C Working Groups, on the [Layout Tracker](https://w3c.github.io/i18n-activity/textlayout/?filter=hangul) page. (That link applies an `hangul` filter.) | ||
|
|
||
| For archived issues, predating github, see the disused [issue tracker](https://www.w3.org/International/track/products/42). | ||
| ### Participate | ||
| There is currently no task-force group set up for Korean. If there is interest, this can be set up. You can participate in the task force work at various levels. In order of increasing commitment, these include Follower, Contributor, Participant, Editor, and Chair. [Find your level](https://www.w3.org/International/i18n-drafts/pages/task_force_roles). | ||
|
|
||
| **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-korean-request@w3.org?subject=subscribe) to the [public-i18n-korean](https://lists.w3.org/Archives/Public/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. | ||
|
|
||
| ### Contributing | ||
| **To contribute content:** All contributors should read and agree with [CONTRIBUTING.md](CONTRIBUTING.md). | ||
|
|
||
| All contributors should read and agree with [CONTRIBUTING.md](https://github.com/w3c/klreq/blob/gh-pages/CONTRIBUTING.md). | ||
| **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests. | ||
|
|
||
| There is currently no Korean Layout Task Force. | ||
| To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation). | ||
|
|
||
| ### Links | ||
| - [Issue tracker](https://w3c.github.io/i18n-activity/textlayout/?filter=hangul) | ||
| - [Github issues](https://github.com/w3c/klreq/issues) | ||
| - Home Page (tbd) | ||
| - Charter (tbd) | ||
| - Action tracker (tbd) | ||
| - [Writing i18n tests](https://github.com/w3c/i18n-activity/wiki/Writing-i18n-tests) | ||
| - [Practical tips for task forces](https://w3c.github.io/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below) | ||
| - Meeting info (tbd) | ||
| - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-korean/) | ||
| - Contacts: [Richard Ishida](mailto:ishida@w3.org) | ||
|
|
||
| ### Links for editors | ||
| **Because the document is bilingual, you need to follow certain steps when creating or modifying the source text.** See [EDITING.md](https://github.com/w3c/klreq/blob/gh-pages/EDITING.md) for details. | ||
| ### Contacts | ||
|
|
||
| - W3C staff: [Richard Ishida](mailto:ishida@w3.org) | ||
|
|
||
| If you edit a document, you should be familiar with and use the following: | ||
|
|
||
| - [Github guidelines for working with i18n documents](https://w3c.github.io/i18n-activity/guidelines/github) | ||
| - [Editorial guidelines for working with i18n documents](https://w3c.github.io/i18n-activity/guidelines/editing) | ||
|
|
||
| The following templates are available: | ||
| - [Gap analysis template](https://w3c.github.io/i18n-activity/templates/gap-analysis/gap-analysis_template.html) | ||
| - [Requirements document template](https://w3c.github.io/i18n-activity/templates/lreq_doc/lreq_template.html) | ||
| ### Links | ||
| - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-arabic/) | ||
| - [Writing i18n tests](https://github.com/w3c/i18n-activity/wiki/Writing-i18n-tests) | ||
| - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below) | ||
| - [Action tracker](https://www.w3.org/International/groups/arabic-layout/track/actions/open) | ||
| - [Meeting info](https://www.w3.org/2017/07/alreq-meeting-info.html) | ||
|
|
||
|
|
||
| ### Links to background information | ||
| The following information describes work going on at the W3C to support languages on the Web. | ||
| - [Language support heatmap](https://w3c.github.io/typography/gap-analysis/language-matrix.html) | ||
| - [Analysing support for text layout on the Web](https://github.com/w3c/i18n-discuss/wiki/Analysing-support-for-text-layout-on-the-Web) | ||
| - [Overview of language enablement work in progress](https://www.w3.org/International/layout) | ||
| - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) | ||
| - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev) | ||
| - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev) | ||
| - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation) | ||
| - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project) | ||
| - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/) | ||
|
|
||
|
|
||
| ### Links for editors | ||
| If you end up creating a document, you should be familiar with and use the following: | ||
|
|
||
| - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github) | ||
| - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing) |