The article Tagging text with no language was updated to correct that statement that lang=”” is not appropriate for HTML. This was introduced with HTML5.
In addition, various editorial changes were made and the page was reorganized, moving the information about XHTML and XML schema considerations to a new advanced section.
The Cascading Style Sheets (CSS) Working Group has published a Candidate Recommendation of CSS Counter Styles Level 3. It adds new built-in counter styles to those defined in CSS 2.1, but, more importantly, it also allows authors to define custom styles for list markers, numbered headings and other types of generated content.
At the same time, the Internationalization Working Group has updated their Working Draft of Predefined Counter Styles, which provides custom rules for over a hundred counter styles in use around the world. It serves both as a ready-to-use set of styles to copy into your own style sheets, and also as a set of worked examples.
The article Why use the language attribute? received a number small of editorial changes, which have been incorporated into the translated versions.
In addition, the following new paragraph was added to the section ‘Styling Pages':
Other typographic and layout features that are affected by language include line-breaking, justification, and case conversion, and more are coming as the specifications develop.
This paragraph has been added, in English, to the German, Russian and Ukrainian translations of the article. Translators, are asked to please provide a translation of the new paragraph.
The article Declaring language in HTML was changed at the end of May. A noticeable change was the introduction of additional headings, to enable readers to more quickly spot relevant information. Also a new section was added: What if element content and attribute values are in different languages?
German, Spanish, Russian and Ukranian translators are asked to update their translations.
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.
Authoring HTML: Handling Right-to-left Scripts and Authoring HTML: Language declarations have both been updated to a new format that lists do’s and don’ts, but points to existing or new articles for detailed information. This will significantly help in keeping the material up to date in the future as technology changes. The documents have also been thoroughly overhauled to reflect the latest changes and information on
The first document provides advice to content authors using HTML markup and CSS style sheets about how to create pages for languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc. It explains how to create content in right-to-left scripts that builds on but goes beyond the Unicode bidirectional algorithm, as well as how to prepare content for localization into right-to-left scripts.
The second helps content authors specify the language of content, which is useful for a wide number of applications, from linguistically-sensitive searching to applying language-specific display properties. In some cases the potential applications for language information are still waiting for implementations to catch up, whereas in others it is a necessity today. Adding markup for language information to content is something that can and should be done now and as content is first developed. If not, it will be much more difficult to take advantage of any future developments.
This update brings the article in line with recent developments in CSS, and reorganizes the material so that readers can find information more quickly. This led to the article being almost completely rewritten.
The article addresses the question: How do I declare the character encoding of a CSS style sheet?
German, Greek, Spanish, Hebrew, Hungarian, Brazilian Portuguese, Russian, Swedish, Ukrainian and Vietnamese translators are asked to update their translation of this article within the next month, otherwise the translations will be removed per the translation policy, since the changes are substantive.
This update brings the article in line with recent developments in HTML5, and reorganizes the material so that readers can find information more quickly. This led to the article being almost completely rewritten.
The article addresses the question: Which character encoding should I use for my content, and how do I apply it to my content?
German, Spanish, Brazilian Portuguese, Russian, Swedish and Ukrainian translators are asked to update their translation of this article within the next month, otherwise the translations will be removed per the translation policy, since the changes are substantive.
This update brings the article in line with recent developments in HTML5, and de-emphasizes information about legacy formats.
An attempt was also made to organize the material so that readers can find information more quickly, and also de-clutter the essential information by moving edge topics, such as UTF-16 and charset links, down the page. This led to the article being almost completely rewritten.
A new boilerplate and styling has also been applied to the article.
German, Spanish, Russian, Swedish and Ukrainian translators are asked to update their translation of this article within the next month, otherwise the translations will be removed per the translation policy, since the changes are substantive.
Inline markup and bidirectional text in HTML is a major update of the article formerly titled What You Need to Know About the Bidi Algorithm and Inline Markup, and reflects the recent changes in bidi markup in the HTML5 specification.
Technically speaking, the main change is that the dir attribute now isolates text by default with respect to the bidi algorithm. Isolation as a default is the recommendation of the Unicode Standard as of version 6.3.
For the less technical-minded, the main advantage of this change is a much simpler transition for both content authors and browser developers who want reap the benefits of isolation. At the same time, these approaches have good results for existing legacy content.