Comments are being sought on this article prior to final release. Please send any comments to firstname.lastname@example.org (subscribe). We expect to publish a final version in one to two weeks. [search keys: qaaaaa]CATEGORIES: For review ============================================================== Talks available ============================================================== TITLE: New talk slides:
Event: @media conference, London, UK
Richard Ishida gave a [presentation/keynote/tutorial/...] entitled Designing for International Users: Practical Tips on 16 June, 2008. [search keys: talk-2008 talk-ishida]
Repeat above as needed for all speakers/talks
Program and slides
Blogs and press reports
PhotosCATEGORIES: Talks ============================================================== Updated Working Draft ============================================================== TITLE: Updated Working Draft:
The Internationalization Core Working Group has published an updated Working Draft of Internationalization Best Practices: Specifying Language in XHTML & HTML Content. Part of a series designed for authors, the document is an aid to specifying the language of content for an international audience.
The title has been changed to reflect that these are 'Best practises' rather than 'Techniques', and the content and format has been substantially reworked. In particular, the term 'primary language' has been replaced with references to the 'language of the intended audience'.
Editor: Richard Ishida. [search keys: tr-bp-char]CATEGORIES: NEW DRAFT, update, highlight ============================================================== New Working Group Note ============================================================== TITLE: New Working Group Note:
The Internationalization Core Working Group has published Internationalization Best Practices: Specifying Language in XHTML & HTML Content as a Working Group Note.
This document provides best practices related to the practical aspects of specifying the language of content. HTML content authors can use these to ensure that their HTML is easily adaptable for an international audience. These are best practices that are best addressed from the start of content development if unnecessary costs and resource issues are to be avoided later on.
Editor: Richard Ishida. [search keys: tr-i18n-html-tech-lang]CATEGORIES: NEW RESOURCE, highlight ============================================================== Updated test results ============================================================== TITLE: Updated test results: doc_title POST:
These tests check whether and how a user agent displays ruby markup in XHTML 1.0 that is served as text/html (without CSS help).
Tests were conducted on later versions of Firefox, Opera and Safari browsers, and the Firefox browser with a later version of the ruby add-on by Jeroen Ruigrok van der Werven. The latter now passes all tests for simple and complex ruby as expected. There was no change for the three former browser setups. [search key: results-ruby-markup-2]Categories: TESTS, update ============================================================== Updated tests ============================================================== TITLE: Updated tests: doc_title POST:
These tests check whether and how a user agent displays list numbering when the value of the CSS list-style-type property is set to armenian, lower-armenian and upper-armenian.
A number of errors in the tests were corrected and the results page was rewritten to reflect the changes and results for latest versions of major browsers. [search keys: test-list-style-type results-list-style-type]Categories: TESTS, update ====================================================== New tutorial:
The CSS3 modules currently in development will introduce a large number of properties designed to support non-Latin text, from vertical script support to kashida justification, from ruby positioning to list numbering. This tutorial will give you a glimpse of some of the properties that lie in store, and discuss how you can help to make these improvements a reality. This tutorial has been significantly rewritten since its earlier drafts, and has been through a wide review period.
After reading this tutorial you should:
- have a general picture of the types of text control that will be available for non-Latin scripts in CSS3
- understand the status of the work, and what you can do to help move the work forward.