Internationalization (i18n)

Making the World Wide Web worldwide!


Groups/repos

i18n WG

i18n Interest Group

African LE

Americas LE

Arabic LE

Chinese LE

Ethiopic LE

European LE

Hebrew LE

India LE

Japanese LE

Korean LE

Mongolian LE

SE Asian LE

Tibetan LE

Participate!

Join a Group

Follow the work

Translate a specification or page

International­ization Sponsorship Program

News by category
News archives
July 2011 (13)
July 2009 (10)
June 2009 (10)
June 2008 (13)
Search news

I18n sponsors

APL, Japan The Paciello Group Monotype Alibaba

Monthly Archives: October 2015

Posts

New First Public Working Draft: Internationalization Best Practices for Spec Developers

The Internationalization Working Group has published a First Public Working Draft of Internationalization Best Practices for Spec Developers.

This document provides a checklist of internationalization-related considerations when developing a specification. Most checklist items point to detailed supporting information in other documents. Where such information does not yet exist, it can be given a temporary home in this document. The dynamic page Internationalization Techniques: Developing specifications is automatically generated from this document.

The current version is still a very early draft, and it is expected that the information will change regularly as new content is added and existing content is modified in the light of experience and discussion.

Updated Candidate Recommendation: Encoding

The Encoding Candidate Recommendation has been updated to take into account changes made to the editor’s draft since its initial publication as a Candidate Recommendation. These changes are largely due to issues discovered during implementation. This is a snapshot of the WHATWG document, as of 29 September 2015 and no changes have been made from the original in the body of the document other than to align with W3C house styles.

If you wish to make comments regarding this document, please raise them as github issues against the latest editor’s draft. Only send comments by email to www-international@w3.org if you are unable to raise issues on github. All comments are welcome.

The utf-8 encoding is the most appropriate encoding for interchange of Unicode, the universal coded character set. Therefore for new protocols and formats, as well as existing formats deployed in new contexts, this specification requires (and defines) the utf-8 encoding.

The other (legacy) encodings have been defined to some extent in the past. However, user agents have not always implemented them in the same way, have not always used the same labels, and often differ in dealing with undefined and former proprietary areas of encodings. This specification addresses those gaps so that new user agents do not have to reverse engineer encoding implementations and existing user agents can converge.

Tags:

Proposed Update UTR #50, Unicode Vertical Text Layout

A Proposed Update of UTR #50 is now available for public review and comment. The UTR is being reissued with a set of data updated to the character repertoire of Unicode Version 8.0. In this revision, four characters are added to the arrows tailoring set. For details on the proposed changes in the data, please refer to the Modifications section in the UTR.

For information about how to discuss this Public Review Issue and how to supply formal feedback, please see the PRI #309 page.

Tags: ,

Best Practices for working with Multilingual Linked Data

The BPMLOD community group has published three best practices for working with Multilingual Linked Data. The best practices are around bilingual dictionariesmultilingual dictionaries and multilingual terminologies. The BPMLOD group will continue to work on further best practices related to other types of language resources.

Tags:

Copyright © 2023 World Wide Web Consortium.
W3C® liability, trademark and permissive license rules apply.

Questions or comments? ishida@w3.org