For ideas on what to translate, take look at the list of Articles, best practices & tutorials, select your language at the top right, and look for links that are still in English after the page has refreshed.
To find out how to translate a W3C specification in the http://www.w3.org/TR/ space, see How to Volunteer as a Translator. If you want to translate an article or tutorial in the http://www.w3.org/International space, read the rest of this page.
To translate a tutorial or article from the http://www.w3.org/International/ site, please follow the instructions on this page, and confirm that you agree:
- to the redistribution terms of the W3C document copyright notice. Consequently, your translation may be republished by the W3C or other entities if it is done in compliance with the notice's terms.
- that the W3C may rescind your right to publish or distribute the derivative work if the W3C finds that it leads to confusion regarding the original document's status or integrity. (Source.)
You should not translate the source text of pages displayed on the Web. You need to obtain the PHP source file from Richard Ishida.
Minimal requirements follow. See the I18N translation process page for a detailed description of how your translation will be handled, or detailed instructions if you prefer to do it yourself.
For pages that are in XHTML, please use UTF-8 and valid XHTML that conforms to Appendix C of the XHTML 1.0 specification. For the pages that are in HTML5, please ensure that your translation is valid HTML5 and conforms to the requirements for polyglot HTML5.
Send the completed translation to Richard Ishida (firstname.lastname@example.org) for hosting on the W3C site (where we will use language negotiation). We will check the file before uploading.
The translation text page points to boilerplate text that will be incorporated into the displayed page. This approach will speed up your work, improve consistency, and help ensure that all non-visible text is translated. If there is no such page (ie. we have no translations in this language yet), you will be asked to also send a translation of the English boilerplate text.
If you feel you need to change any markup or style sheet rules, please contact us. Please inform Richard Ishida (email@example.com) if you plan to adapt, rather than just translate, the content during translation.
Do not change any of the PHP code, other than the assignments and any appropriate HTML in the first large PHP block at the top of the page. There are comments in the text to help you identify what to change.
Don't forget to translate hidden text such as the meta description. Links to pages below /International should not start with http://www.w3.org; nor should they end with .html (this is to facilitate language negotiation). Please check that all links work before sending the file for publication.
Before sending us the translated text, please use the translation checklist to check your text.
Richard Ishida will notify the firstname.lastname@example.org list after a translation is uploaded to the W3C International site. He will also add a blog post to the I18n Home Page.
Updated pages. If the English version of a page is updated, a note will be sent to the email@example.com list with information about what changed, and a request for the translator to update their translation. The page will have a banner added to it that says it is out of date, and points to the English original. If the changes are only small additions, such as a new paragraph or a new short section, the English may be added to the translation whlie awaiting an update. For most pages, if no update has been received for the translation within approximately a month of the notification, the translation will be removed.