├── home.md
├── .gitignore
├── .github
└── ISSUE_TEMPLATE
│ ├── formtest
│ ├── other.md
│ ├── ask-a-question.md
│ ├── form_test.md
│ ├── formTest.yml
│ └── add-a-new-gap-analysis-topic.md
├── images
├── syllable.png
└── fig_stack.svg
├── tibt
├── images
│ ├── syllable.png
│ └── fig_stack.svg
├── echidna
├── local.css
└── index.html
├── fonts
└── TibMachUni-1.901.woff
├── gap-analysis
├── echidna-tibt-gap
└── index.html
├── w3c.json
├── LICENCE.md
├── print.css
├── echidna
├── homepage
├── index-data
│ ├── translations.js
│ └── local.css
└── index.html
├── CONTRIBUTING.md
├── local.css
├── script.js
├── EDITING.md
├── README.md
├── index.html
└── charter
├── index.html
└── charter2017.html
/home.md:
--------------------------------------------------------------------------------
1 | README.md
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | *.DS_Store
2 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/formtest:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/images/syllable.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/tlreq/HEAD/images/syllable.png
--------------------------------------------------------------------------------
/tibt/images/syllable.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/tlreq/HEAD/tibt/images/syllable.png
--------------------------------------------------------------------------------
/fonts/TibMachUni-1.901.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/tlreq/HEAD/fonts/TibMachUni-1.901.woff
--------------------------------------------------------------------------------
/gap-analysis/echidna-tibt-gap:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=tibt-gap respec
3 |
--------------------------------------------------------------------------------
/w3c.json:
--------------------------------------------------------------------------------
1 | {
2 | "group": [97249, 72665, 32113]
3 | , "contacts": ["rishida"]
4 | , "repo-type": "note"
5 | , "policy": "restricted"
6 | }
--------------------------------------------------------------------------------
/LICENCE.md:
--------------------------------------------------------------------------------
1 | All documents in this Repository are licensed by contributors
2 | under the
3 | [W3C Document License](http://www.w3.org/Consortium/Legal/copyright-documents).
4 |
5 |
--------------------------------------------------------------------------------
/print.css:
--------------------------------------------------------------------------------
1 | @media print {
2 | #langSwitch {
3 | display: none;
4 | }
5 |
6 | details>summary {
7 | font-size: 110%;
8 | list-style: none;
9 | }
10 | }
--------------------------------------------------------------------------------
/tibt/echidna:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=tibt-lreq respec
3 | local.css
4 | images/syllable.png
5 | images/fig_stack.svg
6 | webfonts/TibMachUni-1.901.woff
7 |
8 |
--------------------------------------------------------------------------------
/echidna:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=tlreq respec
3 | local.css
4 | script.js
5 | fonts/TibMachUni-1.901.woff
6 | images/syllable.png
7 | images/fig_stack.svg
8 |
9 |
--------------------------------------------------------------------------------
/homepage/index-data/translations.js:
--------------------------------------------------------------------------------
1 | var trans = { }
2 |
3 | trans.versions = ['en']
4 |
5 | trans.outofdatetranslations = []
6 |
7 | trans.updatedtranslations = []
8 |
9 | trans.unlinkedtranslations = []
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/other.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Other
3 | about: Please use links or pictures for examples and sources where possible.
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/ask-a-question.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Ask a question
3 | about: Use to ask about how people use the Tibetan language or script.
4 | title: Short_version_of_the_question?
5 | labels: question
6 | assignees: ''
7 |
8 | ---
9 |
10 | Ask_the_question_here_Use_pictures_and_links
11 |
--------------------------------------------------------------------------------
/homepage/index-data/local.css:
--------------------------------------------------------------------------------
1 | table {
2 | border-collapse: collapse;
3 | width: 100%;
4 | }
5 | th {
6 | background-color: #eee;
7 | border: 1px solid #ccc;
8 | }
9 | .date {
10 | white-space:nowrap;
11 | width: 8em;
12 | }
13 | td {
14 | font-size: 90%;
15 | padding: 0 .3em;
16 | border: 1px solid #ccc;
17 | }
18 | .labels {
19 | float: right;
20 | height: 11px;
21 | width: 11px;
22 | border-radius: 2px;
23 | margin: 3px;
24 | font-size: .2em;
25 | color: rgba(0,0,0,0.00);
26 | }
27 | #internal-links {
28 | display: none;
29 | }
30 | .hidden {
31 | display: none;
32 | }
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/form_test.md:
--------------------------------------------------------------------------------
1 | - type: textarea
2 | attributes:
3 | label: Operating System
4 | description: What operating system are you using?
5 | placeholder: Example: macOS Big Sur
6 | value: operating system
7 | validations:
8 | required: true
9 | - type: dropdown
10 | attributes:
11 | label: Version
12 | description: What version of our software are you running?
13 | multiple: false
14 | options:
15 | - label: 1.0.2 (Default)
16 | - label: 1.0.3 (Edge)
17 | validations:
18 | required: true
19 | - type: checkboxes
20 | attributes:
21 | label: Code of Conduct
22 | description: The Code of Conduct helps create a safe space for everyone. We require
23 | that everyone agrees to it.
24 | options:
25 | - label: I agree to follow this project's [Code of Conduct](link/to/coc)
26 | required: true
27 | - type: markdown
28 | attributes:
29 | value: "Thanks for completing our form!"
30 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/formTest.yml:
--------------------------------------------------------------------------------
1 | name: "Form test"
2 | - type: textarea
3 | attributes:
4 | label: Operating System
5 | description: What operating system are you using?
6 | placeholder: Example macOS Big Sur
7 | value: operating system
8 | validations:
9 | required: true
10 | - type: dropdown
11 | attributes:
12 | label: Version
13 | description: What version of our software are you running?
14 | multiple: false
15 | options:
16 | - label: 1.0.2 (Default)
17 | - label: 1.0.3 (Edge)
18 | validations:
19 | required: true
20 | - type: checkboxes
21 | attributes:
22 | label: Code of Conduct
23 | description: The Code of Conduct helps create a safe space for everyone. We require
24 | that everyone agrees to it.
25 | options:
26 | - label: I agree to follow this project's [Code of Conduct](link/to/coc)
27 | required: true
28 | - type: markdown
29 | attributes:
30 | value: "Thanks for completing our form!"
31 |
--------------------------------------------------------------------------------
/tibt/local.css:
--------------------------------------------------------------------------------
1 | @font-face {
2 | font-family: 'Tibetan Machine Uni WF';
3 | font-style: normal;
4 | font-weight: normal;
5 | src: url(webfonts/TibMachUni-1.901.woff);
6 | }
7 |
8 | [lang='bo'] {
9 | font-family: 'Tibetan Machine Uni WF', "Tibetan Machine Uni", Kokonor, "Microsoft Himalaya", sans-serif;
10 | font-size: 22px;
11 | }
12 |
13 |
14 |
15 |
16 |
17 |
18 | /* tlreq specific */
19 |
20 | .large_example {
21 | font-size: 32px;
22 | }
23 | .highlight_bo {
24 | color: red;
25 | }
26 | span[lang=bo], bdi[lang=bo] {
27 | font-size: 28px;
28 | }
29 | #terminology_table td {
30 | border: 1px solid #eee;
31 | }
32 | h3+h3 {
33 | margin-top: 0;
34 | }
35 | .leadin[lang="bo"] {
36 | font-size: 20px;
37 | }
38 | .locations td .ex {
39 | margin-left: 8px;
40 | font-size: 36px;
41 | color: #f00;
42 | }
43 | .locations th {
44 | border: 1px solid #CCC;
45 | vertical-align: middle;
46 | height: 40px;
47 | }
48 | .chartable { line-height: 1.4; }
49 | .chartable td { padding: 8px; border: 1px solid #ddd; }
50 | .chartable td :lang(bo) {
51 | margin-left: 8px;
52 | font-size: 48px;
53 | color: #f00;
54 | }
55 | .ipa {
56 | font-family: doulosipa,"Gentium Plus","Lucida Sans Unicode","Lucida Grande","lucida sans","helvetica",sans-serif;
57 | font-size: 18px;
58 | }
59 | .ipa::before {
60 | content: "/";
61 | font-family: "Helvetica Neue",serif;
62 | margin-right: 1.5px;
63 | }
64 | .ipa::after {
65 | content: "/";
66 | font-family: "Helvetica Neue",serif;
67 | margin-left: 1.5px;
68 | }
69 |
70 |
71 |
72 |
73 |
74 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | ## Contributions
2 |
3 | Contributions to this repository are intended to become part of the Internationalization Interest Group and Internationalization Working Group documents governed by the [Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software). By committing here, you agree to that licensing of your contributions.
4 |
5 | If you are not the sole contributor to a contribution (pull request), please identify all contributors in the pull request comment.
6 |
7 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows:
8 |
9 | ```
10 | +@github_username
11 | ```
12 |
13 | If you added a contributor by mistake, you can remove them in a comment with:
14 |
15 | ```
16 | -@github_username
17 | ```
18 |
19 | If you are making a pull request on behalf of someone else but you had no part in designing the feature, you can remove yourself with the above syntax.
20 |
21 |
22 |
23 | ## Copyright
24 |
25 | Copyright is a very important part of standardization activities. It allows the standards development organization to maintain vendor neutral control over a specification, and thus protect the consensus found within a Working Group.
26 |
27 | In the course of the development of materials within the W3C, Task Force Participants will make contributions. Those contributions will be integrated into the jointly developed work thus creating shared copyright on the Task Force Participant's contribution. Most W3C Specifications contain a section with acknowledgement of contributions.
28 |
29 | Task Force Participants grant to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Task Force Participant's copyrights on his or her contributions, to copy, publish and distribute the contribution under a license of W3C's choosing. Additionally, the Task Force Participant grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, his or her contribution and that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C. Furthermore, the Task Force Participant understands that W3C will be able to exercise all rights as a copyright owner of Task Force Participant's contribution, including enforcement against infringers without additional agreement or notice.
30 |
31 | Nothing in this agreement restricts the Task Force Participant from using their individual contributions as they wish, even if those have later been amalgamated into joint works. Where W3C releases materials under a permissive license such as the W3C Software License or CC-BY, nothing in this agreement should be read to restrict the Task Force Participant from exercising the permissions granted by that license. The Task Force Participant represents that they are legally entitled to grant the above license. If their employer(s) have rights to intellectual property that the Task Force Participant creates that includes the contributions, they represent that they have received permission to make contributions on behalf of that employer or that the employer has waived such rights for the contributions to W3C.
32 |
33 |
34 | ## Decency
35 |
36 | The Task Force Participant will participate in the W3C Group in a decent way. Task Force Participants will refrain from defaming, harassing or otherwise offending other participants. The [Section 3.1 of the Process Document](https://www.w3.org/2015/Process-20150901/#ParticipationCriteria) applies, as does the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).
37 |
38 | The Task Force Participant will refrain from sending unsolicited commercial messages to W3C mailing-lists and other promotional activities for personal matters or for third parties. This is especially required from Task Force Participants sending messages to public W3C Groups.
39 |
--------------------------------------------------------------------------------
/local.css:
--------------------------------------------------------------------------------
1 | @font-face {
2 | font-family: 'Tibetan Machine Uni WF';
3 | font-style: normal;
4 | font-weight: normal;
5 | src: url(fonts/TibMachUni-1.901.woff);
6 | }
7 |
8 | [lang='bo'] {
9 | font-family: 'Tibetan Machine Uni WF', "Tibetan Machine Uni", Kokonor, "Microsoft Himalaya", sans-serif;
10 | font-size: 22px;
11 | }
12 |
13 |
14 |
15 |
16 |
17 |
18 | /* tlreq specific */
19 |
20 | .large_example {
21 | font-size: 32px;
22 | }
23 | .highlight_bo {
24 | color: red;
25 | }
26 | span[lang=bo], bdi[lang=bo] {
27 | font-size: 28px;
28 | }
29 | #terminology_table td {
30 | border: 1px solid #eee;
31 | }
32 | h3+h3 {
33 | margin-top: 0;
34 | }
35 | .leadin[lang="bo"] {
36 | font-size: 20px;
37 | }
38 | .locations td .ex {
39 | margin-left: 8px;
40 | font-size: 36px;
41 | color: #f00;
42 | }
43 | .locations th {
44 | border: 1px solid #CCC;
45 | vertical-align: middle;
46 | height: 40px;
47 | }
48 | .chartable { line-height: 1.4; }
49 | .chartable td { padding: 8px; border: 1px solid #ddd; }
50 | .chartable td :lang(bo) {
51 | margin-left: 8px;
52 | font-size: 48px;
53 | color: #f00;
54 | }
55 | .ipa {
56 | font-family: doulosipa,"Gentium Plus","Lucida Sans Unicode","Lucida Grande","lucida sans","helvetica",sans-serif;
57 | font-size: 18px;
58 | }
59 | .ipa::before {
60 | content: "/";
61 | font-family: "Helvetica Neue",serif;
62 | margin-right: 1.5px;
63 | }
64 | .ipa::after {
65 | content: "/";
66 | font-family: "Helvetica Neue",serif;
67 | margin-left: 1.5px;
68 | }
69 |
70 |
71 |
72 | .char_highlight { color: red; }
73 |
74 | p { line-height: 2em; }
75 |
76 | #character_list_table td {
77 | vertical-align: top;
78 | border: 1px solid #eee;
79 | padding: 0.5em;
80 | }
81 | #character_list_table:lang(bo) {
82 | font-size: 1.75em;
83 | padding: 0.5em;
84 | }
85 | #character_list_table td td {
86 | border: none;
87 | padding: 0.2em;
88 | font-size: 100%;
89 | }
90 | #character_list_table th {
91 | vertical-align: top;
92 | font-weight: normal;
93 | text-align: start;
94 | font-size: 90%;
95 | font-style: italic;
96 | }
97 |
98 |
99 |
100 |
101 |
102 | #langSwitch {
103 | position: fixed;
104 | top: -14px;
105 | z-index: 10000;
106 | top: 100px;
107 | right: 10px;
108 | width: 5em;
109 | text-align: right;
110 | }
111 | #langSwitch button {
112 | background: #FFF none repeat scroll 0% 0%;
113 | border: 1px solid #CCC;
114 | border-radius: 5px;
115 | }
116 |
117 | .punctuation {
118 | border-collapse: collapse;
119 | }
120 | .punctuation td, .punctuation th {
121 | border: 1px solid #ddd;
122 | vertical-align: top;
123 | padding: 5px;
124 | }
125 | .punctuation th.topth:lang(en) {
126 | font-size: 80%;
127 | padding: 5px;
128 | vertical-align: bottom;
129 | text-align: start;
130 | }
131 |
132 | .translateme, .retranslateme {
133 | background-color: #F3F3C3;
134 | }
135 | .checkme {
136 | background-color: #BBEFFC;
137 | }
138 |
139 | a .fig-title {
140 | display: none;
141 | }
142 | a .figno:after {
143 | content: '';
144 | }
145 | ol li {
146 | list-style-type: lower-alpha;
147 | }
148 | ol li li {
149 | list-style-type: decimal;
150 | }
151 | ol li li li {
152 | list-style-type: lower-roman;
153 | }
154 | .hidden {
155 | display: none;
156 | }
157 |
158 | .checkme::before {
159 | content: ' Check this translation: ';
160 | color: coral;
161 | border-left: 4px solid coral;
162 | padding-left: .5em;
163 | }
164 |
165 | .translateme::before {
166 | content: ' Translate this: ';
167 | color: coral;
168 | border-left: 4px solid coral;
169 | padding-left: .5em;
170 | }
171 |
172 | .retranslateme::before {
173 | content: ' (Re)translate this: ';
174 | color: coral;
175 | border-left: 4px solid coral;
176 | padding-left: .5em;
177 | }
178 |
179 |
180 | .figureSub summary {
181 | font-weight: normal;
182 | margin-block-start: -2rem;
183 | font-size: 80%;
184 | cursor: pointer;
185 | text-align: center;
186 | }
187 |
188 |
189 |
190 |
191 |
192 |
193 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Add a new gap-analysis topic
3 | about: Only those in the tlreq group should use this template.
4 | title: Brief_description_of_the_problem
5 | labels: doc:tlreq, gap
6 | assignees: ''
7 |
8 | ---
9 |
10 | This issue is applicable to most_languages.
11 |
12 | Brief_intro_illustrating_the_requirements
13 |
14 | More:
15 | - [requirements_doc]()
16 | - [etc]()
17 |
18 |
19 | IF THIS IS NOT THE ISSUE THAT IS BEING TRACKED BY THE GAP-ANALYSIS PIPELINE, ADD A POINTER TO THAT ISSUE. THE INITIAL BRIEF INTRO SHOULD REMAIN, AND MAY BE TAILORED WITH EXAMPLES RELEVANT TO THIS LANGUAGE. YOU MAY, OPTIONALLY, ALSO ADD OTHER DETAILS BELOW IF THEY ARE SPECIFIC TO THIS LANGUAGE. THEN ADD THIS:
20 |
21 | For more details, see [this GitHub issue](https://github.com/w3c/XXXX/issues/XX), which is being used to track this gap. Please add any discussion there, and not to this issue.
22 |
23 | THEN ADD THESE 2 PARAS TO THE SECOND COMMENT FIELD AND DELETE THE REST OF THIS TEMPLATE.
24 |
25 | _The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document._
26 |
27 | _**Please add any discussion to the GitHub issue being used to track this gap, and not to this issue**_
28 |
29 |
30 |
31 |
32 |
33 | ### The GAP
34 |
35 | Description_of_the_problem_and_summary_of_test_results
36 |
37 | Brief_description_of_what_spec_says_on_the_matter
38 | [shortname](url_to_section) describe_what_it_says
39 |
40 | Gecko, Blink, and Webkit
41 |
42 | More:
43 | - [relevant_issues]()
44 | - [etc]()
45 |
46 |
47 |
48 |
49 | ### Priority
50 | Why_you_chose_the_priority
51 |
52 |
53 |
54 |
55 |
56 |
57 | ### Tests & results
58 |
59 | Interactive test, [assertion](url)
60 | I18n test suite, [section_head](url)
61 |
62 | Summarise_the_results_for_each_major_engine_only_if_useful
63 |
64 |
65 |
66 |
67 |
68 | ### Action taken
69 | Issue, [XXX](url) Closed.
70 |
71 | [Gecko](url) • [Blink](url) • [Webkit](url)
72 |
73 |
74 |
75 |
76 | ### Outcomes
77 | Brief_description_of_developments
78 |
79 |
80 |
81 | TEXT FOR THE SECOND COMMENT FIELD: ADAPT THE LINKS AS NEEDED; IF THE DOCS SPAN REPOS, BOLD THE ONE THAT IS REFERRED TO FROM THE PIPELINE
82 | _The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document. Proposals for changes or discussion of the content can be made by adding comments below this point._
83 |
84 | _Relevant gap analysis documents include:_
85 | _[Adlam](https://www.w3.org/TR/adlm-gap#fragmentid) • [Arabic/Persian](https://www.w3.org/TR/alreq-gap#fragmentid) • [Bengali](https://www.w3.org/TR/beng-gap/#fragmentid) • [Cherokee](https://www.w3.org/TR/cher-gap#fragmentid) • [Chinese](https://www.w3.org/TR/clreq-gap#fragmentid) • [Dutch](https://www.w3.org/TR/latn-nl-gap#fragmentid) • [Ethiopic](https://www.w3.org/TR/elreq-gap#fragmentid) • [French](https://www.w3.org/TR/latn-fr-gap#fragmentid) • [Georgian](https://www.w3.org/TR/geor-gap#fragmentid) • [German](https://www.w3.org/TR/latn-de-gap#fragmentid) • [Greek](https://www.w3.org/TR/grek-gap#fragmentid) • [Gujarati](https://www.w3.org/TR/gujr-gap#fragmentid) • [Hebrew](https://www.w3.org/TR/hebr-gap#fragmentid) • [Hindi](https://www.w3.org/TR/deva-gap#fragmentid) • [Hungarian](https://w3c.github.io/eurlreq/gap-analysis/latn-nl-gap#fragmentid) • [Inuktitut/Cree](https://www.w3.org/TR/cans-iu-cr-gap#fragmentid) • [Japanese](https://www.w3.org/TR/jpan-gap#fragmentid) • [Javanese](https://www.w3.org/TR/java-gap#fragmentid) • [Kashmiri](https://www.w3.org/TR/arab-ks-gap#fragmentid) • [Khmer](https://www.w3.org/TR/khmr-gap#fragmentid) • [Korean](https://www.w3.org/TR/kore-gap#fragmentid) • [Lao](https://www.w3.org/TR/laoo-gap#fragmentid) • [Mongolian](https://www.w3.org/TR/mong-gap#fragmentid) • [N'Ko](https://www.w3.org/TR/nkoo-gap#fragmentid) • [Osage](https://www.w3.org/TR/osge-osa-gap#fragmentid) • [Punjabi](https://www.w3.org/TR/guru-gap#fragmentid) • [Tamil](https://www.w3.org/TR/taml-gap#fragmentid) • [Thai](https://www.w3.org/TR/thai-gap#fragmentid) • [Tibetan](https://www.w3.org/TR/tibt-gap#fragmentid) • [Uighur](https://www.w3.org/TR/arab-ug-gap#fragmentid)_
86 |
87 | SETTING LABELS (delete before submitting)
88 | gap should already be assigned
89 | doc:... should point to each document _in this repo_ where this gap report will appear
90 | i:... should indicate the section in those documents where this will appear
91 | x:blink/gecko/webkit should be set for browser engines that don't resolve the gap (and removed when they do)
92 | x:... language or script related tags should be set for all affected languages
93 | p:... should indicate the priority of this gap
94 |
--------------------------------------------------------------------------------
/script.js:
--------------------------------------------------------------------------------
1 | "use strict";
2 | (() => {
3 | void function() {
4 | const LANG_LIST = ["en", "zh-hans"];
5 | const L10N = {
6 | "en": {
7 | selector: {
8 | "head > title": "Requirements for Tibetan Text Layout and Typography",
9 | "#abstract > h2": "Abstract",
10 | "#toc > ol > li:nth-child(1) > a": "Abstract",
11 | "#sotd > h2": "Status of This Document",
12 | "#toc > ol > li:nth-child(2) > a": "Status of This Document",
13 | "#table-of-contents": "Table of Contents",
14 | ".note-title": "Note"
15 | },
16 | "fig": "Fig. ",
17 | dt: {},
18 | dd: {
19 | "Bug tracker:": 'file a bug (open bugs)'
20 | }
21 | },
22 | "zh-hans": {
23 | selector: {
24 | "head > title": "藏文排版需求",
25 | "#abstract > h2": "\u6458\u8981",
26 | "#toc > ol > li:nth-child(1) > a": "\u6458\u8981",
27 | "#sotd > h2": "\u5173\u4E8E\u672C\u6587\u6863",
28 | "#toc > ol > li:nth-child(2) > a": "\u5173\u4E8E\u672C\u6587\u6863",
29 | "#table-of-contents": "\u5185\u5BB9\u5927\u7EB2",
30 | ".note-title": "\u6CE8"
31 | },
32 | "fig": "\u56FE",
33 | "summary": "\u5173\u4E8E\u6B64\u6587\u6863",
34 | dt: {
35 | "This version:": "\u672C\u7248\u672C\uFF1A",
36 | "History:": "\u5386\u53F2\uFF1A",
37 | "Previous version:": "\u4E0A\u4E00\u7248\uFF1A",
38 | "Latest published version:": "\u6700\u65B0\u53D1\u5E03\u8349\u7A3F\uFF1A",
39 | "Latest editor's draft:": "\u6700\u65B0\u7F16\u8F91\u8349\u7A3F\uFF1A",
40 | "Editors:": "\u7F16\u8F91\uFF1A",
41 | "Former editors:": "\u539F\u7F16\u8F91\uFF1A",
42 | "Participate:": "\u534F\u52A9\u53C2\u4E0E\uFF1A",
43 | "Feedback:": "\u53CD\u9988\uFF1A"
44 | },
45 | dd: {
46 | "Bug tracker:": '\u53CD\u9988\u9519\u8BEF\uFF08\u4FEE\u6B63\u4E2D\u7684\u9519\u8BEF\uFF09'
47 | }
48 | }
49 | };
50 | const $root = document.documentElement;
51 | let $$hidden = [];
52 | function arrayify(obj) {
53 | return Array.from ? Array.from(obj) : Array.prototype.slice.call(obj);
54 | }
55 | function $$(selector) {
56 | return arrayify(document.querySelectorAll(selector));
57 | }
58 | function toggle$rootClass(lang) {
59 | $root.lang = lang === "all" ? "en" : lang;
60 | if (lang === "all") {
61 | $root.classList.add("is-multilingual");
62 | $root.classList.remove("isnt-multilingual");
63 | } else {
64 | $root.classList.remove("is-multilingual");
65 | $root.classList.add("isnt-multilingual");
66 | }
67 | }
68 | function showAndHideLang(lang) {
69 | $$hidden.forEach(function($elmt) {
70 | Object.assign($elmt, { hidden: false });
71 | });
72 | if (lang === "all") {
73 | return;
74 | }
75 | $$hidden = LANG_LIST.filter(function(it) {
76 | return it !== lang;
77 | }).reduce(function(result, it) {
78 | return result.concat($$('[its-locale-filter-list="' + it + '"]'));
79 | }, []).map(function($elmt) {
80 | return Object.assign($elmt, { hidden: true });
81 | });
82 | }
83 | function replaceBoilerplateText(lang) {
84 | const l10n = L10N[lang === "all" ? "en" : lang];
85 | Object.keys(l10n.selector).forEach(function(s) {
86 | $$(s).forEach(function($elmt) {
87 | Object.assign($elmt, { textContent: l10n.selector[s] });
88 | });
89 | });
90 | $$("figcaption, .fig-ref").forEach(function($elmt) {
91 | Object.assign($elmt.firstChild, { textContent: l10n["fig"] });
92 | });
93 | $$("body > div.head > details > summary").forEach(function($summary) {
94 | let originalText = $summary.dataset.originalText || $summary.textContent.trim();
95 | let text = l10n["summary"] || originalText;
96 | if (text) {
97 | $summary.textContent = text;
98 | $summary.dataset.originalText = originalText;
99 | }
100 | });
101 | $$("body > div.head > details > dl > dt").forEach(function($dt) {
102 | let originalText = $dt.dataset.originalText || $dt.textContent.trim();
103 | let text = l10n.dt[originalText] || originalText;
104 | if (text) {
105 | $dt.textContent = text;
106 | $dt.dataset.originalText = originalText;
107 | }
108 | if (originalText === "Bug tracker:") {
109 | $dt.nextElementSibling.innerHTML = l10n.dd["Bug tracker:"];
110 | }
111 | });
112 | }
113 | window.switchLang = function(lang) {
114 | toggle$rootClass(lang);
115 | showAndHideLang(lang);
116 | replaceBoilerplateText(lang);
117 | };
118 | function addLangAttr() {
119 | toggle$rootClass("all");
120 | LANG_LIST.forEach(function(lang) {
121 | $$('[its-locale-filter-list="' + lang + '"]').forEach(function($elmt) {
122 | if (!$elmt.lang) {
123 | $elmt.lang = lang;
124 | }
125 | });
126 | });
127 | }
128 | addLangAttr();
129 | }();
130 | })();
131 |
--------------------------------------------------------------------------------
/EDITING.md:
--------------------------------------------------------------------------------
1 | # Editorial guidelines | 编辑指南
2 | Combining the English and Chinese text in one document makes it much easier to develop and maintain content in both languages in parallel. However, it is important to follow certain steps when creating or editing the source text.
3 |
4 | (Note that the English version will be the authoritative version, since it is more widely accessible to developers around the world.)
5 |
6 | 同時包含英語及漢語的文檔結構使平行開發與內容維護得以化繁為簡。需要注意的是，W3C以英文版本为权威版本，因其更方便让世界各地的开发者閱讀。
7 |
8 | ### Creating or modifying content | 添加或修正内容
9 |
10 | When creating new content, you should always create markup for both English and Chinese versions.
11 |
12 | 添加新的内容文本時，请務必同時建立英文与中文的元素標記。
13 |
14 | For example:
15 | 例如：
16 |
17 | ```html
18 |
The same text in English.
19 |
此為漢語文本。
20 | ```
21 |
22 | If you are able to create text in both English and Chinese, please do so. If you are only able to create text in one language, still create the dual structure in markup, but put the same text in both places. Then add `class="translateme"` to the text that needs translation.
23 |
24 | 若您可以書寫英、中文二種語言，請同時創建這二種語言的文本；若您只能書寫其中一種语言，请保持英、中文的元素標記结构，將单一语言添加在这两段標記中，並為該段落添加`class="translateme"`類別来提醒其他志愿者翻译此段落。
25 |
26 | For example:
27 | 例如：
28 |
29 | ```html
30 |
此為漢語文本。
31 |
此為漢語文本。
32 | ```
33 |
34 | If you change existing text, and if that change requires a change in the parallel translation but you are unable to do so, add `class="translateme"` to the text that needs to be updated.
35 |
36 | 如果您打算修正現有的内容，并且該内容的另一个语言版本需要同时更新翻译，请您更新翻译或添加`class="translateme"`類別，提醒其他志愿者翻译此段落。
37 |
38 | When text highlighted by the `translateme` class is updated, and matches the recent changes in the other language, the class should be removed.
39 |
40 | 当標記為`translateme`類別的高亮文本已被翻译，并且这段翻译与最新修正內容匹配，请移除它的`translateme`類別。
41 |
42 | ### Markup tips | 標記小提示
43 |
44 | Here are some tips on how to maintain the parallel language structure in markup. The principles in these example approaches should be extended to other markup as needed.
45 |
46 | 此文檔以元素標記来维护双重语言結構，下面是一些協助您依此原則進行編輯的小提示。在需要時，請自行擴展各原則中的範例標記。
47 |
48 | - The English text should always come before its corresponding Chinese text.
49 |
50 | 英文内容永遠置於中文内容前方。
51 |
52 | - List elements need `p` elements inside them。
53 |
54 | 列表元素中，請使用`p`元素。
55 |
56 | ```html
57 |
58 |
这是中国的文字。
59 |
这是中国的文字。
60 |
61 | ```
62 |
63 | - Headings should use `span`s for `zh` and `en` versions, and there should be a line break between spans.
64 |
65 | 标题內应以`span`元素来分別包裹`zh`和`en`語言，两者间应有一个换行。
66 |
67 | ```html
68 |
69 | My heading
70 | 我的标题
71 |
72 | ```
73 |
74 | - Attribute `id`s should go on `section` elements, not `h[1-6]` elements.
75 |
76 | 屬性`id`應跟随`section`元素，而非`h[1-6]`元素。
77 |
78 | ```html
79 |
80 |
81 | English heading
82 | 漢語標題
83 |
84 | …
85 | ```
86 |
87 | - Attribute `id`s on `dfn` elements should start with `xxdef`, where `xx` is either `zh` or `en`.
88 |
89 | 在`dfn`元素里的屬性`id`应该以`xxdef`开始，`xx`隨語言的不同作`zh`或`en`。
90 |
91 | ```html
92 |
The term is a technical word.
93 |
这个词汇是一个技术用语。
94 | ```
95 |
96 | - `figcaption`s should use `span`s for the different language versions.
97 |
98 | `figcaption`元素应以`span`元素来标示不同语言。
99 |
100 | ```html
101 |
102 |
103 |
104 |
105 | English caption
106 | 漢語說明
107 |
108 |
109 | ```
110 |
111 | - Use the following markup for Unicode codepoint names:
112 |
113 | 请使用以下標記来表示Unicode碼位名稱：
114 |
115 | ```html
116 | U+3002 IDEOGRAPHIC FULL STOP [。]
117 | ```
118 |
119 | For additional ideas about markup and styling in Internationalization Activity documents, especially wrt inline markup conventions, see .
120 |
121 | 欲了解更多国际化标准计划文档里的標記和样式条约，尤其是wrt行内標記的使用慣例，请查看。
122 |
123 | ## Last-minute Pre-publication edits | 发布前的最后改动备忘录
124 |
125 | **Make the following changes to the respec file before pushing to GitHub:**
126 |
127 | **发布至GitHub前，請对respec文件進行以下改动：**
128 |
129 | 1. in the SoTD, change the link on "latest dated version in /TR" to the location of the document that is about to be published.
130 |
131 | 对SoTD，把「/TR下最新版本」的链接改指向至准备发布的文件路徑。
132 |
133 | 2. Change the path in following code to the same location above:
134 |
135 | 將下列代碼內的路徑指向上述的链接：
136 |
137 | ```html
138 |
139 | ```
140 |
141 | 3. Change `previousPublishDate` to reflect the date of the last publication.
142 |
143 | 把`previousPublishDate`改为上一次发布的日期。
144 |
145 | **Make the following edits to the snapshot of the file that will be published to TR.**
146 |
147 | **对准备发布至TR的版本快照進行以下编辑：**
148 |
149 | 1. Convert the content of the `h1` tag to the following:
150 |
151 | 把`h1`标签的内容改为：
152 |
153 | ```html
154 | Requirements for Tibetan Text Layout
155 | 中文排版需求
156 | ```
157 |
158 | 2. Remove:
159 | 去除：
160 |
161 | ```html
162 |
163 | ```
164 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Tibetan Language Enablement (tlreq)
2 |
3 | This is the place to explore gaps in support for languages using the Tibetan script on the Web and in eBooks, and to document requirements.
4 |
5 | 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.
6 |
7 | Topics for discussion are suggested by [the gap-analysis template](https://www.w3.org/International/i18n-activity/templates/gap-analysis/gap-analysis_template.html). This work feeds into the [language matrix](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) which provides a heat-map for language issues on the Web.
8 |
9 |
10 | ### Key links
11 | [GitHub repo](https://github.com/w3c/tlreq) • [Discussion threads](https://github.com/w3c/tlreq/issues) • [Charter](https://www.w3.org/International/tlreq/charter/)
12 |
13 |
14 | ---
15 | ## Help wanted! ###
16 | **We're looking for information about this writing system. Follow the link for specific questions.**
17 |
18 | **[Tibetan](https://github.com/w3c/tlreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion)**
19 |
20 | ---
21 |
22 |
23 |
24 |
25 |
26 | ### Resource & requirement docs
27 | - **Tibetan Script Resources** • [DNOTE](https://www.w3.org/TR/tibt-lreq) • [*Editor's draft*](https://www.w3.org/International/tlreq/tibt/) • [*Latest commits*](https://github.com/w3c/tlreq/commits/gh-pages/tibt/)
28 | - **Tibetan Layout Requirements** • [DNOTE](https://www.w3.org/TR/tlreq) • [*Editor's draft*](https://www.w3.org/International/tlreq/) • [*Latest commits*](https://github.com/w3c/tlreq/commits/gh-pages/index.html)
29 |
30 |
31 |
32 | ### Gap analysis docs
33 | - **Tibetan Gap Analysis** • [DNOTE](https://www.w3.org/TR/tibt-gap) • [*Editor's draft*](https://www.w3.org/International/tlreq/gap-analysis/) • [*Latest commits*](https://github.com/w3c/tlreq/commits/gh-pages/gap-analysis/index.html)
34 |
35 |
36 |
37 | ### Discussions
38 | - **Tibetan** • [*Questions*](https://github.com/w3c/tlreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion)
39 | • [*Gap reports*](https://github.com/w3c/tlreq/labels/doc%3Atlreq)
40 | • [*Other*](https://github.com/w3c/tlreq/issues?q=is%3Aopen+-label%3Agap+-label%3Aquestion)
41 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Atlreq+label%3Aspec-type-issue)
42 |
43 |
44 |
45 | ### Feedback
46 | Please use the [GitHub issue list](https://github.com/w3c/tlreq/issues) to report issues for language support, for discussions, and to send feedback about documents. (Learn [how GitHub issues work](https://www.w3.org/International/i18n-activity/guidelines/issues.html).)
47 |
48 | Note that the public-i18n-tibetan mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion.
49 |
50 |
51 | ### Participate
52 | 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](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation.html).
53 |
54 | **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-tibetan-request@w3.org?subject=subscribe) to the [public-i18n-tibetan](https://lists.w3.org/Archives/Public/public-i18n-tibetan/) 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 Tibetan writing systems.
55 |
56 | **To contribute content:** All contributors must read and agree with [CONTRIBUTING.md](CONTRIBUTING.md).
57 |
58 | **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests.
59 |
60 | To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation).
61 |
62 |
63 | ### Contacts
64 |
65 | - W3C staff: Chunming Hu, [Richard Ishida](mailto:ishida@w3.org)
66 |
67 |
68 | ### Links
69 | - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-tibetan/)
70 | - [Writing i18n tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests)
71 | - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below)
72 | - [Charter](https://www.w3.org/International/tlreq/charter/)
73 | - Action tracker (tbd)
74 | - Meeting info (tbd)
75 |
76 |
77 | ### Links to background information
78 | The following information describes work going on at the W3C to support languages on the Web.
79 | - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html)
80 | - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev)
81 | - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev)
82 | - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation)
83 | - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project)
84 | - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/)
85 |
86 |
87 | ### Links for editors
88 | **Because the document is bilingual, you need to follow certain steps when creating or modifying the source text.** See [EDITING.md](https://w3c.github.io/tlreq/EDITING) for details.
89 |
90 | If you edit a document, you should be familiar with and use the following:
91 |
92 | - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github)
93 | - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing)
94 |
--------------------------------------------------------------------------------
/homepage/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Tibetan Layout Task Force Home Page
6 |
7 |
8 |
9 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
This task force does gap analysis and documents requirements, related to the layout and presentation of text in languages that use the Tibetan script, in the context of Web standards and technologies such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
We welcome participation requests from people who are interested
74 | in contributing to the work of the Task Force. There are two ways to get involved:
75 |
76 |
Task force members are expert contributors
77 | who participate actively in producing the work of the group, regularly
78 | contributing text and advice to create the outputs, and participating in
79 | meetings. For more information about becoming a task force member
80 | contact Richard Ishida.
81 |
It is also possible to follow and contribute to
82 | discussions without the commitment required in being an expert
83 | contributor. See the github home page for details.
The Tibetan Layout Task Force will not produce
101 | Recommendation-track deliverables but expects to produce Working
102 | Group Notes, published by the Internationalization
103 | Working Group.
104 |
To find and follow progress on deliverables, see the GitHub repo.
Requirements for Tibetan Text Layout
110 | Editor's draft
111 |
112 |
The group charter also allows review of draft specifications
113 | produced by other working groups, and provision of translations of
114 | relevant W3C specifications and resources. The group may also choose to produce other non-normative deliverables,
115 | such as test cases and error reports, under the terms of the Policies
116 | for Contribution of Test Cases to W3C, and in coordination
117 | with any relevant working groups.
Most of the technical discussion takes place in the GitHub issues list. If you want to raise an issue with the documents, this is the place to raise it.
120 |
To follow the work, you can 'Watch' the repository, or subscribe to the public-i18n-tibetan mailing list, which is notified once a day about changes to the repo. The www-international list is also notified daily. (Please use github issues rather than the mailing list to send feedback.) Meeting minutes are sent to public-i18n-tibetan.
There is also a public-tlreq-admin mailing list for internal and administrative use by the TF
124 | participants, for example for announcing teleconference agendas, new
125 | participants, preparing for publication, etc. or for discussing other
126 | non-technical, practical arrangements related to the group. Only
127 | participants in the task force are subscribed to that list.
128 |
The task force aims to hold teleconference or face-to-face
129 | meetings at least once a month, with additional
130 | meetings as needed to enable discussion and review status of the
131 | work.
132 |
The #tlreq IRC channel is used for supplementary communication and minute-taking during meetings. Instructions for use are sent out with the meeting agenda.
133 |
134 |
135 |
136 |
137 |
138 |
139 |
Chair: tbd
140 | Staff contact: Hu Chunming, Richard Ishida
141 | $Id: Overview.html,v 1.77 2010/03/02 12:12:01 rishida Exp $
This document points to resources for the layout and presentation of text in languages that use the Tibetan script. The target audience includes developers of Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode, as well as implementers of web browsers, ebook readers, and other applications that need to render Tibetan text.
52 |
53 |
54 |
55 |
This document points to resources for Tibetan script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications about how to support languages written using the Tibetan script. The information here is developed in conjunction with a document that summarises gaps where the Web fails to adequately support the Tibetan script.
56 |
57 |
🚩
58 |
59 | This document is a stub awaiting future edits. .
60 | See Tibetan Script Resources instead.
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on using a URL.
This document points to resources for Tibetan script layout and text support on the Web and in eBooks. These resources provide information for developers of Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support languages written using the Tibetan script. They include requirements, tests, GitHub discussions, type samples, and more,
101 |
102 |
The document focuses on typographic layout issues. For a deeper understanding of the Tibetan script and how it works see Tibetan Orthography Notes, which includes topics such as:
103 | Phonology,
104 | Vowels,
105 | Consonants,
106 | Encoding choices, and
107 | Numbers.
108 |
Tibetan can be written using two different styles: དབུ་ཅནdbu canwith a head, the block style of the Tibetan script used in print, pronounced u.cen; and དབུ་མེདdbu medheadless, the cursive style of the Tibetan script used in shorthand and calligraphy, pronounced u.me. This page concentrates on the former. Pronunciations are based on the central, Lhasa dialect.
160 |
161 |
Historically, Tibetan text was written on loose-leaf sheets called pechas, ( དཔེ་ཆ pé.t͡ɕʰá book, scripture ). Some of the characters used and formatting approaches are different in books and pechas.
162 |
163 |
164 |
Tibetan text runs left to right in horizontal lines.
165 |
166 |
Words boundaries are not indicated. However, Tibetan words are made up of one or more units called tsheg-bar which are basically equivalent to phonological syllables. The tsheg-bar units are separated using ་ U+0F0B TIBETAN MARK INTERSYLLABIC TSHEG.
167 |
168 |
These tsheg-bar units are composed of structural elements that include vowel signs and consonants used as prefixes, root characters, subscripts, superscripts, suffixes, and secondary suffixes. A common realisation includes a stack and additional consonants to either side of the root consonant. These may indicate syllable-final consonant sounds, but more often than not they qualify or modify the root value, and are not associated with their nominal sound value. The actual pronunciation of Tibetan is usually much more simple than a typical romanisation would suggest. For example, the word བཀོད kǿː to create is transcribed as bkod.
169 |
170 |
171 |
172 |
173 | The single-syllable word cy᷈ː string with an initial stack of three consonants plus a vowel sign. followed by a suffix consonant (to the right).
174 |
175 |
176 |
177 |
178 |
To write the sounds of the standard Lhasa dialect, Tibetan uses 28 consonant letters (plus their subjoined forms). 6 more letters are used to write Sanskrit.
179 |
180 |
A distinguishing feature of Tibetan is the set of separate code points for subjoined consonants, used to create consonant stacks. Of the 77 combining characters in the Tibetan block, 48 represent subjoined consonant forms. Unlike many other Indic scripts, the modern Tibetan orthography doesn't use a virama to create stacks.
181 |
182 |
Tibetan is an abugida with one inherent vowel. When writing the Lhasa dialect, other post-consonant vowels are represented using 4 vowel signs, all combining marks.
183 |
184 |
There are no pre-base, circumgraph, or multipart vowels in the Tibetan used to write the Llasa dialect (though there are when writing in Sanskrit).
185 |
186 |
Standalone vowels are written by adding vowel signs to either འ U+0F60 TIBETAN LETTER -A or ཨ U+0F68 TIBETAN LETTER A, depending on the tone.
187 |
188 |
Sanskrit vowels written in Tibetan use additional vowel signs and combining marks, some of which represent diphthongs, and some of which form circumgraphs or multipart characters, depending on the encoding.
189 |
190 |
Tone is indicated by the choice of root character and/or its associated prefixes and superscripts.
191 |
192 |
Modern Tibetan writing uses few punctuation marks or symbols, but the Tibetan script block in Unicode contains many of these.
The following diagram shows characters in all of the syllabic positions, and lists the characters that can appear in each of the non-root locations. The two-syllable word in the example is འགྲེམས་སྟོན 'grems-ston ɖɹemton exhibition.
Tibetan numerals can be used for list counters. The Tibetan numbers are used in a simple decimal notation, ie. in the same way as European numerals; they differ only in shape.
The mission of this task force is to support the use of the Tibetan script by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications and Unicode. It does this by establishing a network of experts who explore, discuss and document gaps and requirements for the languages in scope.
37 |
In addition to China, especially the Tibet Autonomous Region, the script is widely used in Bhutan, Nepal, India and throughout the Tibetan diaspora. Requirements for these regions are also included in the scope of the document,
38 | and participation in this work by those communities is welcomed.
The output of the task force is pointed to by the International text layout and typography index, and sits alongside similar work for other writing systems. For information about layout and typographic requirements work for other scripts, see Layout & typography.
This charter is intended to reflect the current direction of the group, so that there is common agreement. It may be altered at any point in order to reflect new priorities or work items.
Teleconferences: On an as-needed basis. Preferably, a minimum of one status meeting per month.
69 | Face-to-face meetings: On an as-needed basis.
70 | Video Conferences: On an as-needed basis.
71 |
72 |
73 |
74 |
75 |
76 |
Scope
77 |
The use of the GitHub issue list is not restricted to any particular set of languages other than that the group is focused on languages using the Tibetan script.
78 |
The set of languages for which gap-analysis and requirements documents will be provided will be determined based on the availability of linguistic and typographic experts. Currently, only a draft Tibetan Layout Requirements document is available.
79 |
Document related to additional languages may be added as expertise becomes available.
80 |
81 |
82 |
Deliverables
83 |
The Tibetan Text Layout Task Force will not produce Recommendation-track deliverables but will produce documents that can be published by the Internationalization Working Group as Working Group Notes or articles.
84 |
The group will also assist in developing tests for language features, most of which will be made available via the Internationalization Test Suite, and some of which may be ported to the Web Platform Tests repository.
85 |
The major deliverables of the program are:
86 |
87 |
a network of experts who receive notifications of issues raised in GitHub and respond when needed with advice about requirements for Tibetan-script languages on the Web. It aims to address the problem that experts 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. This network of experts should help to significantly reduce that problem.
88 |
gap-analysis documents focused on specific languages and/or scripts, which describe features that need attention and prioritise them. The gap-analysis document will describe the problems, demonstrate them using tests or screen grabs, and describe whether work is needed on specifications (such as the CSS spec) or implementations (such as major web browsers). This work feeds into the language matrix which provides a heat-map for language issues on the Web.
89 |
requirements documents, which describe in a technology-agnostic way how the script/language works. The requirements documents may be developed piecemeal, to match progress in the gap analysis documents, ie. as a new section is created for the latter, content may be added to the requirements document to indicate the expected result.
90 |
91 |
Note that the requirements document should always remain technology-agnostic, so that it is evergreen. The gap analysis document, however, should be technology-specific, and as issues are addressed parts of the gap analysis document will eventually become merely historical records (and should be labelled as such).
92 |
93 |
118 |
119 |
120 |
121 |
Success Criteria
122 |
123 |
The success of the Task Force will be evaluated based on:
124 |
125 |
the number of experts recruited to participate in or follow discussions
126 |
the number of issues raised and dealt with
127 |
the number of documents produced
128 |
how successful the group is in advancing support for Tibetan languages and scripts on the Web
129 |
130 |
131 |
132 |
133 |
134 |
Relationships to other groups
135 |
136 |
Working Drafts and Notes will be published by the i18n WG, and the i18n WG will work with the task force closely to assist with development and review of the documents.
137 |
138 |
Dependencies
139 |
140 |
W3C Internationalization WG
141 |
The W3C i18n WG will oversee the work of the Task Force, and will
142 | publish the Working Drafts and Notes on their behalf. The i18n WG will also help the Task Force produce work that fits with the work of other Task Forces, and wider initiatives at the W3C.
143 |
144 |
145 |
W3C Publishing Working Group
146 |
The group will work with the Digital Publishing
147 | Working Group to ensure the work it is doing is known to
148 | that group and any issues that are common to the two groups are
149 | identified and tracked appropriately.
150 |
151 |
152 |
The group has no formal dependencies on any
153 | other W3C Working Groups, but important points of contact include:
The Task Force is also expected to take advantage of opportunities for discussion and collaboration with existing groups and communities in Tibetan-speaking countries as well as groups and communities elsewhere.
165 |
166 |
167 |
168 |
169 |
Participation
170 |
171 |
A number of types of participation are possible, ranging from very low commitment (eg. 'Followers') to significant (eg. 'Editors' and 'Chairs'). These are described in a wiki page.
172 |
173 |
The GitHub home page for the group describes how to participate.
174 |
Everyone participating in the work of the task force, be it through the issue list, by contributing content or tests, or any other communication, must do so in conformance with the provisions of the CONTRIBUTING document.
The GitHub issue list is used to report issues for language support, for discussions, and to send feedback about documents.
184 |
The public-i18n-tibetan mailing list is used to send notification digests & meeting minutes. It is not for technical discussion.
185 |
There is also a public-tlreq-admin mailing list for internal and administrative use by the TF participants, for example for announcing teleconference agendas, new participants, preparing for publication, etc. or for discussing other non-technical, practical arrangements related to the group. Only participants in the task force are subscribed to that list.
When there is a quorum of Participants, the task force should aim to hold teleconference or face-to-face meetings at least once a month, with additional meetings as needed to enable discussion and review status of the work. Such meetings have proven to be extremely useful in maintaining the heartbeat of the work.
188 |
The #tlreq IRC channel is used for supplementary communication and for minute-taking during meetings. Instructions for use are sent out with the meeting agenda.
189 |
190 |
191 |
192 |
193 |
Decision Policy
194 |
195 |
As explained in the Process Document (section 3.3),
197 | this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).
198 |
199 |
200 |
201 |
Patent Policy
202 |
203 |
Participants in the Task Force are obligated to comply with W3C patent-disclosure policy as outlined in Section 6 of the W3C Patent Policy document. Although the Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.
This charter for the Task Force within the Internationalization Interest Group is not a formal document and does not require W3C management or Advisory Committee review or approval. It is intended to summarise the goals and procedures of the group at any given time, and can be changed at any time to realign with changed priorities for the group.
212 |
213 |
214 | Charter Authors: Richard Ishida
215 |
216 |
217 |
The mission of this task
39 | force is to document requirements for the layout and
40 | presentation of text in languages written in the Tibetan script,
41 | when those languages are used by Web standards and technologies,
42 | such as HTML, CSS, SVG, Mobile Web, Digital Publications and
43 | Unicode.
44 |
This in an informal charter, and can be changed at any time if the Task Force members are in agreement. It serves to clarify the intended direction of the group.
45 |
In addition to China, especially the Tibet Autonomous Region, the script is widely used in Bhutan, Nepal, India and throughout the Tibetan diaspora. Requirements for these regions are also included in the scope of the document,
46 | and participation in this work by those communities is welcomed.
47 | This task force will gather and integrate feedback from the
48 | participating members about the need for and technical
49 | feasibility of various requirements.
50 |
The Task Force is part of the Internationalization Interest Group.
51 |
The aim of this Task Force is to follow the
52 | example of Requirements
53 | for Japanese Text Layout, Ethiopic Layout Requirements, and Arabic Layout Requirements,
54 | and collect information about specific use cases for technologies
55 | defined in various Web specifications as they relate to the
56 | Tibetan script. The Task Force will report the results of its
57 | activities as a group back to the Internationalization Working Group,
58 | as well as to other relevant groups and to the W3C membership and
59 | community.
Teleconferences: On an as-needed basis. Preferably, a minimum of two status meetings per month.
88 | Face-to-face meetings: On an as-needed basis.
89 | Video Conferences: On an as-needed basis.
90 |
91 |
92 |
93 |
94 |
95 |
Scope
96 |
Primary objective
97 |
The main objective of the task force is to document
98 | typographic and layout requirements for languages using the
99 | Tibetan script. These requirements should be met in Web
100 | standards and technologies, such as HTML, CSS, SVG, and
101 | Digital Publication technologies.
102 |
Use of the Tibetan script extends beyond the Tibetan language.
103 | Although these languages and writing
104 | traditions are important, the initial focus of this Task Force
105 | will be on the usage associated with the Tibetan language. This can be changed at any time, if expert contributors representing other languages are able to contribute to the Task Force.
106 |
Optional additional items
107 |
In addition to those technologies mentioned above, the group may review (but is by no means explicitly limited to reviewing) the following:
108 |
109 |
The work of the Internationalization Working Group.
110 |
CSS3 Modules, in particular:
111 |
112 |
CSS3 Writing Modes Working Draft
113 |
CSS3 Text
114 |
CSS3 Lists
115 |
CSS3 Fonts
116 |
CSS3 Counter Styles
117 |
118 |
119 |
HTML (in particular references to bidi, locale-specific formats, and other internationalization aspects)
120 |
121 |
122 |
Along with reviewing the above mentioned specifications and related specifications, the group will also gather comments and questions about those specifications, collect information about specific use cases affecting the Tibetan script for technologies defined in those specifications or browser implementations, and report the results of its activities as a group back to the Internationalization Working Group, as well as to other relevant groups - such as the HTML Working Group, CSS Working Group, SVG Working Group, and other Working Groups at the W3C as needed. It can also link to discussions about gaps between the requirements and the implementations from the Typography Index maintained by the Internationalization Working Group.
123 |
124 |
Initial set of languages
125 |
Initial set of languages to be covered consists of Tibetan.
126 | Information regarding other languages will be included based
127 | on the availability of linguistic and typographic experts.
128 |
129 |
Deliverables
130 |
Main deliverables
131 |
Target deliverable is the document Tibetan Script Layout
132 | Requirements.
133 |
The Tibetan Layout Task Force will not produce
134 | Recommendation-track deliverables but will produce documents
135 | that can be published by the Internationalization Working
136 | Group as Working Group Notes about text layout and
137 | typography in the Tibetan script.
138 |
Optional deliverables
139 |
The group may also choose to produce other non-normative deliverables, such as test cases and bug reports – under the terms of the Policies for Contribution of Test Cases to W3C, and in coordination with any relevant working groups, browser vendors or application developers.
140 |
Milestones
141 |
142 |
Plans for the main document deliverable are as follows. All deliverables will be made available in English.
143 |
144 |
145 |
146 |
147 |
148 |
149 |
Note: The group will
150 | document significant changes from this initial
151 | schedule on the group home page.
152 |
153 |
154 |
155 |
156 |
Specification
157 |
158 |
FPWD
160 |
WD for final review
162 |
WG Note
164 |
165 |
166 |
Requirements for Tibetan Script Layout and Typography
167 |
168 |
Q2 2017
170 |
Q3 2018
171 |
Q4 2018
172 |
173 |
174 |
175 |
Other deliverables may be produced on an ongoing basis throughout the life of the charter, and the specific topics to be addressed by the task force and schedule information cannot be determined far in advance, but are driven by the needs of the Web community.
176 |
177 |
Success Criteria
178 |
The success of the Task Force will be evaluated based on how
179 | productively it engages with W3C members and the relevant
180 | script communities to promote discussion of specifications
181 | that affect layout and presentation of languages on the Web,
182 | and how effectively it is able to produce additional documents
183 | for the refinement, implementation, and adoption of text
184 | layout and related technologies in Hebrew.
185 |
186 |
187 |
188 |
Relationships to External Groups
189 |
190 |
Working Drafts and Notes will be published by the i18n WG, and the i18n WG will work with the task force closely to assist with development and review of the documents.
191 |
192 |
Dependencies
193 |
194 |
The Tibetan Layout Task Force has no formal
195 | dependencies on any W3C Working Groups other than the
196 | Internationalization Working Group. Important points of
197 | contact are:
The Tibetan Layout Task Force is also expected to take
210 | advantage of opportunities for discussion and collaboration
211 | with existing groups and communities in China as well as
212 | interested groups and communities elsewhere.
213 |
214 |
215 |
216 |
217 |
Participation
218 |
To be successful, the Tibetan Layout Task Force is
219 | expected to have participation or contributions, for its duration, from a
220 | representative section of the typographic and digital text
221 | publishing communities for each of the main languages covered.
222 | Effective participation in the Tibetan Layout Task Force
223 | is expected to consume up to one work day per week for each
224 | participant; two days per week for editors.
People contributing substantive text to the deliverables must be public invited experts or work for W3C member organizations, in order to meet the policy requirements of section 7 of this charter.
229 |
230 |
231 |
232 |
233 |
Communication
234 |
Tibetan Layout Task Force discussions take place via github, teleconferences and email, and face-to-face meetings may be called at locations
235 | that are convenient to participants in the project. Any
236 | publications or other reports eventually contributed by the
237 | Task Force back to the W3C will be made available in English.
238 | (Translations may be produced in addition to the English
239 | version, but the English version will remain the authoritative
240 | version.)
241 |
The task force reaches out to the wider international
242 | community with discussions and announcements in English on the public-i18n-tibetan@w3.org list (archive).
244 |
245 |
246 |
247 |
248 |
249 |
250 | That list will be used for technical discussions, where
251 | necessary, but the group will use github issues to handle most
252 | technical or editorial comments and discussions. The public-i18n-tibetan@w3.org list must archive or point to
253 | minutes and summaries of all teleconferences and face-to-face
254 | meetings. Meeting minutes will list all attendees at a given
255 | meeting.
256 |
An administrative list, public-i18n-tlreq-admin, will also be
257 | used for internal communication about practical matters, such
258 | as meeting agenda, which should be published before each
259 | teleconference or face-to-face meeting.
As explained in the Process Document (section 3.3),
285 | this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).
286 |
287 |
288 |
289 |
Patent Policy
290 |
Participants in the Tibetan Layout Task Force are
291 | obligated to comply with W3C patent-disclosure policy as
292 | outlined in Section
294 |
295 |
296 |
297 |
298 |
299 | 6 of the W3C Patent Policy document. Although the
300 | Tibetan Layout Task Force is not chartered to produce
301 | Recommendation-track documents that themselves require patent
302 | disclosure, participants in the group are nevertheless
303 | obligated to comply with W3C patent-disclosure policy for any
304 | Recommendation-track specifications that they review or
305 | comment on.
This charter for the Tibetan Task Force within the Internationalization Interest Group has been
314 | created according to section 6.2 of the Process Document. In the event of a conflict between this
317 | document or the provisions of any charter and the W3C Process, the W3C Process
318 | shall take precedence.
319 |
320 |
321 | Charter Authors: Richard Ishida, Chunming Hu
322 |
323 |
This document describes and prioritises gaps for the support of the Tibetan script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, such as HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
71 |
72 |
73 |
74 |
75 |
This document describes and prioritises gaps for the support of the Tibetan script 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.
76 | It is linked to from the language matrix that tracks Web support for many languages.
The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.
The W3C needs to make sure that the needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.
116 |
117 |
This page documents difficulties that people encounter when trying to use languages written in the Tibetan script on the Web.
118 |
119 |
Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.
This document not only describes gaps, it also attempts to prioritise them in terms of the impact on the local user. The prioritisation is indicated by colour.
131 |
132 |
Key:
133 |
134 |
135 |
136 |
137 |
138 |
139 |
140 |
141 |
142 |
It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.
143 |
144 |
A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines.
145 |
146 |
Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may be marked as OK. The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide.
147 |
148 |
If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section will be the lowest denominator.
A summary of this report and others can be found as part of the Language Matrix.
161 |
162 |
Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. Find the Tibetan items.
163 |
164 |
For more information about the Tibetan script, including requirements, tests, GitHub discussions, type samples, and more, see Tibetan Script Resources.
Sometimes a script or language does things that are not common outside of its sphere of influence. This is a loose bag of additional items that weren't previously mentioned. This section may also be relevant for observations related to locale formats (such as number, date, currency, format support).
There are many other CSS modules which may need review for script-specific requirements, not to mention the SVG, HTML, Speech, MathML and other specifications. What else is likely to cause problems for worldwide deployment of the Web, and what requirements need to be addressed to make the Web function well locally?
This document describes or points to requirements for the layout and presentation of text in languages that use the Tibetan script. The target audience is developers of Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode, as well as implementers of web browsers, ebook readers, and other applications that need to render Tibetan script text.
61 |
62 |
63 |
64 |
This document describes the basic requirements for Tibetan script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications about how to support users of Tibetan script languages. Currently the document focuses on the Tibetan script as used for Tibetan script. The information here is developed in conjunction with a document that summarises gaps in support on the Web for Tibetan script.
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on using a URL.
69 |
70 |
71 |
72 |
73 |
Some links on this page point to repositories or pages to which information will be added over time. Initially, the link may produce no results, but as issues, tests, etc. are created they will show up.
74 |
75 |
Links that have a gray color led to no content the last time this document was updated. They are still live, however, since relevant content could be added at any time. When the document is updated, links that now point to results will have their live colour restored.
The aim of this document is to describe the basic requirements for Tibetan script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of the Tibetan script.
108 |
109 |
The document focuses on typographic layout issues. For a deeper understanding of Tibetan script using the Tibetan script and how it works see Tibetan Orthography Notes, which includes topics such as: Phonology, Vowels, Consonants, and Numbers.
110 |
111 |
This document should contain no reference to a particular technology. For example, it should not say "CSS does/doesn't do such and such", and it should not describe how a technology, such as CSS, should implement the requirements. It is technology agnostic, so that it will be evergreen, and it simply describes how the script works. The gap analysis document is the appropriate place for all kinds of technology-specific information.
This document should be used alongside a separate document, Tibetan script Gap Analysis, which describes gaps in support for Tibetan script on the Web, and prioritises and describes the impact of those gaps on the user.
To complement any content authored specifically for this document, the sections in the document also point to related, external information, tests, GitHub discussions, etc.
137 |
138 |
The document Language enablement index points to this document and others, and provides a central location for developers and implementers to find information related to various scripts.
139 |
140 |
The W3C also has a repository with discussion threads related to the Tibetan script, including requests from developers to the user community for information about how scripts/languages work, and a notification system that tracks issues in W3C working groups related to the Tibetan script. See a list of unresolved questions for Tibetan script experts. Each section below points to related discussions. See also the repository home page.
Tibetan can be written using two different styles: དབུ་ཅནdbu canwith a head, the block style of the Tibetan script used in print, pronounced u.cen; and དབུ་མེདdbu medheadless, the cursive style of the Tibetan script used in shorthand and calligraphy, pronounced u.me. This page concentrates on the former. Pronunciations are based on the central, Lhasa dialect.
164 |
165 |
Historically, Tibetan text was written on loose-leaf sheets called pechas, ( དཔེ་ཆ pé.t͡ɕʰá book, scripture ). Some of the characters used and formatting approaches are different in books and pechas.
166 |
167 |
168 |
Tibetan text runs left to right in horizontal lines.
169 |
170 |
Words boundaries are not indicated. However, Tibetan words are made up of one or more units called tsheg-bar which are basically equivalent to phonological syllables. The tsheg-bar units are separated using ་ U+0F0B TIBETAN MARK INTERSYLLABIC TSHEG.
171 |
172 |
These tsheg-bar units are composed of structural elements that include vowel signs and consonants used as prefixes, root characters, subscripts, superscripts, suffixes, and secondary suffixes. A common realisation includes a stack and additional consonants to either side of the root consonant. These may indicate syllable-final consonant sounds, but more often than not they qualify or modify the root value, and are not associated with their nominal sound value. The actual pronunciation of Tibetan is usually much more simple than a typical romanisation would suggest. For example, the word བཀོད kǿː to create is transcribed as bkod.
173 |
174 |
175 |
176 |
177 | The single-syllable word cy᷈ː string with an initial stack of three consonants plus a vowel sign. followed by a suffix consonant (to the right).
178 |
179 |
180 |
181 |
182 |
To write the sounds of the standard Lhasa dialect, Tibetan uses 28 consonant letters (plus their subjoined forms). 6 more letters are used to write Sanskrit.
183 |
184 |
A distinguishing feature of Tibetan is the set of separate code points for subjoined consonants, used to create consonant stacks. Of the 77 combining characters in the Tibetan block, 48 represent subjoined consonant forms. Unlike many other Indic scripts, the modern Tibetan orthography doesn't use a virama to create stacks.
185 |
186 |
Tibetan is an abugida with one inherent vowel. When writing the Lhasa dialect, other post-consonant vowels are represented using 4 vowel signs, all combining marks.
187 |
188 |
There are no pre-base, circumgraph, or multipart vowels in the Tibetan used to write the Llasa dialect (though there are when writing in Sanskrit).
189 |
190 |
Standalone vowels are written by adding vowel signs to either འ U+0F60 TIBETAN LETTER -A or ཨ U+0F68 TIBETAN LETTER A, depending on the tone.
191 |
192 |
Sanskrit vowels written in Tibetan use additional vowel signs and combining marks, some of which represent diphthongs, and some of which form circumgraphs or multipart characters, depending on the encoding.
193 |
194 |
Tone is indicated by the choice of root character and/or its associated prefixes and superscripts.
195 |
196 |
Modern Tibetan writing uses few punctuation marks or symbols, but the Tibetan script block in Unicode contains many of these.
The following diagram shows characters in all of the syllabic positions, and lists the characters that can appear in each of the non-root locations. The two-syllable word in the example is འགྲེམས་སྟོན 'grems-ston ɖɹemton exhibition.
173 | 