CINXE.COM
Korean Language Enablement (klreq) | klreq
<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- Begin Jekyll SEO tag v2.8.0 --> <title>Korean Language Enablement (klreq) | klreq</title> <meta name="generator" content="Jekyll v3.10.0" /> <meta property="og:title" content="Korean Language Enablement (klreq)" /> <meta property="og:locale" content="en_US" /> <meta name="description" content="Requirements for Hangul Text Layout and Typography" /> <meta property="og:description" content="Requirements for Hangul Text Layout and Typography" /> <link rel="canonical" href="https://w3c.github.io/klreq/home.html" /> <meta property="og:url" content="https://w3c.github.io/klreq/home.html" /> <meta property="og:site_name" content="klreq" /> <meta property="og:type" content="website" /> <meta name="twitter:card" content="summary" /> <meta property="twitter:title" content="Korean Language Enablement (klreq)" /> <script type="application/ld+json"> {"@context":"https://schema.org","@type":"WebPage","description":"Requirements for Hangul Text Layout and Typography","headline":"Korean Language Enablement (klreq)","url":"https://w3c.github.io/klreq/home.html"}</script> <!-- End Jekyll SEO tag --> <link rel="stylesheet" href="/klreq/assets/css/style.css?v=d9732f1cab7dc3abeede9189efd78e1df8b9ac16"> <!-- start custom head snippets, customize with your own _includes/head-custom.html file --> <!-- Setup Google Analytics --> <!-- You can set your favicon here --> <!-- link rel="shortcut icon" type="image/x-icon" href="/klreq/favicon.ico" --> <!-- end custom head snippets --> </head> <body> <div class="container-lg px-3 my-5 markdown-body"> <h1><a href="https://w3c.github.io/klreq/">klreq</a></h1> <h1 id="korean-language-enablement-klreq">Korean Language Enablement (klreq)</h1> <p>This is the place to explore gaps in support for Korean on the Web and in eBooks, and to document requirements.</p> <p>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.</p> <p>Topics for discussion are suggested by <a href="https://www.w3.org/International/i18n-activity/templates/gap-analysis/gap-analysis_template.html">the gap-analysis template</a>. This work feeds into the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html">language matrix</a> which provides a heat-map for language issues on the Web.</p> <h3 id="key-links">Key links</h3> <p><a href="https://github.com/w3c/klreq">GitHub repo</a> • <a href="https://github.com/w3c/klreq/issues">Discussion threads</a></p> <hr /> <h2 id="help-wanted">Help wanted!</h2> <p><strong>We’re looking for information about this writing system. Follow the link for specific questions.</strong></p> <p><strong><a href="https://github.com/w3c/klreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion">Korean</a></strong></p> <hr /> <h3 id="resource--requirement-docs">Resource & requirement docs</h3> <ul> <li><strong>Korean Script Resources</strong> • <a href="https://www.w3.org/TR/kore-lreq">DNOTE</a> • <a href="https://www.w3.org/International/klreq/kore/"><em>Editor’s draft</em></a> • <a href="https://github.com/w3c/klreq/commits/gh-pages/kore/"><em>Latest commits</em></a></li> <li><strong>Requirements for Hangul Text Layout and Typography : 한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항</strong> • <a href="https://www.w3.org/TR/klreq">DNOTE</a> • <a href="https://www.w3.org/International/klreq/"><em>Editor’s draft</em></a> • <a href="https://github.com/w3c/klreq/commits/gh-pages/index.html"><em>Latest commits</em></a></li> </ul> <p>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.</p> <h3 id="gap-analysis-docs">Gap-analysis docs</h3> <ul> <li><strong>Korean Gap Analysis</strong> • <a href="https://www.w3.org/TR/kore-gap">DNOTE</a> • <a href="https://www.w3.org/International/klreq/gap-analysis/"><em>Editor’s draft</em></a> • <a href="https://github.com/w3c/klreq/commits/gh-pages/gap-anaylsis/index.html"><em>Latest commits</em></a></li> </ul> <h3 id="related-documents">Related documents</h3> <ul> <li><a href="https://www.w3.org/TR/predefined-counter-styles/">Ready-made Counter Styles</a></li> </ul> <h3 id="feedback">Feedback</h3> <p>Please use the <a href="https://github.com/w3c/klreq/issues">GitHub issue list</a> to report issues for language support, for discussions, and to send feedback about documents. (Learn <a href="https://www.w3.org/International/i18n-activity/guidelines/issues.html">how GitHub issues work</a>.)</p> <p>Note that the public-i18n-korean mailing list is used to send notification digests & meeting minutes. It is <strong>not</strong> for technical discussion.</p> <h3 id="participate">Participate</h3> <p>You can participate in the work at various levels. In order of increasing commitment, these include List subscriber, Participant, Editor, and Chair. <a href="https://www.w3.org/International/i18n-drafts/pages/languagedev_participation.html">Explore the options</a>.</p> <p><strong>To just follow the work:</strong> Rather than ‘Watch’ this repository, <a href="mailto:public-i18n-korean-request@w3.org?subject=subscribe">subscribe</a> to the <a href="https://lists.w3.org/Archives/Public/public-i18n-korean/">public-i18n-korean</a> 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.</p> <p>If you prefer to receive notifications of all discussions for Chinese, Japanese, and Korean languages, <a href="mailto:public-i18n-cjk-request@w3.org?subject=subscribe">subscribe</a> to the <a href="https://lists.w3.org/Archives/Public/public-i18n-cjk/">public-i18n-cjk</a> mailing list.</p> <p><strong>To contribute content:</strong> All contributors should read and agree with <a href="/klreq/CONTRIBUTING.md">CONTRIBUTING.md</a>.</p> <p><strong>To become a participant, editor, or chair:</strong> contact <a href="mailto:ishida@w3.org">Richard Ishida</a>. We welcome participation requests.</p> <p>To get an idea about what’s involved, see <a href="https://www.w3.org/International/i18n-drafts/pages/languagedev_participation">Get involved with Language Enablement!</a>.</p> <h3 id="contacts">Contacts</h3> <ul> <li>W3C staff: <a href="mailto:ishida@w3.org">Richard Ishida</a></li> </ul> <h3 id="links">Links</h3> <ul> <li><a href="https://lists.w3.org/Archives/Public/public-i18n-korean/">public-i18n-korean mail archive</a></li> <li><a href="https://lists.w3.org/Archives/Public/public-i18n-cjk/">public-i18n-cjk mail archive</a></li> <li><a href="[https://github.com/w3c/i18n-activity/wiki/Writing-i18n-tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests)">Writing i18n tests</a></li> <li><a href="https://www.w3.org/International/i18n-activity/guidelines/process.html">Practical tips for task forces</a> (See also the github and editorial guidelines below)</li> </ul> <h3 id="links-to-background-information">Links to background information</h3> <p>The following information describes work going on at the W3C to support languages on the Web.</p> <ul> <li><a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html">Language support heatmap (matrix)</a></li> <li><a href="https://www.w3.org/International/i18n-drafts/nav/languagedev">Analysing support for text layout on the Web</a></li> <li><a href="https://www.w3.org/International/i18n-drafts/nav/languagedev">Overview of language enablement work in progress</a></li> <li><a href="https://www.w3.org/International/i18n-drafts/pages/languagedev_participation">Get involved with Language Enablement</a></li> <li><a href="https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project">Setting up a Gap Analysis Project</a></li> <li><a href="https://www.w3.org/International/sponsorship/">Internationalization Sponsorship Program</a></li> </ul> <h3 id="links-for-editors">Links for editors</h3> <p>If you end up creating a document, you should be familiar with and use the following:</p> <ul> <li><a href="https://www.w3.org/International/i18n-activity/guidelines/github">Github guidelines for working with i18n documents</a></li> <li><a href="https://www.w3.org/International/i18n-activity/guidelines/editing">Editorial guidelines for working with i18n documents</a></li> </ul> <div class="footer border-top border-gray-light mt-5 pt-3 text-right text-gray"> This site is open source. <a href="https://github.com/w3c/klreq/edit/gh-pages/home.md">Improve this page</a>. </div> </div> <script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/4.1.0/anchor.min.js" integrity="sha256-lZaRhKri35AyJSypXXs4o6OPFTbTmUoltBbDCbdzegg=" crossorigin="anonymous"></script> <script>anchors.add();</script> </body> </html>