back to home

w3c / clreq

Requirements for Chinese Text Layout

789 stars
64 forks
186 issues
HTMLCSSTypeScript

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing w3c/clreq in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/w3c/clreq)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Chinese Language Enablement (clreq) **Languages: English (current)** | **简体中文** | **繁體中文** This is the place to explore gaps in support for the Chinese Simplified and Traditional scripts 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. Key links GitHub repo • Discussion threads • Charter --- Help wanted! **We're looking for information about this writing system. Follow this link for specific questions.** --- Chinese, Simplified & Traditional • **Chinese Script Resources** • DNOTE • *Editor's draft* • *Latest commits* • **Chinese Layout Requirements** • DNOTE • *Editor's draft* • *Latest commits* • **Chinese Gap Analysis** • DNOTE • *Editor's draft* • *Latest commits* • **Discussions** • *Questions* • *Gap reports* • *Other* • *Spec issues* Other documents • Ready-made Counter Styles Feedback 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-chinese mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion. **You may raise issues in Chinese, however any substantive discussions should be summarised in English at some point, so that non-Chinese speakers can follow the rationale and contribute comments.** Participate 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-chinese 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 Chinese writing systems. If you prefer to receive notifications of all discussions for Chinese, Japanese, and Korean languages, subscribe to the public-i18n-cjk mailing list. **To contribute content:** All contributors should read and agree with CONTRIBUTING.md. **To become a participant, editor, or chair:** contact Richard Ishida or 薛富侨 (Fuqiao Xue). We welcome participation requests. To get an idea about what's involved, see Get involved with Language Enablement!. Contacts • Chairs: Yijun CHEN, Eric Q. LIU • W3C staff: Fuqiao Xue, Richard Ishida • Group participants Links to practical information • public-i18n-chinese mail archive • public-i18n-cjk mail archive • Writing i18n tests • Practical tips for task forces (See also the github and editorial guidelines below) • Meeting info • Action tracker (tbd) Links to background information 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 Links for editors If you end up creating a document, you should be familiar with and use the following: **Because the document is multilingual, you need to follow certain steps when creating or modifying the source text. See EDITING.md for details.** • GitHub guidelines for working with i18n documents • Editorial guidelines for working with i18n documents • Editorial guidelines for Hans-Hant Glossary