This is the place to explore gaps in support for European language on the Web and in eBooks, and to document requirements.

We aim to address the problem that local users don't know how to tell the W3C what problems exist for support of their language on the Web, and the W3C doesn't know how to contact people who can help when questions arise.

Topics for discussion are suggested by the gap-analysis template. This work feeds into the language matrix which provides a heat-map for language issues on the Web.

We're looking for information about this writing system. Follow the link for specific questions.

Dutch • French • Georgian • German • Greek • Hungarian

GitHub repo • Discussion threads • Charter.

• Georgian Script Layout Requirements • DNOTE • Editor's draft • Latest commits

• Greek Script Layout Requirements • DNOTE • Editor's draft • Latest commits

• Latin Script Layout Requirements • DNOTE • Editor's draft • Latest commits

• Georgian Gap Analysis • DNOTE • Editor's draft • Latest commits

• Greek Gap Analysis • DNOTE • Editor's draft • Latest commits

• Latin Script Gap Analysis • DNOTE • Editor's draft • Latest commits

• Catalan Gap Analysis • Editor's draft • Latest commits

• Dutch Gap Analysis • DNOTE • Editor's draft • Latest commits

• French Gap Analysis • DNOTE • Editor's draft • Latest commits

• German Gap Analysis • DNOTE • Editor's draft • Latest commits

• Hungarian Gap Analysis • DNOTE • Editor's draft • Latest commits

• Catalan • Questions • Gap reports • Other • Spec issues

• Dutch • Questions • Gap reports • Other • Spec issues

• French • Questions • Gap reports • Other • Spec issues

• Georgian • Questions • Gap reports • Other • Spec issues

• German • Questions • Gap reports • Other • Spec issues

• Greek • Questions • Gap reports • Other • Spec issues

• Hungarian • Questions • Gap reports • Other • Spec issues

• Requirements for Latin Text Layout and Pagination
• Ready-made Counter Styles

Please use the GitHub issue list to report issues for language support, for discussions, and to send feedback about documents. (Learn how GitHub issues work.)

Note that the public-i18n-europe mailing list is used to send notification digests & meeting minutes. It is not for technical discussion.

You can participate in the work at various levels. In order of increasing commitment, these include List subscriber, Participant, Editor, and Chair. Explore the options.

To just follow the work: Rather than 'Watch' this repository, subscribe to the public-i18n-europe mailing list. That list is notified (no more than once a day, and in digest form), about changes to issues in this repository, but also about other W3C Working Group issues related to the European orthographies.

To contribute content: All contributors must read and agree with CONTRIBUTING.md.

To become a participant, editor, or chair: contact Richard Ishida. We welcome participation requests.

To get an idea about what's involved, see Get involved with Language Enablement.

• W3C staff: Richard Ishida

• Mail archive
• Writing i18n tests
• Practical tips for task forces (See also the github and editorial guidelines below)
• Charter
• Action tracker (tbd)
• Meeting info (tbd)

The following information describes work going on at the W3C to support languages on the Web.

• Language support heatmap (matrix)
• Analysing support for text layout on the Web
• Overview of language enablement work in progress
• Get involved with Language Enablement
• Setting up a Gap Analysis Project
• Internationalization Sponsorship Program

If you end up creating a document, you should be familiar with and use the following:

• Github guidelines for working with i18n documents
• Editorial guidelines for working with i18n documents