├── .github
└── ISSUE_TEMPLATE
│ ├── add-a-new-gap-analysis-topic.md
│ ├── ask-a-question.md
│ └── other.md
├── .gitignore
├── .pr-preview.json
├── CONTRIBUTING.md
├── README.md
├── charter
└── index.html
├── gap-analysis
├── echidna-java-gap
├── echidna-khmr-gap
├── echidna-laoo-gap
├── echidna-thai-gap
├── java-gap.html
├── javanese-tests
│ ├── javanese_line_break-zwsp.html
│ ├── javanese_line_break.html
│ └── javanese_line_break_textarea.html
├── khmer-tests
│ ├── khmer_letter_space.html
│ └── khmer_line_break.html
├── khmr-gap.html
├── lao-tests
│ ├── lao_line_break.html
│ └── letter-spacing.html
├── laoo-gap.html
├── mymr-gap.html
├── sund-gap.html
├── thai-gap.html
└── thai-tests
│ └── thai_justification.html
├── home.md
├── homepage
├── index-data
│ ├── local.css
│ └── translations.js
└── index.html
├── java
├── echidna
└── index.html
├── javanese
├── images
│ ├── line-break-taling.png
│ └── pangandika.png
├── index.html
└── local.css
├── khmer
├── echidna
├── images
│ ├── font_style_chor.png
│ ├── font_style_chrieng.png
│ └── font_style_mul.png
├── index.html
├── local.css
└── webfonts
│ └── notoserifkhmer-regular-webfont.woff2
├── lao
├── echidna
├── index.html
├── local.css
└── webfonts
│ └── notoseriflao-regular-webfont.woff2
├── thai
├── echidna
├── index-data
│ ├── am_spacing.png
│ ├── am_spacing.svg
│ ├── fig_baselines_angsana.png
│ ├── fig_baselines_freesiaupc.png
│ ├── fig_baselines_noto_sans.png
│ ├── fig_baselines_noto_serif.png
│ ├── fig_baselines_thonburi.png
│ ├── fig_cs_alphabetic.png
│ ├── fig_cs_numeric.png
│ ├── fig_multiple_diacritics.svg
│ ├── fig_shaping.png
│ ├── fig_shaping1.svg
│ ├── fig_shaping2.svg
│ ├── fig_shaping3.svg
│ ├── fig_wide_spacing.png
│ ├── g_program.png
│ ├── g_program.svg
│ ├── g_sacred.png
│ ├── g_sacred.svg
│ ├── g_smell.png
│ ├── g_smell.svg
│ ├── g_toilet.png
│ ├── g_toilet.svg
│ ├── initial_diacritics.jpg
│ ├── initial_e.jpg
│ ├── initial_multiple_diacritics.jpg
│ ├── justification_intercharacter_spacing.jpg
│ ├── justification_para_indent.jpg
│ ├── looped_silom.png
│ ├── loopless_sukhumvitset.png
│ ├── metrics.png
│ ├── multiple_diacritics.png
│ ├── thai_alt1.png
│ ├── thai_alt2.png
│ ├── thai_position.png
│ ├── thai_position.svg
│ ├── thai_words.png
│ └── thai_wrap.png
├── index.html
├── local.css
└── webfonts
│ └── notosansthai-regular-webfont.woff2
└── w3c.json
/.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 sealreq 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 |
--------------------------------------------------------------------------------
/.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 |
--------------------------------------------------------------------------------
/.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 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | *.DS_Store
2 |
--------------------------------------------------------------------------------
/.pr-preview.json:
--------------------------------------------------------------------------------
1 | {
2 | "src_file": "gap-analysis/java-gap.html",
3 | "type": "respec"
4 | }
5 |
--------------------------------------------------------------------------------
/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 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Southeast Asia Language Enablement (sealreq)
2 |
3 | This is the place to explore gaps in support for languages in Southeast Asia 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/sealreq) • [Discussion threads](https://github.com/w3c/sealreq/issues) • [Charter](https://www.w3.org/International/sealreq/charter/)
12 |
13 |
14 |
15 | ---
16 | ### Help wanted! ###
17 | **We're looking for information about these writing systems. Follow the links for specific questions.**
18 |
19 | **[Balinese](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Abali+label%3Aquestion) • [Javanese](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Ajava+label%3Aquestion) • [Khmer](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Akhmr+label%3Aquestion) • [Lao](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Alaoo+label%3Aquestion) • [Myanmar](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Amymr+label%3Aquestion) • [Sundanese](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Asund+label%3Aquestion) • [Thai](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Athai+label%3Aquestion)**
20 |
21 | ---
22 |
23 |
24 |
25 |
26 | ### Resource & requirement docs
27 | - **Lao Script Resources** • [DNOTE](https://www.w3.org/TR/laoo-lreq/) • [*Editor's draft*](https://www.w3.org/International/sealreq/lao/) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/lao/index.html)
28 | - **Thai Script Resources** • [DNOTE](https://www.w3.org/TR/thai-lreq/) • [*Editor's draft*](https://www.w3.org/International/sealreq/thai/) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/thai/index.html)
29 | - **Javanese Script Resources** • [DNOTE](https://www.w3.org/TR/java-lreq/) • [*Editor's draft*](https://www.w3.org/International/sealreq/javanese/) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/javanese/index.html)
30 | - **Khmer Script Resources** • [DNOTE](https://www.w3.org/TR/khmr-lreq/) • [*Editor's draft*](https://www.w3.org/International/sealreq/khmer/) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/khmer/index.html)
31 |
32 |
33 |
34 |
35 | ### Gap-analysis docs
36 | - **Lao Gap Analysis** • [DNOTE](https://www.w3.org/TR/laoo-gap) • [*Editor's draft*](https://www.w3.org/International/sealreq/gap-analysis/laoo-gap) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/gap-analysis/laoo-gap.html)
37 | - **Thai Gap Analysis** • [DNOTE](https://www.w3.org/TR/thai-gap) • [*Editor's draft*](https://www.w3.org/International/sealreq/gap-analysis/thai-gap) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/gap-analysis/thai-gap.html)
38 | - **Khmer Gap Analysis** • [DNOTE](https://www.w3.org/TR/khmr-gap) • [*Editor's draft*](https://www.w3.org/International/sealreq/gap-analysis/khmr-gap) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/gap-analysis/khmr-gap.html)
39 | - **Javanese Gap Analysis** • [DNOTE](https://www.w3.org/TR/java-gap) • [*Editor's draft*](https://www.w3.org/International/sealreq/gap-analysis/java-gap) • [*Latest commits*](https://github.com/w3c/sealreq/commits/gh-pages/gap-analysis/java-gap.html)
40 |
41 |
42 |
43 |
44 | ### Discussions
45 | - **Javanese** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Ajava+label%3Aquestion)
46 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Ajava)
47 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Ajava+-label%3Aquestion)
48 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
49 | - **Khmer** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Akhmr+label%3Aquestion)
50 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Akhmr)
51 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Akhmr+-label%3Aquestion)
52 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
53 | - **Lao** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Alaoo+label%3Aquestion)
54 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Alaoo)
55 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Alaoo+-label%3Aquestion)
56 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
57 | - **Myanmar** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Amymr+label%3Aquestion)
58 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Amymr)
59 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Amymr+-label%3Aquestion)
60 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
61 | - **Sundanese** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Asund+label%3Aquestion)
62 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Asund)
63 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Asund+-label%3Aquestion)
64 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
65 | - **Thai** • [*Questions*](https://github.com/w3c/sealreq/issues?q=is%3Aissue+is%3Aopen+label%3As%3Athai+label%3Aquestion)
66 | • [*Gap reports*](https://github.com/w3c/sealreq/labels/doc%3Athai)
67 | • [*Other*](https://github.com/w3c/sealreq/issues?q=is%3Aopen+label%3As%3Athai+-label%3Aquestion)
68 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Asealreq+label%3Aspec-type-issue)
69 |
70 |
71 |
72 |
73 | ### Related documents
74 | - [Ready-made Counter Styles](https://www.w3.org/TR/predefined-counter-styles/)
75 |
76 |
77 | ### Feedback
78 | Please use the [GitHub issue list](https://github.com/w3c/sealreq/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).)
79 |
80 | Note that the public-i18n-sea mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion.
81 |
82 |
83 | ### Participate
84 | 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).
85 |
86 | **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-sea-request@w3.org?subject=subscribe) to the [public-i18n-sea](https://lists.w3.org/Archives/Public/public-i18n-sea/) 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 Southeast Asian writing systems.
87 |
88 | **To contribute content:** All contributors should read and agree with [CONTRIBUTING.md](CONTRIBUTING.md).
89 |
90 | **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests.
91 |
92 | To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation).
93 |
94 |
95 | ### Contacts
96 | W3C staff: [Richard Ishida](mailto:ishida@w3.org)
97 |
98 |
99 | ### Links to practical information
100 | - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-sea/)
101 | - [Writing i18n tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests)
102 | - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below)
103 | - [Charter](https://w3c.github.io/sealreq/charter/)
104 | - Action tracker (tbd)
105 | - Meeting info (tbd)
106 |
107 |
108 | ### Links to background information
109 | The following information describes work going on at the W3C to support languages on the Web.
110 | - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html)
111 | - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev)
112 | - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev)
113 | - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation)
114 | - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project)
115 | - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/)
116 |
117 |
118 | ### Links for editors
119 | If you end up creating a document, you should be familiar with and use the following:
120 |
121 | - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github)
122 | - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing)
123 |
124 |
--------------------------------------------------------------------------------
/charter/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Southeast Asian Layout Task Force Charter
6 |
8 |
10 |
12 |
16 |
17 |
18 |
19 |
20 |
The mission of this task force is to support the use of languages of Southeast Asia 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.
The output of the task force is pointed to by the Language enablement 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.
67 | Face-to-face meetings: On an as-needed basis.
68 | Video Conferences: On an as-needed basis.
69 |
70 |
71 |
72 |
73 |
74 |
Scope
75 |
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 and scripts used in Southeast Asian
76 |
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, the following are available:
77 |
78 |
Khmer
79 |
Lao
80 |
Thai
81 |
Javanese (Javanese script)
82 |
83 |
Document related to additional languages may be added as expertise becomes available. (Myanmar is discussed in the issues, but does not yet have documents.)
84 |
85 |
86 |
Deliverables
87 |
The Southeast Asian 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.
88 |
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.
89 |
The initial goal is the establishment of a network of experts who receive notifications of issues raised in GitHub and respond when needed with advice about requirements for Southeast Asian 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.
90 |
Depending on the availability of resources, the group will also produce two key types of document:
91 |
92 |
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.
93 |
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.
94 |
95 |
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).
96 |
97 |
122 |
123 |
124 |
125 |
Success Criteria
126 |
127 |
The success of the Task Force will be evaluated based on:
128 |
129 |
the number of experts recruited to participate in or follow discussions
130 |
the number of issues raised and dealt with
131 |
the number of documents produced
132 |
how successful the group is in advancing support for Southeast Asian languages and scripts on the Web
133 |
134 |
135 |
136 |
137 |
138 |
Relationships to other groups
139 |
140 |
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.
141 |
142 |
Dependencies
143 |
144 |
W3C Internationalization WG
145 |
The W3C i18n WG will oversee the work of the Task Force, and will
146 | 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.
147 |
148 |
149 |
W3C Publishing Working Group
150 |
The group will work with the Digital Publishing
151 | Working Group to ensure the work it is doing is known to
152 | that group and any issues that are common to the two groups are
153 | identified and tracked appropriately.
154 |
155 |
156 |
The group has no formal dependencies on any
157 | 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 African countries as well as groups and communities elsewhere.
169 |
170 |
171 |
172 |
173 |
Participation
174 |
175 |
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.
176 |
177 |
The GitHub home page for the group describes how to participate.
178 |
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.
188 |
The public-i18n-sea mailing list is used to send notification digests & meeting minutes. It is not for technical discussion.
189 |
There is also a public-sealreq-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.
192 |
The #sealreq IRC channel is used for supplementary communication and for minute-taking during meetings. Instructions for use are sent out with the meeting agenda.
193 |
194 |
195 |
196 |
197 |
Decision Policy
198 |
199 |
As explained in the Process Document (section 3.3),
201 | 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).
202 |
203 |
204 |
205 |
Patent Policy
206 |
207 |
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.
216 |
217 |
218 | Charter Authors: Richard Ishida
219 |
220 |
221 |
This document describes and prioritises gaps for the support of the Javanese 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.
67 |
68 |
69 |
70 |
71 |
This document describes and prioritises gaps for the support of the Javanese 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.
72 | 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.
112 |
113 |
This page documents difficulties that people encounter when trying to use languages written in the Javanese script on the Web.
114 |
115 |
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.
127 |
128 |
Key:
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
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.
139 |
140 |
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.
141 |
142 |
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.
143 |
144 |
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.
157 |
158 |
Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. Find the Javanese items.
159 |
160 |
For more information about the Javanese script, including requirements, tests, GitHub discussions, type samples, and more, see Javanese 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 and prioritises gaps for the support of the Khmer 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.
66 |
67 |
68 |
69 |
70 |
This document describes and prioritises gaps for the support of the Khmer 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.
71 | 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.
112 |
113 |
This page documents difficulties that people encounter when trying to use languages written in the Khmer script on the Web.
114 |
115 |
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.
127 |
128 |
Key:
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
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.
139 |
140 |
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.
141 |
142 |
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.
143 |
144 |
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).
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 Myanmar 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. This is a preliminary analysis.
74 |
75 |
76 |
77 |
78 |
This document describes and prioritises gaps for the support of the Myanmar 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.
79 |
80 | It is linked to from the language matrix that tracks Web support for many languages.
81 |
This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
Introduction
90 |
91 |
92 |
93 |
94 |
95 |
96 |
Contributors
97 |
98 |
The original version of this document was created by Richard Ishida.
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 people encounter when trying to use the Myanmar 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.
120 |
121 |
A summary of this report and others can be found as part of the language matrix.
This version of the document is a preliminary analysis
134 |
135 |
Gap analysis work usually starts with a preliminary analysis, conducted quickly by one or a small group of experts. Then a more detailed analysis is carried out, involving a wider range of experts. The detailed analysis may involve the development of tests, in order to illustrate issues and track results for browsers. The next phase is ongoing maintenance. It is expected that the resulting document will not be frozen: as gaps are fixed, this should be noted in the document. It is also possible that new gaps are noticed or arise, and they can be added to this document when that happens.
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.
148 |
149 |
Key:
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
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.
160 |
161 |
Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.
162 |
163 |
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. 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 should be the lowest denominator.
164 |
165 |
A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.)
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 and prioritises gaps for the support of Sundanese using the Sundanese 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. This is a preliminary analysis.
74 |
75 |
76 |
77 |
78 |
This document describes and prioritises gaps for the support of Sundanese using the Sundanese 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.
79 |
80 | It is linked to from the language matrix that tracks Web support for many languages.
81 |
This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
Introduction
90 |
91 |
92 |
93 |
94 |
95 |
96 |
Contributors
97 |
98 |
The original version of this document was created by Richard Ishida.
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 people encounter when trying to use the xxx language with the xxx 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.
120 |
121 |
A summary of this report and others can be found as part of the language matrix.
This version of the document is a preliminary analysis
134 |
135 |
Gap analysis work usually starts with a preliminary analysis, conducted quickly by one or a small group of experts. Then a more detailed analysis is carried out, involving a wider range of experts. The detailed analysis may involve the development of tests, in order to illustrate issues and track results for browsers. The next phase is ongoing maintenance. It is expected that the resulting document will not be frozen: as gaps are fixed, this should be noted in the document. It is also possible that new gaps are noticed or arise, and they can be added to this document when that happens.
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.
148 |
149 |
Key:
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
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.
160 |
161 |
Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.
162 |
163 |
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. 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 should be the lowest denominator.
164 |
165 |
A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.)
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 and prioritises gaps for the support of the Thai 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 Thai 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.
113 |
114 |
This page documents difficulties that people encounter when trying to use languages written in the Thai script on the Web.
115 |
116 |
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.
128 |
129 |
Key:
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
139 |
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.
140 |
141 |
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.
142 |
143 |
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.
144 |
145 |
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).
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 task force provides advice on Southeast Asian script support, and may produce gap analysis and requirements documents related to the layout and
72 | presentation of text in languages that use Southeast Asian non-Latin scripts. The work supports Web standards and technologies such as HTML, CSS,
73 | Mobile Web, Digital Publications, and Unicode.
We welcome participation requests from people who are interested
76 | in contributing to the work of the Task Force. There are two ways to get involved:
77 |
78 |
Task force members are expert contributors
79 | who can provide and discuss information related to Southeast Asian scripts. Some of them may participate actively in producing the work of the group, regularly
80 | contributing text and advice to create the outputs, and participating in
81 | meetings. For more information about becoming a task force member
82 | contact Richard Ishida.
83 |
It is also possible to follow and contribute to
84 | discussions without the commitment required in being an expert
85 | contributor. See the github home page for details
For information about layout and typographic requirements work for other scripts, see the page Layout & typography.
100 |
See also the language matrix, which provides an overview of where users have problems using the local features of their script on the Web or in eBooks.
The Southeast Asian Layout Task Force will not produce
107 | Recommendation-track deliverables but may produce Working
108 | Group Notes, published by the Internationalization
109 | Working Group.
110 |
To find and follow progress on deliverables, see the GitHub repo.
111 |
The task force is initial established in order to create a network of experts who can be called upon to provide advice about gaps and requirements for Web users in the non-Latin scripts of Southeast Asia.
112 |
In time, the task force may produce deliverables including the following:
113 |
114 |
Gap analysis reports for several SEA languages/scripts
115 | Template
116 |
Text Layout Requirements for several SEA scripts
117 | Editor's draft
118 |
119 |
The group charter also allows review of draft specifications
120 | produced by other working groups, and provision of translations of
121 | relevant W3C specifications and resources. The group may also choose to produce other non-normative deliverables,
122 | such as test cases and error reports, under the terms of the Policies
123 | for Contribution of Test Cases to W3C, and in coordination
124 | 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.
127 |
To follow the work, you can 'Watch' the repository, or subscribe to the public-i18n-sea 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-sea.
There is also a public-sealreq-admin mailing list for internal and administrative use by the TF
131 | participants, for example for announcing teleconference agendas, new
132 | participants, preparing for publication, etc. or for discussing other
133 | non-technical, practical arrangements related to the group. Only
134 | participants in the task force are subscribed to that list.
135 |
The task force may at some point hold regular teleconference or face-to-face
136 | meetings at least once a month, with additional
137 | meetings as needed to enable discussion and review status of the
138 | work. At the moment, no teleconferences are held.
139 |
The #sealreq IRC channel may be used for supplementary communication and minute-taking during meetings. Instructions for use are sent out with the meeting agenda.
140 |
141 |
142 |
143 |
144 |
145 |
Chair: Richard Ishida
146 | Staff contacts: Richard Ishida
147 |
This document describes requirements for the layout and presentation of text in languages that use the Javanese script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
43 |
44 |
45 |
46 |
This document describes the basic requirements for Javanese 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 the Javanese script. Currently the document focuses on Javanese as used for the Javanese language. The information here is developed in conjunction with a document that summarises gaps in support on the Web for Javanese script.
This document is pointed to by a separate document, Javanese Gap Analysis, which describes gaps in support for Javanese on the Web, and prioritises and describes the impact of those gaps on the user.
63 |
Wherever an unsupported feature is indentified through the gap analysis process, the requirements for that feature need to be documented. This document is where those requirements are described.
64 |
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.
65 |
66 |
67 |
68 |
69 |
Other related resources
70 |
71 |
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.
72 |
The W3C also maintains a tracking system that has links to github issues in W3C repositories. There are separate links for (a) requests from developers to the user community for information about how scripts/languages work, (b) issues raised against a spec, and (c) browser bugs. For example, you can find out what information developers are currently seeking, and the resulting list can also be filtered by script.
73 |
74 |
75 |
76 |
77 |
78 |
Javanese Script Overview
79 |
Javanese is an abugida, ie. consonants carry an inherent vowel sound that is overridden, where needed, using vowel signs. In Javanese, consonants carry an inherent vowel, which can be a or o.
80 |
An orthographic syllable in Javanese can be described as {C F} C {{R}Y} {V{A}} {Z}, where:
81 |
82 |
C is a consonant (or consonant + ◌꦳U+A9B3 JAVANESE SIGN CECAK TELU),
83 |
F is ◌꧀U+A9C0 JAVANESE PANGKON,
84 |
R is◌ꦿU+A9BF JAVANESE CONSONANT SIGN CAKRA,
85 |
Y is ◌ꦾU+A9BE JAVANESE CONSONANT SIGN PENGKAL,
86 |
V is a vowel-sign,
87 |
A is ◌ꦴU+A9B4 JAVANESE VOWEL SIGN TARUNG, and
88 |
Z is one of the syllable-final consonants.
89 |
90 |
The initial consonant cluster may represent a word-initial cluster such as mb, nd, ndh, nj or nng,c eg. ꦩꦧꦸꦫꦸmburuhunting, or it may represent the final consonant of a preceding syllable and the initial consonant of another, eg. ꦲꦏ꧀ꦱꦫhk͓sr (aksara)characters.
91 |
Root words are typically disyllables of the form Cˡ V Cˡ V Cˡ, where Cˡ represents an optional consonant or consonant cluster, and V represents a vowel. Most commonly, this represents CVCVC, followed by CVCCVC.c
The concept of 'word' is difficult to define in any language (see What is a word?). We will treat it as a vaguely-defined but recognisable semantic unit that is typically smaller than a phrase and may comprise one or more syllables.
116 |
Spaces are used in Javanese as phrase separators, but Javanese doesn't separate words in a phrase using visible spaces.
117 |
118 |
119 |
Quotations
120 |
Javanese text may use ꧊U+A9CA JAVANESE PADA ADEG for quotation marks.
121 |
Alternatively, the pair of characters ꧌U+A9CC JAVANESE PADA PISELEH and ꧍U+A9CD JAVANESE TURNED PADA PISELEH may be used.
Like Tibetan, line breaking can occur after any full orthographic syllable. Hyphenation is not used.→g
143 |
Javanese stacks consonants when they occur without intervening vowels, and this stacking occurs across word and syllable boundaries. When breaking a line, these stacks are not split. Similarly, some consonant clusters are rendered with conjoined glyphs, which should also not be broken. This means that line-breaking is done at the boundaries of 'orthographic syllables', rather than phonetic ones.
144 |
The example in the figure below shows the Javanese words pangan and dika. The final n in pangan and the initial di in dika form a stack. The line break opportunity appears just before the stack, which means that the final n in pangan will be wrapped to the next line with the word dika.
145 |
146 |
147 | Line break opportunity between the words pangan and dika (red line) splits the final consonant from pangan.
148 |
149 |
150 |
In some printed material, when a new line begins with ꦺU+A9BA JAVANESE VOWEL SIGN TALING, an additional spacing glyph of the same character is placed at the end of the previous line.
151 |
152 |
153 | An extra taling at the end of the line when the word kawon is split before won.
154 |
155 |
156 |
157 |
158 |
159 |
160 |
161 |
162 |
163 |
164 |
165 |
166 |
167 |
168 |
169 |
198 |
199 |
200 |
Acknowledgements
201 |
202 |
Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).
