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

Category: For review

Posts

First Public Working Draft: Korean Layout Gap Analysis

This document describes and prioritises gaps for the support of Korean language on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

The first public working draft is published to encourage users and experts to review the information it currently contains, and provide any additional information that may be relevant to supporting users of the Korean language on the Web.

We are looking for expert contributors who can help us move this work forward by answering questions, documenting other gaps in support, and creating tests. For more information about the program, see this 15 minute overview (slides), and see the Language Enablement overview page.

Comments Off on First Public Working Draft: Korean Layout Gap Analysis
Tags:

For review: N’Ko Layout Requirements

N’Ko Layout Requirements is out for wide review in preparation for publishing as a First Public Working Draft. We are looking for comments by Wednesday 3 May.

The N’Ko script is used for a West African koiné register of Manding (called Kángbɛ).

The document describes requirements for the layout and presentation of text in Web standards and technologies such as HTML, CSS, & Digital Publications. It supports the N’Ko Gap Analysis.

Please send any comments as github issues.

Tags:
Categories: afrlreq, For review

For review: Working with source code markup and code examples for RTL scripts

The article Working with source code markup and code examples for RTL scripts is out for wide review. We are looking for comments by Wednesday 26 April.

Editing markup for pages in Arabic, Hebrew, and many other languages poses challenges unless a specialized editor is available. For similar reasons, it is also difficult to include examples of bidirectional code in explainers. This page looks at some of the problems content developers and implementers of editors are likely to be faced with, and offers some advice, where possible.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (That will add some useful information to your comment.)

Categories: afrlreq, alreq, For review, hlreq

For review: Font styles & font fallback

The article Font styles & font fallback is out for wide review. We are looking for comments by Thursday 3 November.

This article provides a non-exhaustive set of examples where choice of a font style may have a practical application. The existence of these distinct styles, with their practical influence on the reading of the text, has implications for fonts on the Web – you would typically want to choose a fallback font that has the same style, if one is available. We look at some implications for generic fonts and fallback mechanisms near the end.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (That will add some useful information to your comment.)

For review: Ruby Styling

The article Ruby Styling is out for wide review. We are looking for comments by Thursday 14 July.

The article reviews the typical usage patterns of inline annotations for Japanese and Simplified/Traditional Chinese, and provides guidance for content authors about how to use features of the CSS Ruby spec to achieve the rendering they want. It also reports on current support for those features in the 3 major browser engines. This information should also be useful for authors writing in the Traditional Mongolian orthography.

This is a companion article to Ruby Markup, which focuses on how to mark up inline annotations.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

Categories: clreq, For review, jlreq, mlreq

For review: RTL rendering of LTR scripts

The article RTL rendering of LTR scripts is out for wide review. We are looking for comments by Thursday 7 July.

The article suggests ways to produce runs of right-to-left text using HTML & CSS for languages that are nowadays normally written left-to-right. The use cases for this are rare, and mostly relate to academic descriptions of text in orthographies such as Chinese, Japanese, Egyptian hieroglyphs, Tifinagh, Old Norse runes, and a good number of other now-archaic scripts.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

Categories: afrlreq, clreq, For review, jlreq

Kashmiri & Uighur Gap-analysis, First Public Working Drafts published

The W3C Internationalization Activity has just published First Public Working Drafts for 2 more documents that explore gaps in language support on the World Wide Web.

We are looking for expert contributors who can help us move this work forward by answering questions, documenting other gaps in support, and creating tests. For more information about the program, see this 15 minute overview (slides), and see the Language Enablement overview page.

Comments Off on Kashmiri & Uighur Gap-analysis, First Public Working Drafts published

First Public Working Draft published: Developing Localizable Manifests

A First Public Working Draft of Developing Localizable Manifests has been published.

This document provides definitions and best practices related to the specification of manifest files and similar document formats on the Web.

Some specifications on the Web deal with defining sets of files or resources to be consumed together. A common design pattern is to provide a manifest or configuration file that defines which resources are available and how various resources should be used or to provide various kinds of metadata about a collection of resources.

The document is still at a very early stage, and shows the intent, rather than reliable detail. Public comments are welcome, please raise them as github issues.

New First Public Working Draft: Internationalization Glossary

The W3C Internationalization Activity has published a first public working draft of an Internationalization Glossary. This document provides or points to definitions for various terms related to W3C internationalization.

As well as adding new terms, we plan to point to related definitions in other locations as the document evolves.

Please send any comments to the GitHub issues list.

For review: Structural markup and right-to-left text in HTML

The article Structural markup and right-to-left text in HTML is out for wide review. We are looking for comments by Thursday 13 May.

This article looks at ways of handling text direction for structural markup in HTML, ie. at the document level and for elements like paragraphs, tables and forms. The article has been largely rewritten to take into account recent developments in HTML and CSS. A section was added to describe the use of logical properties. The text was make more concise.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

Tags:
Categories: For review

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

Questions or comments? ishida@w3.org