├── home.md
├── .gitignore
├── cans
└── echidna
├── cher
└── echidna
├── osge
├── echidna
└── index.html
├── w3c.json
├── gap-analysis
├── echidna-iu-cr-gap
├── images
│ ├── 87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png
│ └── 143437861-3b6ea1c4-2b55-425b-a306-22c1cea738bc.png
├── echidna-osge-osa-gap
├── echidna-chr-gap
├── osge-osa-gap.html
├── iu-cr-gap.html
└── chr-gap.html
├── .github
└── ISSUE_TEMPLATE
│ ├── any-other-issue.md
│ ├── ask-a-question.md
│ └── add-a-new-gap-analysis-topic.md
├── CONTRIBUTING.md
└── README.md
/home.md:
--------------------------------------------------------------------------------
1 | README.md
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | *.DS_Store
2 |
--------------------------------------------------------------------------------
/cans/echidna:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=cans-lreq respec
3 |
--------------------------------------------------------------------------------
/cher/echidna:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=cher-lreq respec
3 |
--------------------------------------------------------------------------------
/osge/echidna:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | index.html?specStatus=DNOTE&shortName=cher-lreq respec
3 |
--------------------------------------------------------------------------------
/w3c.json:
--------------------------------------------------------------------------------
1 | {
2 | "group": [72665, 32113]
3 | , "contacts": "r12a"
4 | , "repo-type": "note"
5 | , "policy": "restricted"
6 | }
--------------------------------------------------------------------------------
/gap-analysis/echidna-iu-cr-gap:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | iu-cr-gap.html?specStatus=DNOTE&shortName=cans-iu-cr-gap respec
3 | images/87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png
4 |
--------------------------------------------------------------------------------
/gap-analysis/images/87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/amlreq/gh-pages/gap-analysis/images/87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png
--------------------------------------------------------------------------------
/gap-analysis/echidna-osge-osa-gap:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | osge-osa-gap.html?specStatus=DNOTE&shortName=osge-osa-gap respec
3 | images/87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png
4 |
--------------------------------------------------------------------------------
/gap-analysis/images/143437861-3b6ea1c4-2b55-425b-a306-22c1cea738bc.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/amlreq/gh-pages/gap-analysis/images/143437861-3b6ea1c4-2b55-425b-a306-22c1cea738bc.png
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/any-other-issue.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Any other issue
3 | about: For comments about the docs, or suggested features.
4 | title: Brief_title_here
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 |
--------------------------------------------------------------------------------
/gap-analysis/echidna-chr-gap:
--------------------------------------------------------------------------------
1 | # ECHIDNA configuration
2 | chr-gap.html?specStatus=DNOTE&shortName=cher-gap respec
3 | images/87327736-5c89f780-c52c-11ea-8d22-7b994925d61a.png
4 | images/143437861-3b6ea1c4-2b55-425b-a306-22c1cea738bc.png
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/ask-a-question.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Ask a question
3 | about: Use to ask about how people use a 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 |
--------------------------------------------------------------------------------
/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 |
--------------------------------------------------------------------------------
/.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 amlreq group should use this template.
4 | title: Brief_description_of_the_problem
5 | labels: 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 | ### Tests & results
57 |
58 | Interactive test, [assertion](url)
59 | I18n test suite, [section_head](url)
60 |
61 | Summarise_the_results_for_each_major_engine_only_if_useful
62 |
63 |
64 |
65 |
66 |
67 | ### Action taken
68 | Issue, [XXX](url) Closed.
69 |
70 | [Gecko](url) • [Blink](url) • [Webkit](url)
71 |
72 |
73 |
74 |
75 | ### Outcomes
76 | Brief_description_of_developments
77 |
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 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Americas Language Enablement (amlreq)
2 |
3 | This is the place to explore gaps in support for languages of the Americas 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 | This page includes links to Latin script information which is maintained in the [eurlreq](https://w3c.github.io/eurlreq/home) repository, since many languages of the Americas are written using the Latin script.
10 |
11 | ---
12 |
13 | ## Help wanted!
14 | **We're looking for information about these scripts. Follow the links to see whether there are outstanding questions.**
15 |
16 | **[Cherokee](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Acher+label%3Aquestion) • [Canadian Syllabics](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Acans+label%3Aquestion) • [Osage](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Aosge+label%3Aquestion) • [Latin](https://github.com/w3c/eurlreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Alatn+label%3Aquestion)**
17 |
18 | ---
19 |
20 |
21 | ### Key links
22 | [GitHub repo](https://github.com/w3c/amlreq) • [Discussion threads](https://github.com/w3c/amlreq/issues) • [Charter](https://www.w3.org/International/amlreq/charter/)
23 |
24 |
25 | ### Resource & requirement docs
26 | - **Cherokee Script Resources** • [DNOTE](https://www.w3.org/TR/cher-lreq) • [*Editor's draft*](https://w3c.github.io/amlreq/cher/) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/cher/)
27 |
28 | - **Canadian Syllabics Script Resources** • [DNOTE](https://www.w3.org/TR/cans-lreq) • [*Editor's draft*](https://w3c.github.io/amlreq/cans/) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/cans/)
29 |
30 | - **Osage Script Resources** • [DNOTE](https://www.w3.org/TR/osge-lreq) • [*Editor's draft*](https://w3c.github.io/amlreq/osge/) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/osge/)
31 |
32 | - **Latin Script Resources** • [DNOTE](https://www.w3.org/TR/latn-lreq) • [*Editor's draft*](https://w3c.github.io/eurlreq/latn/) • [*Latest commits*](https://github.com/w3c/eurlreq/commits/gh-pages/latn/)
33 |
34 |
35 |
36 |
37 |
38 | ### Gap documents
39 | - **Cherokee Gap Analysis** • [DNOTE](https://www.w3.org/TR/cher-gap) • [*Editor's draft*](https://www.w3.org/International/amlreq/gap-analysis/chr-gap) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/gap-analysis/chr-gap.html)
40 |
41 | - **Canadian Syllabics Gap Analysis** • [DNOTE](https://www.w3.org/TR/cans-iu-cr-gap) • [*Editor's draft*](https://www.w3.org/International/amlreq/gap-analysis/iu-cr-gap) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/gap-analysis/iu-cr-gap.html)
42 |
43 | - **Osage Gap Analysis** • [DNOTE](https://www.w3.org/TR/osge-osa-gap) • [*Editor's draft*](https://www.w3.org/International/amlreq/gap-analysis/osge-osa-gap) • [*Latest commits*](https://github.com/w3c/amlreq/commits/gh-pages/gap-analysis/osge-osa-gap.html)
44 |
45 | - **Latin Gap Analysis** • [DNOTE](https://www.w3.org/TR/latn-gap) • [*Editor's draft*](https://www.w3.org/International/eurlreq/gap-analysis/latn-gap) • [*Latest commits*](https://github.com/w3c/eurlreq/commits/gh-pages/gap-analysis/latn-gap.html)
46 |
47 |
48 | ### Discussions
49 | - **Cherokee** • [*Questions*](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3Al%3Achr+label%3Aquestion)
50 | • [*Gap reports*](https://github.com/w3c/amlreq/labels/doc%3Acher)
51 | • [*Other*](https://github.com/w3c/amlreq/issues?q=is%3Aopen+label%3Al%3Achr+-label%3Aquestion+-label%3Agap)
52 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Ascript-cher)
53 | - **Plains Cree** • [*Questions*](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3Al%3Acrk+label%3Aquestion)
54 | • [*Gap reports*](https://github.com/w3c/amlreq/labels/doc%3Acans)
55 | • [*Other*](https://github.com/w3c/amlreq/issues?q=is%3Aopen+label%3Al%3Acrk+-label%3Aquestion+-label%3Agap)
56 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Aamlreq)
57 | - **Inuktitut** • [*Questions*](https://github.com/w3c/script-cans/issues?q=is%3Aissue+is%3Aopen+label%3Al%3Aike+label%3Aquestion)
58 | • [*Gap reports*](https://github.com/w3c/amlreq/labels/doc%3Acans)
59 | • [*Other*](https://github.com/w3c/amlreq/issues?q=is%3Aopen+label%3Al%3Aike+-label%3Aquestion+-label%3Agap)
60 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Ascript-cans)
61 | - **Osage** • [*Questions*](https://github.com/w3c/amlreq/issues?q=is%3Aissue+is%3Aopen+label%3Al%3Aosa+label%3Aquestion)
62 | • [*Gap reports*](https://github.com/w3c/amlreq/labels/doc%3Aosge)
63 | • [*Other*](https://github.com/w3c/amlreq/issues?q=is%3Aopen+label%3Al%3Aosa+-label%3Aquestion+-label%3Agap)
64 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Ascript-osge)
65 |
66 |
67 |
68 | ### Feedback
69 | Please use the [GitHub issue list](https://github.com/w3c/amlreq/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).)
70 |
71 | Note that the [public-i18n-americas](https://lists.w3.org/Archives/Public/public-i18n-americas/) mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion.
72 |
73 |
74 | ### Participate
75 | 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).
76 |
77 | **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-africa-request@w3.org?subject=subscribe) to the [public-i18n-americas](https://lists.w3.org/Archives/Public/public-i18n-americas/) 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 writing systems and languages of the Americas.
78 |
79 | **To contribute content:** All contributors must read and agree with [CONTRIBUTING.md](CONTRIBUTING.md).
80 |
81 | **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests.
82 |
83 | To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation).
84 |
85 |
86 | ### Contacts
87 |
88 | - W3C staff: [Richard Ishida](mailto:ishida@w3.org)
89 |
90 |
91 | ### Links to practical information
92 | - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-americas/)
93 | - [Writing i18n tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests)
94 | - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the links for editors below)
95 | - Action tracker (tbd)
96 | - Meeting info (tbd)
97 |
98 |
99 | ### Links to background information
100 | The following information describes work going on at the W3C to support languages on the Web.
101 | - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html)
102 | - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev)
103 | - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev)
104 | - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation)
105 | - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project)
106 | - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/)
107 |
108 |
109 | ### Links for editors
110 | If you end up creating a document, you should be familiar with and use the following:
111 |
112 | - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github)
113 | - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing)
114 |
--------------------------------------------------------------------------------
/gap-analysis/osge-osa-gap.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | Osage Gap Analysis
8 |
9 |
10 |
11 |
13 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
This document describes and prioritises gaps for the support of the Osage 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.
68 |
69 |
70 |
71 |
72 |
This document describes and prioritises gaps for the support of the Osage 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.
73 | 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.
109 |
110 |
This page documents difficulties that people encounter when trying to use languages written in the Osage script on the Web.
111 |
112 |
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.
124 |
125 |
Key:
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
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.
136 |
137 |
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.
138 |
139 |
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.
140 |
141 |
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.
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).
718 |
719 |
720 |
721 |
722 |
723 |
724 |
725 |
What else?
726 |
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 and prioritises gaps for the support of the Unified Canadian Aboriginal Syllabics script (UCAS) 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.
70 |
71 |
72 |
73 |
74 |
This document describes and prioritises gaps for the support of the Canadian Syllabics 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.
75 | 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.
111 |
112 |
This page documents difficulties that people encounter when trying to use languages written in the Canadian Syllabics script on the Web.
113 |
114 |
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.
126 |
127 |
Key:
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
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.
138 |
139 |
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.
140 |
141 |
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.
142 |
143 |
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.
For more information about the Canadian Syllabics script, including requirements, tests, GitHub discussions, type samples, and more, see Canadian Syllabics 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).
718 |
719 |
720 |
721 |
722 |
723 |
724 |
725 |
What else?
726 |
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 and prioritises gaps for the support of the Cherokee 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.
69 |
70 |
71 |
72 |
73 |
This document describes and prioritises gaps for the support of the Cherokee 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.
74 | 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.
110 |
111 |
This page documents difficulties that people encounter when trying to use languages written in the Cherokee script on the Web.
112 |
113 |
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.
125 |
126 |
Key:
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
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.
137 |
138 |
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.
139 |
140 |
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.
141 |
142 |
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.
155 |
156 |
Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. Find the Cherokee items.
157 |
158 |
For more information about the Cherokee script, including requirements, tests, GitHub discussions, type samples, and more, see Cherokee 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).
734 |
735 |
736 |
737 |
738 |
739 |
740 |
741 |
What else?
742 |
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 points to resources for the layout and presentation of text in languages that use the Osage 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 Osage text.
58 |
59 |
60 |
61 |
This document points to resources for Osage 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 Osage script. The information here is developed in conjunction with a document that summarises gaps where the Web fails to adequately support the Osage 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.
66 |
67 |
68 |
69 |
70 |
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.
71 |
72 |
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.
This document points to resources for Osage 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 Osage script. They include requirements, tests, GitHub discussions, type samples, and more,
109 |
110 |
The document focuses on typographic layout issues. For a deeper understanding of the Osage script and how it works see Osage Orthography Notes, which includes topics such as:
111 | Phonology,
112 | Vowels,
113 | Consonants, and
115 | Numbers.
116 |
This document should be used alongside a separate document, Osage Gap Analysis, which describes gaps in language support for users of the Osage script, and prioritises and describes the impact of those gaps on the user.
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.
142 |
143 |
The W3C also has a repository with discussion threads related to the Osage 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 Osage script. See a list of unresolved questions for Osage experts. Each section below points to related discussions. See also the repository home page.
The Osage script is an alphabet, ie. a writing system in which both consonants and vowels are indicated.
167 |
168 |
Osage text runs left-to-right in horizontal lines. Words are separated by spaces. The script is bicameral. The shapes of the upper and lowercase forms are typically the same.
169 |
170 |
Osage pronunciation has a good deal of allophonic variation built into most sounds in its alphabet, influenced by surrounding sounds or by dialect.
171 |
172 |
Osage has 21 basic consonant letters. It also has letters to represent 5 pre-aspirated sounds but the language-learning curriculum of the Osage Nation doesn't use them, with aim of simplifying the learning experience. Another 3 ejective sounds are written using ʼ U+02BC MODIFIER LETTER APOSTROPHE.
173 |
174 |
This orthography is an alphabet where vowels are written using 10 vowel letters (20 in total), including some diphthongs. Nasalisation is very common and is marked using ◌͘U+0358 COMBINING DOT ABOVE RIGHT.
175 |
176 |
Three other combining marks can be used to indicate vowel length or accent, although they are not commonly used. None of the marks combine with their base characters to form precomposed shapes.