CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>Join 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 = 'nav-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%; } .eyecatcher {font-size: 140%; color: #E8941D; font-weight: 400; } </style> </head> <body> <header> <nav id="mainNavigation"></nav><script>document.getElementById('mainNavigation').innerHTML = mainNavigation</script> </header> <div class="content"> <h1>Get involved in W3C Internationalization</h1> <section id="sidebarExtras"> <h2 id="i18n" class="notoc"><a href="#i18n">Related</a></h2> <p><a href="about#groups">List of groups</a></p> </section> <p>The Internationalization Activity welcomes the participation of individuals and organizations around the world to help improve the appropriateness of the Web for multiple cultures, scripts and languages.</p> <p>We are always looking for people who can help us (a) understand the state of the international Web, and requirements for improving it, (b) review specifications and support developers, and (c) develop or review educational materials for content developers and others.</p> <p>See also the <a href="about#groups">list of W3C Internationalization groups</a>, which provides information about github repositories, mailing lists, and home pages.</p> <section id="benefits"> <h2>Benefits of participation</h2> <p>Participation can benefit the participant and his or her organization in the following ways.</p> <ul> <li>Significantly develop your understanding of how W3C technologies are used in a global Web and bring that knowledge back to your organization.</li> <li>Review the state of the art in a range of Web technologies and develop understanding of key internationalization issues by reviewing specifications.</li> <li>Raise your profile and that of your organization by developing best practices, and education and outreach materials.</li> <li>Contribute your and your organization's ideas and needs for the development of new specifications. </li> <li>Discuss and explore ideas alongside other leaders in the field.</li> <li>Gain exposure to internationalization issues in a wide range of technologies.</li> <li>Lay claim to contributing directly to making the World Wide Web more worldwide.</li> </ul> <p>The groups need people with a wide range of skills, from technical authoring to specialised knowledge of particular technologies.</p> </section> <section id="joining"> <h2>Join the Internationalization Working Group (i18n WG)</h2> <p>The Internationalization Working Group provides a wide range of advice and support for groups developing or using international aspects of the Web. It reviews specifications produced by other W3C Working Groups, looking for issues that would cause barriers to deployment and use of Web technologies due to language, script, region or culture, and discusses issues with those groups. It also produces its own documents and content. This includes requirements, guidelines and proposals for specification writers, as well as educational resources, checkers and outreach to help developers and content authors better understand and more widely implement the internationalization aspects of W3C technology. The group also develops tests for internationalization features on the Web, and produces summaries of their results.</p> <p>See the <a href="https://w3c.github.io/i18n-activity/i18n-wg/" class="eyecatcher">home page</a> for more information, including how to sign up. </p> </section> <section id="join_ig"> <h2>Join the Internationalization Interest Group (i18n IG)</h2> <p>By subscribing to the <a href="https://lists.w3.org/Archives/Public/www-international/" class="eyecatcher">www-international@w3.org</a> mailing list you can join the Internationalization Interest Group. This will enable you to track discussions and work of the i18n WG, since the list recieves daily digests of all Github traffic and can also be used for adhoc discussions, where appropriate. There are no teleconferences. To join, send a mail to <a href="mailto:www-international-request@w3.org?subject=subscribe">www-international-request@w3.org</a> with <code>subscribe</code> as the subject.</p> <p>See the <a href="https://w3c.github.io/i18n-activity/i18n-ig/" class="eyecatcher">home page</a> for more information.</p> </section> <section id="join_layout"> <h2>Join a Language Enablement group</h2> <p>Under the umbrella of the i18n IG, and supported by the i18n WG, there are a number of initiatives in place to identify international typography problems experienced by Web users and content authors. The task forces identify and analyse the gaps that exist, document the related requirements, and help spec developers and browser implementers to introduce support for needed local features.</p> <p>See the <a href="https://www.w3.org/International/i18n-drafts/pages/languagedev_participation" class="eyecatcher">Get involved with Language Enablement</a> for a list of groups, and information about how to contribute. </p> </section> <section id="join_its"> <h2>Join the ITS IG</h2> <p>The ITS (Internationalization Tag Set) Interest Group aims to foster a community of users of the <a href="https://www.w3.org/TR/its/">Internationalization Tag Set (ITS)</a> by promoting its adoption and gathering information for its further development. ITS provides a set of concepts that can be mapped to markup and that make it easier to internationalize and localize documents. The group works through a public list and wiki, and monthy teleconference calls.</p> <p>See the <a href="https://w3c.github.io/i18n-activity/its-ig/" class="eyecatcher">home page</a> for more information. </p> </section> <section id="tests"> <h2>Internationalization Sponsorship Program</h2> <p>The W3C is looking to increase participation and funding so that we can expand our activity beyond the core work. We invite organisations, governments, and all interested stakeholders to support the sponsorship program. For more information, see the <a class="eyecatcher" href="/International/sponsorship/">Sponsorship overview </a></p> </section> <section id="cgs"> <h2>Join a Community Group (CG)</h2> <p>There are also some related Community Groups. New CGs can be started at any time, so you may need to check for new groups from time to time. Note that these are not run by the Internationalization WG. Anyone can join a CG. See the <a href="https://www.w3.org/community/groups/" class="eyecatcher">full list of CGs</a>.</p> </section> <section id="other_ways"> <h2>Other ways to contribute</h2> <ul> <li><a href="https://lists.w3.org/Archives/Public/www-international/">Join the Github discussions</a> Active discussions appear in digests posted to the www-international mailing list.</li> <li><a href="https://github.com/orgs/w3c/projects/92/views/1">Review articles</a> prior to publication and send comments.</li> <li><a href="https://github.com/orgs/w3c/projects/91">Review W3C specifications</a> for internationalization issues, and send comments to the Working Group. See the next subsection for more information about how to go about this.</li> <li><a href="https://w3c.github.io/i18n-activity/textlayout/?filter=type-info-request">Provide information about language or script usage</a> in response to our requests for information.</li> <li><a href="/International/i18n-drafts/nav/languagedev">Track or comment on gaps</a> for use of the Web in your region.</li> <li><a href="/International/i18n-drafts/pages/translation">Translate</a> some of the Internationalization Activity's articles.</li> </ul> <section id="reviews"> <h3>Review a spec</h3> <p>One of the core activities of the Internationalization Working Group is to check specifications for internationalization issues. We are always looking for help with this, and the benefit goes two ways, since you learn about bleeding edge technology while reviewing the spec.</p> <p>We also encourage Working Groups to do their own self-review.</p> <p>The following links may help.</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" title="13">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" title="14">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="translate"> <h3>Translate a resource</h3> <p>Many of our articles have been translated, but there's always more work to do. If you are interested in translating something for us, follow this link:</p> <ul> <li><a href="/International/i18n-drafts/pages/translation">Translation instructions</a></li> </ul> </section> </section> </div> <br style="clear: both;" /> <footer id="thefooter"></footer><script>document.getElementById('thefooter').innerHTML = g.bottomOfPage</script> <script>completePage()</script> </body> </html>