Internationalization (i18n) Activity

Making the World Wide Web worldwide!


Group pages

i18n Working Group

MultilingualWeb-LT Working Group

i18n Interest Group

Internationalization Tag Set (ITS) Interest Group

Indic Layout Task Force

Japanese Layout Task Force

Activity Statement

W3C Validator Suite
Includes i18n Checker

Site links

Getting Started
Tasks
Topics
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Resource types
Reviews
Mail archives
Aggregated data
Translation
News by category
News archives
July 2011 (13)
July 2009 (10)
June 2009 (10)
June 2008 (13)

Search for news

Admin

Tag(s): tr-encoding

Posts

Encoding is a Candidate Recommendation

The Encoding specification has been published as a Candidate Recommendation. This is a snapshot of the WHATWG document, as of 4 September 2014, published after discussion with the WHATWG editors. No changes have been made in the body of this document other than to align with W3C house styles. The primary reason that W3C is publishing this document is so that HTML5 and other specifications may normatively refer to a stable W3C Recommendation.

Going forward, the Internationalization Working Group expects to receive more comments in the form of implementation feedback and test cases. The Working Group
believes it will have satisfied its implementation criteria no earlier than 16 March 2015. If you would like to contribute test cases or information about implementations, please send mail to www-international@w3.org.

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:

Last Call draft published for Encoding spec

A Last Call Working Draft of Encoding has been published.

While encodings have been defined to some extent, implementations 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 attempts to fill those gaps so that new implementations do not have to reverse engineer encoding implementations of the market leaders and existing implementations can converge.

The body of this spec is an exact copy of the WHATWG version as of the date of its publication, intended to provide a stable reference for other specifications. We are hoping for people to review the specification and send comments about any technical areas that need attention (see the Status section for details).

Please send comments by 1 July 2014.

Comments Off
Tags:

First public working draft of Encoding published

The Internationalization Working Group has published a First Public Working Draft of Encoding.

While encodings have been defined to some extent, implementations 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 attempts to fill those gaps so that new implementations do not have to reverse engineer encoding implementations of the market leaders and existing implementations can converge.

This is a snapshot of the Encoding Living Standard, as of the date shown on the title page. No changes have been made in the body of the W3C draft other than to align with W3C house styles. The primary reason that W3C is publishing this document is so that HTML5 and other specifications may normatively refer to a stable W3C Recommendation.

Tags:

Copyright © 2014 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.
Questions or comments? ishida@w3.org