CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>Find i18n</title> <script> var f = { } // AUTHORS should fill in these assignments: f.directory = 'nav'+'/'; // the path to this file, not including /International or the file name f.filename = 'resources'; // the file name WITHOUT extensions f.authors = 'Richard Ishida, W3C'; // author(s) and affiliations f.previousauthors = ''; // as above f.modifiers = ''; // people making substantive changes, and their affiliation f.searchString = 'level2-resources'; // blog search string - usually the filename without extensions f.firstPubDate = '2006-03-12'; // date of the first publication of the document (after review) f.lastSubstUpdate = { date:'2016-05-06', time:'12:05'} // date and time of latest substantive changes to this document f.status = 'notreviewed'; // should be one of draft, review, published, notreviewed or obsolete f.path = '' // what you need to prepend to a URL to get to the /International directory // AUTHORS AND TRANSLATORS should fill in these assignments: f.thisVersion = { date:'2016-05-06', time:'12:05'} // date and time of latest edits to this document/translation f.contributors = ''; // people providing useful contributions or feedback during review or at other times // also make sure that the lang attribute on the html tag is correct! // TRANSLATORS should fill in these assignments: f.translators = 'xxxNAME, ORG'; // translator(s) and their affiliation - a elements allowed, but use double quotes for attributes f.breadcrumb = ''; f.additionalLinks = '' </script> <script src="resources-data/translations.js"> </script> <script src="../javascript/doc-structure/article-dt.js"> </script> <script src="../javascript/boilerplate-text/boilerplate-en.js"></script>  <script src="../javascript/doc-structure/sitepage-2022.js"> </script> <script src="../javascript/articletoc-2022.js"></script> <link rel="stylesheet" href="../style/sitepage-2022.css" /> <link rel="copyright" href="#copyright"/> <style> .content ul a { font-size: 140%; } </style> </head> <body> <header> <nav id="mainNavigation"></nav><script>document.getElementById('mainNavigation').innerHTML = mainNavigation</script> </header> <div class="content"> <h1> Find W3C I18n resources</h1> <p>This page links to various types of resource available on the W3C Internationalization site, and some elsewhere, relating to Internationalization.</p> <p>The following pages also point to subsets of this information, but are tailored to specific roles:</p> <p style="text-align: center;"><a href="../nav/contentdev" style="font-size: 140%;">Content authors</a></p> <p style="text-align: center;"><a href="../nav/specdev" style="font-size: 140%;">Spec developers & implementers</a></p> <p style="text-align: center;"><a href="../nav/languagedev" style="font-size: 140%;">Language enablement</a></p> <p style="text-align: center;"><a href="../getting-started/wg.en" style="font-size: 140%;">Group participants</a></p> <section id="radar"> <h2>Current projects & news</h2> <p>Links to help you locate current topics of interest. See also the page <a href="follow">Follow W3C Internationalization work</a> for suggestions about how to follow the work.</p> <ul> <li><a class="print" href="../../i18n-activity/projects/">Project RADAR</a> <span class="desc"><br> An overview of current activity, grouped by work area. This would normally be your starting point for getting to know the work of the Working Group (WG).</span></li> <li><a class="print" href="../..//i18n-activity/repostatus/">i18n WG tracker</a> <span class="desc"><br> Tracks issues raised against documents we are developing, or those developed by task forces.</span></li> <li><a class="print" href="https://www.w3.org/International">i18n home page</a><br> <span class="desc">Provides news bulletins.</span></li> <li><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="rgb(29,141,238)" class="bi bi-mastodon" viewBox="0 0 16 16"> <path d="M11.19 12.195c2.016-.24 3.77-1.475 3.99-2.603.348-1.778.32-4.339.32-4.339 0-3.47-2.286-4.488-2.286-4.488C12.062.238 10.083.017 8.027 0h-.05C5.92.017 3.942.238 2.79.765c0 0-2.285 1.017-2.285 4.488l-.002.662c-.004.64-.007 1.35.011 2.091.083 3.394.626 6.74 3.78 7.57 1.454.383 2.703.463 3.709.408 1.823-.1 2.847-.647 2.847-.647l-.06-1.317s-1.303.41-2.767.36c-1.45-.05-2.98-.156-3.215-1.928a3.614 3.614 0 0 1-.033-.496s1.424.346 3.228.428c1.103.05 2.137-.064 3.188-.189zm1.613-2.47H11.13v-4.08c0-.859-.364-1.295-1.091-1.295-.804 0-1.207.517-1.207 1.541v2.233H7.168V5.89c0-1.024-.403-1.541-1.207-1.541-.727 0-1.091.436-1.091 1.296v4.079H3.197V5.522c0-.859.22-1.541.66-2.046.456-.505 1.052-.764 1.793-.764.856 0 1.504.328 1.933.983L8 4.39l.417-.695c.429-.655 1.077-.983 1.934-.983.74 0 1.336.259 1.791.764.442.505.661 1.187.661 2.046v4.203z"></path> </svg> <a class="print" href="https://w3c.social/@webi18n">@webi18n on Mastodon</a><br> <span class="desc"></span>Follow the news feed on Mastodon.</li> <li><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="20px" height="18px" viewBox="0 0 20 18" version="1.1"> <g id="surface1"> <path style=" stroke:none;fill-rule:nonzero;fill:rgb(6.666667%,52.156866%,99.607843%);fill-opacity:1;" d="M 4.523438 1.496094 C 6.742188 3.191406 9.125 6.628906 10 8.472656 C 10.875 6.628906 13.257812 3.191406 15.476562 1.496094 C 17.074219 0.273438 19.667969 -0.675781 19.667969 2.335938 C 19.667969 2.9375 19.328125 7.390625 19.128906 8.113281 C 18.441406 10.625 15.925781 11.265625 13.6875 10.878906 C 17.597656 11.558594 18.59375 13.804688 16.445312 16.046875 C 12.363281 20.3125 10.582031 14.980469 10.125 13.613281 C 10.039062 13.359375 10 13.242188 10 13.34375 C 10 13.242188 9.960938 13.359375 9.875 13.613281 C 9.417969 14.980469 7.636719 20.3125 3.554688 16.046875 C 1.40625 13.804688 2.402344 11.558594 6.3125 10.878906 C 4.074219 11.265625 1.558594 10.625 0.871094 8.113281 C 0.671875 7.390625 0.332031 2.9375 0.332031 2.335938 C 0.332031 -0.675781 2.925781 0.273438 4.523438 1.496094 Z M 4.523438 1.496094 "/> </g> </svg> <a class="print" href="https://bsky.app/profile/webi18n.bsky.social">@webi18n on Bluesky</a><br> <span class="desc"></span>Follow the news feed on Bluesky.</li> <li><img src="https://www.w3.org/International/icons/twitter-bird.png" alt="" style="vertical-align: middle;"><a class="print" href="https://www.twitter.com/webi18n">@webi18n on Twitter</a><br> <span class="desc"></span>Follow the news feed on Twitter.</li> </ul> </section> <section id="docs"> <h2>Documents</h2> <p>Find WG Notes and articles intended to explain i18n concepts to content authors, spec developers, etc.</p> <ul> <li> <p><a class="eyecatcher" href="https://www.w3.org/standards/techs/i18n">Technical reports & notes </a><br> Documents that follow the W3C Process guidelines. The target for such documents is normally W3C Recommendation or WG Note.</p> </li> <li> <p><a class="eyecatcher" href="/International/articlelist">Articles, tutorials and best practices </a> <br> Miscellaneous resources related to the use of W3C and other more general Web technologies in international content.</p> </li> </ul> </section> <section id="education"> <h2>Educational resources</h2> <p>Techniques indexes provide a set of do's and don'ts for specific tasks, and links to further reading. These two indexes are the best developed.</p> <ul> <li><p><a href="/International/i18n-drafts/techniques/authoring-html.en?collapse">Authoring HTML & CSS</a></p></li> <li><p><a href="/International/i18n-drafts/techniques/developing-specs.en?collapse">Developing specifications</a></p></li> </ul> <p>The following links may also be useful, although they are less well developed.</p> <p><a href="/International/techniques/authoring-svg?collapse" style="font-size: 110%;"> Authoring SVG</a> • <a href="/International/techniques/authoring-xml?collapse" style="font-size: 110%;">Authoring XML</a> • <a href="/International/techniques/server-setup?collapse" style="font-size: 110%;">Setting up a server</a> • <a href="/International/techniques/developing-schemas?collapse" style="font-size: 110%;">Developing schemas</a></p> <p>More links</p> <ul> <li><a class="print" href="https://www.w3.org/International/articlelist">Article list</a> <span class="desc"><br> A short-cut to the articles and tutorials the W3C i18n WG produces.</span></li> <li><a class="print" href="https://github.com/orgs/w3c/projects/92/views/1">Article development pipeline</a> <span class="desc"><br> See what educational material we're currently working on, and what's out for review.</span></li> </ul> </section> <section id="groups"> <h2>Groups</h2> <ul> <li><a href="about#groups">List of groups</a><br> Groups working on internationalization at W3C, including links to home pages, GitHub repos, and mailing lists. </li> <li><a href="participate">Join a group</a></li> </ul> </section> <section id="obsolete"> <h2>Historic/obsolete documents</h2> <ul> <li><a href="/International/articles/historic/">Links</a><br> These links are to documents that are out of date and are no longer linked to from the rest of the site. </li> </ul> </section> <section id="layout"> <h2>Language enablement</h2> <ul> <li><a class="print" href="https://w3.org/TR/typography/">Language enablement index</a> <span class="desc"><br> Index of requirements for text layout.</span></li> <li><a class="print" href="http://w3c.github.io/type-samples/">Type samples</a> <span class="desc"><br> Samples of layout features in the wild.</span></li> <li><a class="print" href="../../i18n-activity/textlayout/">Layout issue tracker</a> <span class="desc"><br> Tracks requests for information, spec issues and browser bugs.</span></li> <li><a class="print" href="../nav/languagedev">Current layout work</a> <span class="desc"></span></li> <li><a class="print" href="../pages/language_framework_overview">Analysing support for text layout on the Web</a> <span class="desc"><br> An overview of the current framework we use for gathering requirements and analysing gaps.</span></li> <li><a class="print" href="https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project">Setting up a Gap Analysis Project</a> <span class="desc"><br> Gap analysis projects look at how well a language or set of languages is supported on the Web in terms of text layout, and creates proposals for improving support where needed.</span></li> </ul> </section> <section id="mail"> <h2>Mail archives</h2> <ul> <li> <p>Mail archives can be found in the <a href="about#groups">list of groups</a>. Check the group pages for information about how the lists are used.</p> </li> </ul> </section> <section id="newsfeeds"> <h2>News feeds</h2> <p>The main news feed for the W3C Internationalization activity is the home page and the @webi18n mastodon and twitter channels. However there are some additional feeds listed at this link.</p> <ul> <li> <p><a class="eyecatcher" href="follow">News feeds </a></p> </li> </ul> </section> <section id="useful"> <h2>Practical how-to's</h2> <p>Useful explainers for group participants.</p> <ul> <li><a href="/International/i18n-activity/guidelines/process.html">Practical tips for group members</a><br> Advice for participants of groups about starting and running a telecon, managing actions, managing issues, using a github project pipeline, and recruiting someone to a task force</li> <li><a href="/International/i18n-activity/guidelines/github">Github guidelines for working with i18n docs</a><br> A simple introduction, with step by step advice, on how to use GitHub as a group participant. </li> <li><a href="/International/i18n-activity/guidelines/editing">Editorial guidelines</a><br> Advice on editing documents related to the internationalization activity. </li> </ul> </section> <section id="standards"> <h2>Related standards work</h2> <ul> <li><a href="http://www.unicode.org/">Unicode</a></li> <li><a href="http://multilingualweb.eu">MultilingualWeb</a></li> </ul> </section> <section id="reviews"> <h2>>Reviews</h2> <p>The Internationalization WG reviews specifications. These links relate to that activity. </p><ul> <li> <p><a href="/International/i18n-drafts/techniques/shortchecklist">Short review checklist</a> <br> Useful for doing a working group participant wanting to do a self-review of their spec, or for anyone else wanting help to review a spec.</p> </li> <li> <p><a href="/International/i18n-drafts/techniques/developing-specs.en?collapse">Full review checklist</a> <br> More detailed checklist for areas that are picked out from the short review checklist.</p> </li> <li> <p><a class="eyecatcher" href="https://github.com/orgs/w3c/projects/91">Review radar</a> <br> A list of documents that need review, and that are in review.</p> </li> <li> <p><a class="eyecatcher" href="/International/i18n-activity/reviews/">Review comment tracker </a> <br> Open review comments made by the i18n Working Group about specifications of other groups, in order of latest changed.</p> </li> <li> <p><a class="eyecatcher" href="/International/i18n-activity/guidelines/review-instructions">Review guidelines </a> <br> How to review specs and raise issues.</p> </li> <li> <p><a class="print" href="/International/i18n-activity/guidelines/review-instructions">How to do a review</a> <span class="desc"><br> Step-by-step guidelines about how to raise review comments.</span></p> </li> <li> <p><a class="print" href="https://www.w3.org/International/reviews/projReview.html">i18n WG review process overview</a> <span class="desc"><br> Presentation describing how i18n folks do reviews, and including tips for chairs and staff contacts.</span></p> </li> </ul> </section> <section id="sponsorship"> <h2>Sponsorship Program</h2> <p>The W3C is looking to increase participation and funding so that we can expand our activity beyond the core work. For more information, see:</p> <ul> <li> <p><a class="eyecatcher" href="/International/sponsorship/">Sponsorship overview </a></p> </li> </ul> </section> <section id="talks"> <h2>Talks</h2> <p>Presentations given by members of the Internationalization Working Group are linked from this page:</p> <ul> <li> <p><a class="eyecatcher" href="https://www.w3.org/blog/International/category/x/talks/">Talks</a></p> </li> </ul> </section> <section id="tests"> <h2>Tests</h2> <p>The i18n WG develops tests for international features, and contributes to the Web Platform Test Suite. It also makes available results for the tests.</p> <ul> <li> <p><a class="eyecatcher" href="/International/i18n-tests/">i18n test index</a><br> Points to summaries of test results. To access the tests themselves, click on the link in the left-most column. The page lists tests available using the I18n Test Suite and tests created using the interactive test format.</p> </li> <li> <p><a class="eyecatcher" href="/International/i18n-drafts/pages/interactive_tests.html">Working with interactive tests</a><br> Describes practical steps for creating and managing interactive tests to support the write-up of a gap.</p> </li> <li> <p><a class="eyecatcher" href="https://github.com/w3c/i18n-tests/#i18n-tests">i18n-tests</a><br> Contains an overview of how to create tests for the i18n test suite, and points to a document to help you manage them.</p> </li> </ul> </section> <section id="tools"> <h2>Tools</h2> <p>Online utilities to help content authors.</p> <ul> <li><a class="print" href="https://validator.w3.org/i18n-checker/">i18n checker</a> <br> <span class="desc">Run your pages through this checker to see if there are any issues.</span></li> <li><a class="print" href="https://r12a.github.io/app-subtags/">Language subtag lookup</a> <span class="desc"><br> Find or check language tags and subtags. Uses the latest BCP47 data.</span></li> <li><a class="print" href="https://www.w3.org/International/tools">Other tools</a></li> </ul> </section> </div> <br style="clear: both;" /> <footer id="thefooter"></footer><script>document.getElementById('thefooter').innerHTML = g.bottomOfPage</script> <script>completePage()</script> </body> </html>