This group is planned, but not yet active. It will exist to explore gaps and requirements for support of languages using the Tibetan script on the Web and in eBooks.
It aims to address the problem that experts often don't know how to tell the W3C what problems exist for support of their script on the Web, and the W3C often doesn't know how to contact people who can help when questions arise.
Some experts may go a step further, and contribute to a gap-analysis or requirements document.
Topics for discussion are suggested by the gap-analysis template. This work feeds into the language matrix which gives an overview of languages needing attention.
Please use the GitHub issue list to report issues for language support, for discussions, and to send feedback about documents.
Rather than just 'Watch' this repository, it is best to subscribe to the public-i18n-tibetan mailing list. That list is notified once a day (in digest form) about not only changes to this repository, but also about other W3C Working Group issues related to the traditional Tibetan writing systems. (Please use github issues rather than the mailing list to send feedback.) Meeting minutes are also sent to public-i18n-mongolian.
You can find a list of open issues, including those from W3C Working Groups, on the Layout Tracker page. (That link applies an tibetan filter.)
All contributors should read and agree with CONTRIBUTING.md.
Group members are expert contributors who participate actively in producing the work of the group, regularly contributing text and advice to create the outputs, and participating in meetings. For more information about becoming a task force member contact Richard Ishida. We welcome participation requests.
Editors should be familiar with and use the following:
- Github guidelines for working with i18n documents
- Editorial guidelines for working with i18n documents
- Issue tracker
- Github issues
- Home Page
- Charter (tbd)
- Action tracker (tbd)
- Writing i18n tests
- Practical tips for task forces (See also the github and editorial guidelines below)
- Meeting info (tbd)
- Mail archive
- Contacts: Chunming Hu, Richard Ishida
Because the document is bilingual, you need to follow certain steps when creating or modifying the source text. See EDITING.md for details.
If you edit 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
The following templates are available:
The following information describes work going on at the W3C to support languages on the Web.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent