W3C Internationalization (I18n) Activity - Category: New resource http://www.w3.org/blog/International Home page of W3C's Web Internationalization Activity--resources for increasing accessibility of the Web for worldwide audiences. en-EU hourly 1 2000-01-01T12:00+00:00 New Working Group Note: Requirements for String Identity Matching and String Indexing http://www.w3.org/blog/International/2009/10/01/new_working_group_note_requirements_for__1 2009-10-01T14:35:50Z Richard Ishida Articles On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note. This document is being published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication. The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing. Editor: Martin Dürst. [search keys: tr-charreq] On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note.

This document is being published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication.

The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing.

Editor: Martin Dürst. [search keys: tr-charreq]

]]> New Working Group Note: Authoring HTML: Handling Right-to-left Scripts http://www.w3.org/blog/International/2009/09/08/new_working_group_note_authoring_html_ha 2009-09-08T19:04:17Z Richard Ishida New resource The Internationalization Core Working Group has published Authoring HTML: Handling Right-to-left Scripts as a Working Group Note. This document describes techniques for the use of HTML markup and CSS style sheets when creating content in languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc. It builds on (but also goes beyond) markup needed to supplement the Unicode bidirectional algorithm, and also touches on how to prepare content that will later be localized into right-to-left scripts. Editor: Richard Ishida. [search keys: tr-i18n-html-tech-bidi] The Internationalization Core Working Group has published Authoring HTML: Handling Right-to-left Scripts as a Working Group Note.

This document describes techniques for the use of HTML markup and CSS style sheets when creating content in languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc. It builds on (but also goes beyond) markup needed to supplement the Unicode bidirectional algorithm, and also touches on how to prepare content that will later be localized into right-to-left scripts.

Editor: Richard Ishida. [search keys: tr-i18n-html-tech-bidi]

]]> New language tag specification, RFC 5646, published http://www.w3.org/blog/International/2009/09/07/new_language_tag_specification_rfc_5646_ 2009-09-07T19:51:22Z Richard Ishida Miscellaneous The IETF has published RFC 5646, an update of Tags for Identifying Languages. This specification obsoletes former RFCs 4646, 3066 and 1766. RFC 5646 makes it possible to use over 7,000 three-letter ISO 639-3 language codes, in addition to the 2 letter codes that have been in use for some time. It also introduces 220 'extended language' subtags, mainly for backwards compatibility. It continues to be best to refer to this specification as BCP47. This is a non-changing name and web address that points to the latest relevant RFCs. The Internationalization Working Group at the W3C is working on an article to help users choose language tags, given the various types of subtag that are now available, and the sheer number of subtags. You can look up language and other subtags in the IANA Language Subtag Registry. (Richard Ishida has provided an unofficial tool for searching the registry that also provides advice for choosing subtags, and allows you to partially validate a hyphen-separated language tag.) The IETF has published RFC 5646, an update of Tags for Identifying Languages. This specification obsoletes former RFCs 4646, 3066 and 1766.

RFC 5646 makes it possible to use over 7,000 three-letter ISO 639-3 language codes, in addition to the 2 letter codes that have been in use for some time. It also introduces 220 'extended language' subtags, mainly for backwards compatibility.

It continues to be best to refer to this specification as BCP47. This is a non-changing name and web address that points to the latest relevant RFCs.

The Internationalization Working Group at the W3C is working on an article to help users choose language tags, given the various types of subtag that are now available, and the sheer number of subtags.

You can look up language and other subtags in the IANA Language Subtag Registry.

(Richard Ishida has provided an unofficial tool for searching the registry that also provides advice for choosing subtags, and allows you to partially validate a hyphen-separated language tag.) ]]> New article: Using Unicode controls for bidi text http://www.w3.org/blog/International/2009/07/10/new_article_using_unicode_controls_for_b 2009-07-10T15:22:46Z Richard Ishida New resource Read the article FAQ-based article: If I'm unable to use markup to correctly order bidirectional text, what can I do? By Richard Ishida, W3C. [search key: qa-bidi-unicode-controls] Read the article

FAQ-based article: If I'm unable to use markup to correctly order bidirectional text, what can I do?

By Richard Ishida, W3C. [search key: qa-bidi-unicode-controls]

]]> New Working Group Note: Requirements for Japanese Text Layout (日本語組版処理の要件) http://www.w3.org/blog/International/2009/06/06/new_working_group_note_requirements_for_ 2009-06-06T11:07:18Z Richard Ishida New resource Read the Note This document describes requirements for Japanese layout realized with technologies like CSS, SVG and XSL-FO. For non-Japanese speakers it provides access for the first time to a wealth of detailed and authoritative information about Japanese typesetting. The document is mainly based on a standard for Japanese layout, JIS X 4051 and its authors include key contributors to that standard. However, it also addresses areas which are not covered by JIS X 4051. The document was created by the Japanese Layout Task Force (with participation from four W3C Working Groups, CSS, Internationalization Core, SVG and XSL) A Japanese version is also available. Read the Note

This document describes requirements for Japanese layout realized with technologies like CSS, SVG and XSL-FO. For non-Japanese speakers it provides access for the first time to a wealth of detailed and authoritative information about Japanese typesetting. The document is mainly based on a standard for Japanese layout, JIS X 4051 and its authors include key contributors to that standard. However, it also addresses areas which are not covered by JIS X 4051.

The document was created by the Japanese Layout Task Force (with participation from four W3C Working Groups, CSS, Internationalization Core, SVG and XSL)

A Japanese version is also available.

]]>