Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Temporary proposed new version of specdev.en.html
- Loading branch information
Showing
1 changed file
with
138 additions
and
0 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 |
|---|---|---|
| @@ -0,0 +1,138 @@ | ||
| <!DOCTYPE html> | ||
| <html lang="en"> | ||
| <head> | ||
| <meta charset="utf-8" /> | ||
| <title>Developer support</title> | ||
| <meta name="description" content="Describes the developer support work of the Internationalization Activity." /> | ||
| <script> | ||
| var f = { } | ||
|
|
||
| // AUTHORS should fill in these assignments: | ||
| f.directory = 'getting-started'+'/'; // the path to this file, not including /International or the file name | ||
| f.filename = 'specdev'; // 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-specdev'; // blog search string - usually the filename without extensions | ||
| f.firstPubDate = '2017-08-07'; // date of the first publication of the document (after review) | ||
| f.lastSubstUpdate = { date:'2017-08-07', time:'12:18'} // 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-01-27', time:'12:18'} // 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="specdev-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 to the subtag for their language!--> | ||
| <script src="../javascript/doc-structure/sitepage.js"> </script> | ||
| <script src="../javascript/articletoc-html5.js"></script> | ||
|
|
||
| <link rel="stylesheet" href="../style/sitepage-2016.css" /> | ||
| <link rel="stylesheet" href="specdev-data/local.css" /> | ||
| <link rel="copyright" href="#copyright"/> | ||
| <style> | ||
| body { font-size: 100%; font-family: Raleway; font-weight: normal; } | ||
| #mainLayout { margin: 0 30% 0 7.5%; } | ||
| </style> | ||
| </head> | ||
|
|
||
| <body> | ||
| <header> | ||
| <nav id="mainNavigation"></nav><script>document.getElementById('mainNavigation').innerHTML = mainNavigation</script> | ||
| </header> | ||
| <h1>Developer support</h1> | ||
|
|
||
|
|
||
| <section id="sidebarExtras"> | ||
| </section> | ||
|
|
||
|
|
||
| <div id="mainLayout"> | ||
| <section> | ||
| <p>An important part of the mission of the Internationalization Activity at the W3C is to support developers by sharing advice and reviewing documents. The developers in question mostly include specification writers and browser implementers. (Content developers are mostly catered for by the Education & outreach work we do.)</p> | ||
| </section> | ||
|
|
||
| <div style="clear: both;"> | ||
|
|
||
| <section id="reference"> | ||
| <h2><a href="#reference">Advice</a></h2> | ||
|
|
||
| <p>If you need internationalization advice you can contact us in a couple of ways.</p> | ||
| <p>If you want advice on a discussion taking place in a GitHub issue thread, the best way to alert us is to add the i18n-tracker label to the issue. We'll be notified. If you have a specific question, add it in a comment. This approach is particularly useful since it keeps discussion threads linked to existing discussions and to appropriate repos. </p> | ||
| <p>Alternatively, technical questions can be sent to <a href="mailto:www-international@w3.org">www-international@w3.org</a>. This is the mailing list of the Internationalization Interest Group.</p> | ||
| </section> | ||
|
|
||
|
|
||
|
|
||
|
|
||
| <section id="resources"> | ||
| <h2><a href="#advice">Resources</a></h2> | ||
|
|
||
| <p>We are trying to write down as much as we can, so that you don't always need to contact us for information.</p> | ||
| <p>The following may be useful:</p> | ||
|
|
||
| <dl> | ||
| <dt> <a class="print" href="https://www.w3.org/International/techniques/developing-specs?collapse">Spec development techniques page</a></dt> | ||
| <dd> | ||
| <p>This page provides do's and dont's for spec developers, with links to explanations and examples, and links to useful documents. The information is arranged so that you can quickly drill down to the information that interests you, and is grouped in a task-oriented way.</p> | ||
| <p>The information in the expandable list is distilled from the document <a href="https://www.w3.org/TR/2020/WD-international-specs-20200529/">Internationalization Best Practices for Spec Developers</a>. You can obtain the same information by using the expandable list or the document.</p> | ||
| </dd> | ||
| <dt> <a class="print" href="https://www.w3.org/standards/techs/i18n#">I18n Notes and WDs</a></dt> | ||
| <dd> | ||
| <p>The Internationalization Activity also published additional documents that provide in-depth coverage of a particular area. The link just above takes you to a complete list of technical reports produced by the Activity, but the following list highlights some particularly useful ones.</p> | ||
| <p><a href="https://www.w3.org/TR/string-meta/">Strings on the Web: Language and Direction Metadata</a>. Describe the best practices for identifying language and base direction for strings that will be used on the Web.</p> | ||
| <p><a href="http://www.w3.org/TR/charmod/">Character Model for the World Wide Web: Fundamentals</a>. Architectural specification providing specification and software developers, and content developers with a common reference for interoperable text manipulation on the World Wide Web. Topics addressed include use of the terms 'character', 'encoding' and 'string', a reference processing model, choice and identification of character encodings, character escaping, and string indexing.. </p> | ||
| <p><a href="https://www.w3.org/TR/charmod-norm/">Character Model for the World Wide Web: String Matching</a>. Provides authors of specifications, software developers, and content developers a common reference on string identity matching on the World Wide Web. Topics include string identity matching and normalization.</p> | ||
| <p><a href="https://www.w3.org/TR/ltli/">Language Tags and Locale Identifiers for the World Wide Web</a>. Best practices for labelling natural language content and locale preferences in document formats, specifications, and implementations on the Web.. </p> | ||
| <p><a href="http://www.w3.org/TR/xml-i18n-bp/">Best Practices for XML Internationalization</a>. A set of guidelines for developing XML documents and schemas that are internationalized properly. Following the best practices describes here allow both the developer of XML applications, as well as the author of XML content to create material in different languages.</p> | ||
| <p><a href="http://www.w3.org/TR/its20/">Internationalization Tag Set (ITS)</a>. Defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS). ITS is designed to be used with schemas to support the internationalization and localization of schemas and documents. An implementation is provided for three schema languages: XML DTD, XML Schema and RELAX NG. </p> | ||
| <p><a href="http://www.w3.org/TR/timezone/">Working with Time Zones</a>. Guidelines for working with time and time zones in applications and document formats. Use cases help developers choose an approach to date and time values that works well with geographically distributed applications. Also provides a vocabulary for talking about time in software, a source of confusion for many developers and content authors on the Web.</p> | ||
| </dd> | ||
|
|
||
| <dt><a class="print" href="https://www.w3.org/International/tests/">Language enablement</a></dt> | ||
| <dd> | ||
| <p>Developers who want to better understand language or writing system features, and what must be taken into account to develop internationalized solutions, can find relevant information using the <a href="http://w3c.github.io/typography/">Language Enablement Index</a>.</p> | ||
| <p>Other useful resources include the <a class="print" href="http://w3c.github.io/i18n-activity/textlayout/">Layout issue tracker</a>, which lists outstanding questions and discussions related to language enablement. Also, the <a href="http://w3c.github.io/type-samples/">Type Samples</a> library provides pictures of typographic features in the wild.</p> | ||
| <p>For more details about the language enablement work of the Activity, see <a href="/International/layout">this separate page</a>.</p> | ||
|
|
||
| </dd><dt><a class="print" href="https://www.w3.org/International/tests/">Tests</a></dt> | ||
| <dd> | ||
| <p>The Internationalization Activity has tests for internationalization features that not look at whether specs are supported in user agents, but also explore how browsers and other user agents handle regional requirements for language support.</p> | ||
| <p>There are two main sets of tests. The i18n test suite conforms to the Web Platform Tests approach, and most of those tests are ported to the WPT repository. There is also a set of test rigs that can be used in an interactive way to rapidly set up and share tests that explore user-agent support for language-related and spec features; these are particularly useful to support gap-analysis during the language enablement work.</p> | ||
| </dd> | ||
| </dl> | ||
| </section> | ||
|
|
||
| </div> | ||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
| <section> | ||
| <h2 id="reviews"><a href="#reviews">Reviews</a></h2> | ||
|
|
||
| <p>Horizontal review of specifications and documents is a key enabler for the W3C's mission to create a "Web for All". Horizontal reviews look at accessibility, privacy, security, device independence, architectural, and, of course, internationalization.</p> | ||
| <p>Working groups wanting to request a review should follow the instructions on the <a href="https://www.w3.org/wiki/DocumentReview">Document Review</a> page.</p> | ||
| <p>We strongly recommend that before requesting a review you <a class="print" href="https://www.w3.org/International/techniques/developing-specs?collapse">do a self-review</a>.</p> | ||
| <p>You can see what i18n reviews are in progress by looking at our <a class="print" href="https://github.com/w3c/i18n-activity/projects/1">Review radar</a>, and you can see what issues we are tracking, grouped by spec, using our <a class="print" href="http://w3c.github.io/i18n-activity/reviews/">Review comment tracker</a> or by looking at our <a href="https://github.com/w3c/i18n-activity/issues/">tracker repository</a> on GitHub.</p> | ||
| </section> | ||
| </div> | ||
|
|
||
|
|
||
| <br style="clear: both;" /> | ||
|
|
||
| <footer id="thefooter"></footer><script>document.getElementById('thefooter').innerHTML = g.bottomOfPage</script> | ||
| <script>completePage()</script> | ||
| </body> | ||
| </html> |