CINXE.COM
W3C I18N Spec Development Techniques
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>W3C I18N Spec Development Techniques</title> <meta name="description" content="Allows you to find articles, tutorials, tests, etc at the W3C Internationalization subsite using lists of tasks." /> <script> var f = { } // AUTHORS should fill in these assignments: f.directory = 'techniques'+'/'; // the path to this file, not including /International or the file name f.filename = 'developing-specs'; // 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 = 'techniques-developing-specs'; // blog search string - usually the filename without extensions f.firstPubDate = '2008-02-11'; // date of the first publication of the document (after review) f.lastSubstUpdate = { date:'2019-03-07', time:'16:47'} // 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:'2019-03-07', time:' 16:47'} // 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 = 'characters'; f.additionalLinks = '' </script> <script src="developing-specs-data/translations.js"> </script> <script src="../javascript/doc-structure/article-dt.js"> </script> <script src="../javascript/boilerplate-text/boilerplate-en.js"></script> <!--TRANSLATORS must change -en in the line above to the subtag for their language!--> <script src="../javascript/doc-structure/sitepage-2022.js"> </script> <script src="../javascript/articletoc-2022.js"></script> <script> console.log(window.location.hash) function initialiseLink () { // add fragids for legacy URLs to all links to orthography descriptions specdevLink = document.querySelector('#specdevLink') specdevLink.href += window.location.hash } </script> <link rel="stylesheet" href="../style/sitepage-2022.css" /> <link rel="stylesheet" href="common/techniques2.css" /> <style>#internal-links { display: none; }</style> <link rel="license" href="#copyright"/> </head> <body> <header> <nav id="mainNavigation"></nav><script>document.getElementById('mainNavigation').innerHTML = mainNavigation</script> </header> <!--section id="sidebarExtras"> </section--> <div class="content"> <h1>Internationalization techniques:<br> Developing specifications</h1> <p id="contentstart">This page has been discontinued. You should now use the document <q>Internationalization Best Practices for Spec Developers</q>. </p> <p>If your URL contains a fragment identifier this link will route you to the appropriate section in that document:</p> <p><a class="highlightLink" id="specdevLink" href="https://www.w3.org/TR/international-specs">Go to Internationalization Best Practices for Spec Developers</a></p> <p>You can still create checklists in that document for use in GitHub issues. <a href="https://w3c.github.io/bp-i18n-specdev/#ghChecklist">Generate the code here</a>.</p> </div> <footer id="thefooter"></footer><script>document.getElementById('thefooter').innerHTML = g.bottomOfPage</script> <script> initialiseLink() completePage() </script> </body> </html>