├── .github
└── ISSUE_TEMPLATE
│ ├── add-a-new-gap-analysis-topic.md
│ ├── ask-a-question.md
│ └── other.md
├── .gitignore
├── AbyssinicaSIL-Regular.woff
├── AbyssinicaSIL-WOFF-metadata.xml
├── AbyssinicaSIL-webfont-elreq.css
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENCE.md
├── README.md
├── charter
└── index.html
├── echidna
├── ethi
├── echidna
└── index.html
├── ethiopic-lists.css
├── gap-analysis
├── echidna-elreq-gap
└── index.html
├── home.md
├── homepage
├── index-data
│ ├── local.css
│ └── translations.js
└── index.html
├── images
├── English-Ethiopic-Relative-Heights-2.png
├── English-Ethiopic-Relative-Heights-3.png
├── English-Ethiopic-Relative-Heights-4.png
├── English-Ethiopic-Relative-Heights-With-Guide-Lines.png
├── English-Ethiopic-Relative-Heights.png
├── EthiopicWhiteSpace-2016.vsd
├── Ethiopicized-Punctuation-Sample-260.png
├── Ethiopicized-Punctuation-Sample-HalfSize.png
├── GeezMargins.png
├── Kerning-Examples.png
├── Ligature-Examples.png
├── Punctuation-At-Latin-Boundary-Ethiopic-Guillemets.png
├── Punctuation-At-Latin-Boundary-Ethiopic-Quotes.png
├── Punctuation-At-Latin-Boundary-Latin-Guillemets.png
├── Punctuation-At-Latin-Boundary-Latin-Quotes.png
├── Sebatbeit-Glyph-Preferences.png
├── Superscript-Vertical-Alignment.png
├── Z-N-Alignment.png
├── Z-Ny-N-Shoulder-Aligned.png
├── Z-Ny-N-Top-Aligned.png
├── Z-Reference-Abyssinica.png
├── Z-Reference-Monotype.png
├── Z-caron-Ny-Z-N-Alignment.png
├── ZN-Superscript.png
├── circle-bullet-size-samples.png
├── corpus-samples
│ ├── Alweledim-Page-87-Cropped.png
│ ├── KWK-Page-159-Cropped.png
│ ├── KWK-Page-65-Cropped.png
│ ├── Nebiy-Mohammed-Page-35-Cropped.png
│ └── Ografi-Page-35-Cropped.png
├── diamond-bullet-size-samples.png
├── ecclesiastical-emphasis-sample-cropped.jpg
├── end-of-list-inline-continuation.png
├── gemination-heights-comparison.png
├── heavy-underline-example.png
├── inline-list-with-space.png
├── inline-list-with-wordspace.png
├── inline-list.png
├── isolated-and-joining-numeral-bars.png
├── justification_centered.png
├── justification_full_mashafa_sawasew.png
├── justification_in_historia_aethiopica.png
├── justification_mashafa_sawasew.png
├── justification_sample_with_12pt.png
├── justification_sample_with_spaces.png
├── justification_word_bounded.png
├── kwk-mashafa-sawasew-page-268-typeface-change-for-emphasis.jpg
├── kwk-mashafa-sawasew-page-65-inner-parenthesis-one-line.png
├── kwk-mezgebe-fidel-page-43-font-size-increase-for-emphasis.png
├── list-aligned-on-counter-left.png
├── list-aligned-on-suffix.png
├── numeral-vertical-alignment.png
├── page-number-in-two-systems.png
├── raised-ellipsis.png
├── semi_justification.png
├── square-bullet-size-samples.png
├── white_space_round_wordspace.png
└── wordspace_with_comma.png
├── index.html
├── local.css
├── references
├── EthiopicTypographyQuestions-20071209.pdf
├── View and Recommendation on Issues Raised for Ethiopic Typesetting.docx
└── View and Recommendation on Issues Raised for Ethiopic Typesetting.pdf
├── style-guide
├── FormattingSurveyQuestions.html
├── images
│ ├── list-aligned-on-counter-left.png
│ └── list-aligned-on-suffix.png
└── index.html
├── survey
├── ELREQ-Survey-1-A4-English.docx
├── ELREQ-Survey-1-A4-English.pdf
├── ELREQ-Survey-2-A4-English.docx
└── ELREQ-Survey-2-A4-English.pdf
├── w3c.json
└── zaima
├── SupportingZaimaInBrowsers.html
├── WhatIsZaima.html
├── ZaimaAsciiTables.html
├── ZaimaInterlinear.html
├── ZaimaModel.html
├── ZaimaPlaypen-Chrome60.html
├── ZaimaPlaypen.html
├── ZaimaStylingUseCases-20171006.pdf
├── ZaimaStylingUseCases-20171024.pdf
├── ZaimaUseCases-Chrome60.html
├── ZaimaUseCases.html
├── images
├── AquaquamZewerhaBealat-Page113.jpg
├── DiguaPage5-Sample.jpg
├── ProjectedLayers.png
├── SeparateLayers.png
├── ZaimaChantNotionalModel.png
└── ZaimaModel3Rows.png
├── index.html
├── use-cases
├── MerhaLiqawntPage127i2.png
├── MerhaLiqawntPage128.2.png
├── MerhaLiqawntPage128i1.png
├── MerhaLiqawntPage23i3.png
├── MerhaLiqawntPage66i1.png
├── MerhaLiqawntPage84i3.png
├── MerhaLiqawntPage84i6.png
├── MerhaLiqawntPages12i1.png
├── SelotKidasiePage103i1.png
├── SelotKidasiePage113i1.png
├── SelotKidasiePage129i2.png
├── SelotKidasiePage145i1.png
├── SelotKidasiePage189i1.png
├── SelotKidasiePage213i1.png
├── SelotKidasiePage253i1.png
├── SelotKidasiePage83i2.png
├── SelotKidasiePage9i2.png
├── ZimarieWemewasitPage68i4-600dpi.png
├── ZimarieWemewasitPageSecondHalf34i1-600dpi.png
└── ZimarieWemewasitPageSecondHalf34i2-600dpi.png
├── zaima-chrome60.css
├── zaima-chrome61.css
├── zaima-gloss.css
└── zaima.css
/.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 elreq group should use this template.
4 | title: Brief_description_of_the_problem
5 | labels: doc:ethi, 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 |
--------------------------------------------------------------------------------
/AbyssinicaSIL-Regular.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/w3c/elreq/a3cd6b269b22b38b317b33315f86722ca58b3e7a/AbyssinicaSIL-Regular.woff
--------------------------------------------------------------------------------
/AbyssinicaSIL-WOFF-metadata.xml:
--------------------------------------------------------------------------------
1 |
2 |
14 |
15 |
16 |
17 |
18 |
22 |
26 |
30 |
33 |
36 |
39 |
42 |
43 |
44 |
45 | Abyssinica SIL is based on Ethiopic calligraphic traditions. This release is a
46 | regular typeface, with no bold or italic version available or planned.
47 |
48 | The goal for this product was to provide a single Unicode-based font
49 | that would contain a comprehensive inventory of glyphs needed for almost any
50 | Ethiopic-based writing system. In addition, there is provision for other
51 | Latin characters and symbols. This font makes use of state-of-the-art font
52 | technologies to support the need to position arbitrary combinations of
53 | *Ethiopic* base glyphs and combining marks optimally. It also supports
54 | almost 200 kerning pairs. This version of the font also supports Stylistic
55 | Sets and Character Variants (OpenType) or Features (Graphite) which make
56 | glyph alternates available for a number of Ethiopic and punctuation
57 | characters. See the AbyssinicaSILOpenTypeFontFeatures.pdf,
58 | AbyssinicaSILGraphiteFontFeatures.pdf and AbyssinicaSILTypeTunerGuide.pdf
59 | for details on applications which support Stylistic Sets and how to access them.
60 |
61 | One font from this typeface family is included in this release:
62 |
63 | * Abyssinica SIL Regular
64 |
65 | For detailed documentation see the contents of the 'documentation' folder.
66 |
67 |
68 | ChangeLog
69 | ---------
70 | (This should list both major and minor changes, most recent first.)
71 |
72 | 9 June 2021 (WSTech Team) Abyssinica SIL version 2.100
73 | - Added U+1E7E0..U+1E7E6, U+1E7E8..U+1E7EB, U+1E7ED..U+1E7EE, U+1E7F0..U+1E7FE
74 | - Modified a few kerning pairs and added kerning pairs for some of the new characters
75 | - Changed Latin digits (for use in Ethiopic) to use a serif style
76 | - Modified Ethiopic digits to have a more consistent size
77 | - Added cv02 to support digits with connecting above and below lines
78 |
79 | 11 September 2019 (Sharon Correll) Abyssinica SIL version 2.000
80 | - Added U+02D0, U+034F, U+2423, U+25CA
81 | - Improved design of U+1256 so the top flag touches
82 | - Improved design of U+1368 to fit the design of the font better
83 | - Improved design of U+1362 (extra space to the right)
84 | - Added language support for Sebat Bet Gurage and Gumuz variants
85 | - Added UI name strings for Graphite and OpenType features
86 | - Removed Stylistic Sets
87 | - Slight change to line spacing to make it consistent across applications
88 | - Unencoded most PUA characters as they are supported through Character Variants
89 |
90 | 13 December 2013 (Lorna Priest Evans) Abyssinica SIL version 1.500
91 | - Improved design of U+1396 and U+1399 (metrics changed for these characters)
92 | - Added character variants
93 | - Added variant glyphs for U+2D93..U+2D96 (for Blin)
94 | - Added variant glyphs for U+12E0..U+12E6 and U+1335 (historical usage)
95 | - Changed Graphite feature identifiers from integers to 4-character
96 | alphanumeric tags
97 |
98 | 13 December 2010 (Lorna Priest) Abyssinica SIL version 1.200
99 | - Updated for Unicode 6.0 (U+AB00..U+AB2F)
100 | - Added Stylistic Sets and Graphite Features
101 | - Removed AAT support
102 |
103 | 1 June 2006 (Jonathan Kew)
104 | - AAT source added
105 |
106 | 25 May 2006 (SIL NRSI team) Abyssinica SIL version 1.0
107 | - First version released under the SIL Open Font License
108 |
109 |
110 |
112 |
113 | Copyright (c) 2000-2013 SIL International (http://scripts.sil.org/) with
114 | Reserved Font Names "Abyssinica" and "SIL".
115 |
116 | This Font Software is licensed under the SIL Open Font License, Version 1.1.
117 | This license is copied below, and is also available with a FAQ at:
118 | http://scripts.sil.org/OFL
119 |
120 |
121 | -----------------------------------------------------------
122 | SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
123 | -----------------------------------------------------------
124 |
125 | PREAMBLE
126 | The goals of the Open Font License (OFL) are to stimulate worldwide
127 | development of collaborative font projects, to support the font creation
128 | efforts of academic and linguistic communities, and to provide a free and
129 | open framework in which fonts may be shared and improved in partnership
130 | with others.
131 |
132 | The OFL allows the licensed fonts to be used, studied, modified and
133 | redistributed freely as long as they are not sold by themselves. The
134 | fonts, including any derivative works, can be bundled, embedded,
135 | redistributed and/or sold with any software provided that any reserved
136 | names are not used by derivative works. The fonts and derivatives,
137 | however, cannot be released under any other type of license. The
138 | requirement for fonts to remain under this license does not apply
139 | to any document created using the fonts or their derivatives.
140 |
141 | DEFINITIONS
142 | "Font Software" refers to the set of files released by the Copyright
143 | Holder(s) under this license and clearly marked as such. This may
144 | include source files, build scripts and documentation.
145 |
146 | "Reserved Font Name" refers to any names specified as such after the
147 | copyright statement(s).
148 |
149 | "Original Version" refers to the collection of Font Software components as
150 | distributed by the Copyright Holder(s).
151 |
152 | "Modified Version" refers to any derivative made by adding to, deleting,
153 | or substituting -- in part or in whole -- any of the components of the
154 | Original Version, by changing formats or by porting the Font Software to a
155 | new environment.
156 |
157 | "Author" refers to any designer, engineer, programmer, technical
158 | writer or other person who contributed to the Font Software.
159 |
160 | PERMISSION & CONDITIONS
161 | Permission is hereby granted, free of charge, to any person obtaining
162 | a copy of the Font Software, to use, study, copy, merge, embed, modify,
163 | redistribute, and sell modified and unmodified copies of the Font
164 | Software, subject to the following conditions:
165 |
166 | 1) Neither the Font Software nor any of its individual components,
167 | in Original or Modified Versions, may be sold by itself.
168 |
169 | 2) Original or Modified Versions of the Font Software may be bundled,
170 | redistributed and/or sold with any software, provided that each copy
171 | contains the above copyright notice and this license. These can be
172 | included either as stand-alone text files, human-readable headers or
173 | in the appropriate machine-readable metadata fields within text or
174 | binary files as long as those fields can be easily viewed by the user.
175 |
176 | 3) No Modified Version of the Font Software may use the Reserved Font
177 | Name(s) unless explicit written permission is granted by the corresponding
178 | Copyright Holder. This restriction only applies to the primary font name as
179 | presented to the users.
180 |
181 | 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
182 | Software shall not be used to promote, endorse or advertise any
183 | Modified Version, except to acknowledge the contribution(s) of the
184 | Copyright Holder(s) and the Author(s) or with their explicit written
185 | permission.
186 |
187 | 5) The Font Software, modified or unmodified, in part or in whole,
188 | must be distributed entirely under this license, and must not be
189 | distributed under any other license. The requirement for fonts to
190 | remain under this license does not apply to any document created
191 | using the Font Software.
192 |
193 | TERMINATION
194 | This license becomes null and void if any of the above conditions are
195 | not met.
196 |
197 | DISCLAIMER
198 | THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
199 | EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
200 | MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
201 | OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
202 | COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
203 | INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
204 | DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
205 | FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
206 | OTHER DEALINGS IN THE FONT SOFTWARE.
207 |
208 |
209 |
210 | Copyright (c) 2000-2021, SIL International (http://scripts.sil.org/).
211 |
212 |
213 | Abyssinica SIL is a trademark of SIL International
214 |
215 |
216 |
--------------------------------------------------------------------------------
/AbyssinicaSIL-webfont-elreq.css:
--------------------------------------------------------------------------------
1 | /*
2 | AbyssinicaSIL-webfont-example.css
3 | AbyssinicaSIL v1.500
4 | 1 Dec 2013
5 | This file is part of Abyssinica SIL font family (http://scripts.sil.org/AbyssinicaSIL)
6 | and is Copyright (c) 2000-2013 SIL International (http://www.sil.org/),
7 | with Reserved Font Names "Abyssinica" and "SIL". This Font Software is licensed
8 | under the SIL Open Font License, Version 1.1. You should have received a copy
9 | of the license along with this Font Software. If this is not the case, go to
10 | (http://scripts.sil.org/OFL) for all the details including a FAQ.
11 | */
12 |
13 | /* use Abyssinica SIL - Regular in .woff format */
14 | @font-face {
15 | font-family: AbyssinicaSILW;
16 | src: url(AbyssinicaSIL-Regular.woff);
17 | }
18 |
19 | /* set body to use Abyssinica SIL in .woff format */
20 | :lang(am), :lang(ti), :lang(byn), :lang(gez) {
21 | font-family: "Abyssinica SIL", AbyssinicaSILW, sans-serif;
22 | /* fall back to sans serif so that it's really obvious if the fonts don't load */
23 | }
24 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 |
3 | All documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).
4 |
--------------------------------------------------------------------------------
/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 |
--------------------------------------------------------------------------------
/LICENCE.md:
--------------------------------------------------------------------------------
1 | All documents in this Repository are licensed by contributors
2 | under the
3 | [W3C Document License](http://www.w3.org/Consortium/Legal/copyright-documents).
4 |
5 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Ethiopic Language Enablement (elreq)
2 |
3 | This is the place to explore gaps in support for languages that use the Ethiopic script on the Web and in eBooks, and to document requirements.
4 |
5 | We aim to address the problem that local users don't know how to tell the W3C what problems exist for support of their language on the Web, and the W3C doesn't know how to contact people who can help when questions arise.
6 |
7 | Topics for discussion are suggested by [the gap-analysis template](https://www.w3.org/International/i18n-activity/templates/gap-analysis/gap-analysis_template.html). This work feeds into the [language matrix](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) which provides a heat-map for language issues on the Web.
8 |
9 | ---
10 |
11 | ## Help wanted!
12 | **We're looking for information about this writing system. Follow the link for specific questions.**
13 |
14 | **[Ethiopic](https://github.com/w3c/elreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion)**
15 |
16 | ---
17 |
18 |
19 | ### Key links
20 | [GitHub repo](https://github.com/w3c/elreq) • [Discussion threads](https://github.com/w3c/elreq/issues) • [Charter](https://www.w3.org/International/elreq/charter/)
21 |
22 |
23 | ### Resource & requirement documents
24 | - **Ethiopic Script Resources** • [DNOTE](https://www.w3.org/TR/ethi-lreq) • [*Editor's draft*](https://www.w3.org/International/elreq/ethi/) • [*Latest commits*](https://github.com/w3c/elreq/commits/gh-pages/ethi/index.html)
25 |
26 | - **Ethiopic Layout Requirements** • [DNOTE](https://www.w3.org/TR/elreq) • [*Editor's draft*](https://www.w3.org/International/elreq/) • [*Latest commits*](https://github.com/w3c/elreq/commits/gh-pages/index.html)
27 |
28 | ### Gap analysis documents
29 | - **Ethiopic Gap Analysis** • [DNOTE](https://www.w3.org/TR/elreq-gap) • [*Editor's draft*](https://www.w3.org/International/elreq/gap-analysis/) • [*Latest commits*](https://github.com/w3c/elreq/commits/gh-pages/gap-analysis/index.html)
30 |
31 |
32 |
33 | ### Discussions
34 | - **Ethiopic** • [*Questions*](https://github.com/w3c/elreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion)
35 | • [*Gap reports*](https://github.com/w3c/elreq/labels/doc%3Aethi)
36 | • [*Other*](https://github.com/w3c/elreq/issues?q=is%3Aopen+-label%3Aquestion)
37 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Aelreq+label%3Aspec-type-issue)
38 |
39 |
40 |
41 | ### Related documents
42 | - [Ready-made Counter Styles](https://www.w3.org/TR/predefined-counter-styles/)
43 |
44 |
45 | ### Feedback
46 | Please use the [GitHub issue list](https://github.com/w3c/elreq/issues) to report issues for language support, for discussions, and to send feedback about documents. (Learn [how GitHub issues work](https://www.w3.org/International/i18n-activity/guidelines/issues.html).)
47 |
48 | Note that the public-i18n-arabic mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion.
49 |
50 |
51 | ### Participate
52 | You can participate in the work at various levels. In order of increasing commitment, these include List subscriber, Participant, Editor, and Chair. [Explore the options](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation.html).
53 |
54 | **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-ethiopic-request@w3.org?subject=subscribe) to the [public-i18n-ethiopic](https://lists.w3.org/Archives/Public/public-i18n-ethiopic/) 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 Ethiopic writing systems.
55 |
56 | **To contribute content:** All contributors should read and agree with [CONTRIBUTING.md](CONTRIBUTING.md).
57 |
58 | **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests.
59 |
60 | To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation).
61 |
62 |
63 |
64 | ### Contacts
65 |
66 | - Chairs: Daniel Yacob
67 | - W3C staff: [Richard Ishida](mailto:ishida@w3.org)
68 | - [Group participants](https://www.w3.org/groups/tf/i18n-elreq/participants)
69 |
70 |
71 | ### Links
72 | - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-ethiopic/)
73 | - [Writing i18n tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests)
74 | - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below)
75 | - [Action tracker](https://www.w3.org/International/groups/ethiopic-layout/track/actions/open)
76 | - Meeting info (tbd)
77 |
78 |
79 | ### Links to background information
80 | The following information describes work going on at the W3C to support languages on the Web.
81 | - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html)
82 | - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev)
83 | - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev)
84 | - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation)
85 | - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project)
86 | - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/)
87 |
88 |
89 | ### Links for editors
90 | If you end up creating a document, you should be familiar with and use the following:
91 |
92 | - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github)
93 | - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing)
94 |
--------------------------------------------------------------------------------
/charter/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Ethiopic Layout Task Force Charter
6 |
8 |
10 |
12 |
13 |
14 |
15 |
16 |
17 |
The mission of this task force is to document requirements for the layout and presentation of text in the official languages of Eritrea and Ethiopia that employ Ethiopic (Ge'ez) script when those languages are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications and Unicode.
35 |
The documents will provide requirements for the development of W3C standards affected by languages used in Eritrea and Ethiopia that utilize Ethiopic script for their written language. This document will not address requirements for languages of these regions that utilize Roman script as a basis for written language.
36 |
Ethiopic script is also used by communities outside of Eritrea and Ethiopia, and participation in this work by those communities is welcomed. This task force will gather and integrate feedback from the participating members about the need for and technical feasibility of various requirements.
37 |
The Task Force is part of the Internationalization Interest Group.
38 |
39 |
The aim of this Task Force is to follow the example of Requirements for Japanese Text Layout and collect information about specific use cases for technologies defined in various Web specifications as they relate to the aforementioned script. The Task Force will report the results of its activities as a group back to the Internationalization Working Group, as well as to other relevant groups and to the W3C membership and community.
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 main objective of the task force is to document typographic and layout requirements for languages using the Ethiopic script, for use with Web standards such as HTML, CSS, and Digital Publication technologies.
76 |
In addition to those technologies mentioned above, the group may review (but is by no means explicitly limited to reviewing) the following:
77 |
78 |
The work of the Internationalization Working Group.
79 |
CSS3 Modules, in particular:
80 |
81 |
CSS3 Text
82 |
CSS3 Lists
83 |
CSS3 Counter Styles
84 |
85 |
86 |
Browser testing and tools
87 |
HTML (in particular references to bidi, locale-specific formats, and other internationalization aspects)
88 |
89 |
90 |
Along with reviewing the above mentioned specifications and related specifications, it is expected that the group will also gather comments and questions about those specifications, collect information about specific use cases in Ethiopia and Eritrea for technologies defined in those specifications, and report the results of its activities as a group back to the Internationalization Working Group, as well as to other relevant groups - such as the HTML Working Group, CSS Working Group, SVG Working Group, and other Working Groups at the W3C as needed.
91 |
92 |
Initial set of languages
93 |
94 |
Ethiopic is used by two of the official languages of Ethiopia (Amharic) and Eritrea (Tigrinya). Including the populations of minority languages also using Ethiopic script, it becomes the basis of literacy for as many as 50 million. Accordingly, the requirements of Amharic and Tigrinya shall set the initial scope of the project. While the basic script is shared by a number of language communites; each will add or remove elements as per their linguistic needs and may also lead to different requirments for fonts, pronunciation and layout.
95 |
The initial scope of the project covers Ethiopic script along with western puncutation and numerals used with Ethiopic. A later phase of the project may encompass external scripts such as Roman and Arabic that are regularly formatted with Ethiopic.
96 |
At a later date the scope may be extended to cover the writing practices of minority groups employing Ethiopic script. Here is an incomplete list of the languages used in Eritrea and Ethiopia: Argobba, Awngi, Blin, Ge'ez, Harari, Khimtanga (Xamtanga), Sebatbeit, Siltie and Tigre. Additional languages will be included based on the availability of linguistic and typographic experts.
97 |
98 |
Deliverables
99 |
The Ethiopic 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 about text layout and related technologies in Ethiopia, Eritrea and elsewhere, the contents of which might include (but by no means are explicitly limited to) the following:
100 |
101 |
Requirements for Text Layout and presentation.
102 |
Requirements for Digital Publications.
103 |
104 |
The group may also choose to produce other non-normative deliverables, such as test cases and error reports – under the terms of the Policies for Contribution of Test Cases to W3C, and in coordination with any relevant working groups.
105 |
106 |
107 |
Target deliverables are documents which include but are not limited to Modern & Classical Ethiopic Layout Requirements.
108 |
109 |
110 |
Milestones
111 |
112 |
Plans for the main document deliverable are as follows. All deliverables will be made available in English.
113 |
114 |
115 |
116 |
Note: The group will document significant changes from this initial
117 | schedule on the group home page.
118 |
119 |
Specification
120 |
FPWD
121 |
WD for final review
122 |
WG Note
123 |
124 |
125 |
Requirements for Ethiopic Text Layout Amharic & Tigrinya
126 |
127 |
Q4 2015
128 |
Q3 2016
129 |
Q4 2016
130 |
131 |
132 |
Other deliverables may be produced on an ongoing basis throughout the life of the charter, and the specific topics to be addressed by the task force and schedule information cannot be determined far in advance, but are driven by the needs of the Web community.
133 |
134 |
Success Criteria
135 |
136 |
The success of the Task Force will be evaluated based on how productively it engages with W3C members and the relevant script communities to promote discussion of specifications that affect layout and presentation of languages on the Web, and how effectively it is able to produce additional documents for the refinement, implementation, and adoption of text layout and related technologies in Eritrea, Ethiopia and worldwide.
137 |
138 |
139 |
140 |
Relationships to External Groups
141 |
142 |
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.
143 |
144 |
Dependencies
145 |
146 |
The Ethiopic Text Layout Task Force has no formal dependencies on any W3C Working Groups other than the Internationalization Working Group. Important points of contact are:
The Ethiopic Text Layout Task Force is also expected to take advantage of opportunities for discussion and collaboration with existing groups and communities in Eritrea and Ethiopia as well as groups and communities elsewhere.
161 |
162 |
163 |
164 |
165 |
Participation
166 |
167 |
To be successful, the Ethiopic Text Layout Task Force is expected to have participation, for its duration, from a representative section of the typographic and digital text publishing communities for each of the main languages covered. Effective participation in the Ethiopic Text Layout Task Force is expected to consume up to one work day per week for each participant; two days per week for editors.
Ethiopic Text Layout Task Force discussions take place via email, and face-to-face meetings may be called at locations that are convenient to participants in the project.The group may communicate in Amharic or Tigrinya. Any publications or other reports eventually contributed by the Task Force back to the W3C will be made available in English. (Translations may be produced in addition to the English version, but the English version will remain the authoritative version.)
178 |
The task force reaches out to the wider international community with discussions and announcements in English on the public-i18n-ethiopic@w3.org list (archive). That list will be used for technical discussions, where necessary, but the group will use github issues to handle most technical or editorial comments and discussions. The public-i18n-ethiopic@w3.org list must archive or point to minutes and summaries of all teleconferences and face-to-face meetings. Meeting minutes will list all attendees at a given meeting.
179 |
An administrative list, public-i18n-alreq-admin, will also be used for internal communication about practical matters, such as meeting agenda, which should be published before each teleconference or face-to-face meeting.
As explained in the Process Document (section 3.3),
194 | 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).
195 |
196 |
197 |
198 |
Patent Policy
199 |
200 |
Participants in the Ethiopic Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined in Section 6 of the W3C Patent Policy document. Although the Ethiopic Text Layout 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 Ethiopic Layout Task Force within the Internationalization Interest Group has been
209 | created according to section 6.2 of the Process Document. In the event of a conflict between this
212 | document or the provisions of any charter and the W3C Process, the W3C Process
213 | shall take precedence.
214 |
215 |
216 | Charter Authors: Daniel Yacob, Richard Ishida.
217 |
218 |
219 |
This document describes and prioritises gaps for the support of the Ethiopic 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 Ethiopic 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.
108 |
109 |
This page documents difficulties that people encounter when trying to use languages written in the Ethiopic script on the Web.
110 |
111 |
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.
123 |
124 |
Key:
125 |
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
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.
135 |
136 |
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.
137 |
138 |
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.
139 |
140 |
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.
153 |
154 |
Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. Find the Ethiopic items.
155 |
156 |
For more information about the Ethiopic script, including requirements, tests, GitHub discussions, type samples, and more, see Ethiopic 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 task force does gap analysis and documents requirements, related to the layout and
74 | presentation of text in languages that use Indian scripts,
75 | in the context of Web standards and technologies such as HTML, CSS,
76 | Mobile Web, Digital Publications, and Unicode.
We welcome participation requests from people who are interested
79 | in contributing to the work of the Task Force. There are two ways to get involved:
80 |
81 |
Task force members are expert contributors
82 | who participate actively in producing the work of the group, regularly
83 | contributing text and advice to create the outputs, and participating in
84 | meetings. For more information about becoming a task force member
85 | contact Richard Ishida.
86 |
It is also possible to follow and contribute to
87 | discussions without the commitment required in being an expert
88 | contributor. See the github home page for details.
The Ethiopic Layout Task Force will not produce
107 | Recommendation-track deliverables but expects to produce Working
108 | Group Notes, published by the Internationalization
109 | Working Group.
110 |
To find and follow progress on deliverables, see the GitHub repo.
The group charter also allows review of draft specifications
119 | produced by other working groups, and provision of translations of
120 | relevant W3C specifications and resources. The group may also choose to produce other non-normative deliverables,
121 | such as test cases and error reports, under the terms of the Policies
122 | for Contribution of Test Cases to W3C, and in coordination
123 | with any relevant working groups.
Most of the technical discussion will take place in the GitHub issues list. If you want to raise an issue with the documents, this is the place to raise it.
126 |
To follow the work, you can 'Watch' the repository, or subscribe to the public-i18n-ethiopic 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-ethiopic.
There is also a public-elreq-admin mailing list for internal and administrative use by the TF
130 | participants, for example for announcing teleconference agendas, new
131 | participants, preparing for publication, etc. or for discussing other
132 | non-technical, practical arrangements related to the group. Only
133 | participants in the task force are subscribed to that list.
134 |
The task force aims to hold teleconference or face-to-face
135 | meetings at least once a month, with additional
136 | meetings as needed to enable discussion and review status of the
137 | work.
138 |
The #elreq IRC channel is used for supplementary communication and minute-taking during meetings. Instructions for use are sent out with the meeting agenda.
139 |
140 |
141 |
142 |
143 |
144 |
145 |
146 |
Chair: Daniel Yacob
147 | Staff contact: Richard Ishida
148 | $Id: Overview.html,v 1.77 2010/03/02 12:12:01 rishida Exp $
Supporting Multiple Ruby Annotation Rows With Markup and CSS
57 |
This page present an incremental development of an approach to supporting multiple rows of annotations with Ruby markup and
58 | CSS styling properties. The page also serves to test the level browser support for the approach taken.
59 |
60 |
While some browser do support the nesting of Ruby markup to present multiple rows of annotation; nesting is not an option
61 | when the positioning and decoration of annotation text at one level does not occur fully within the boundaries of the other. For example,
62 | the upper annotation level may begin midway within the boundaries of the lower level annotation, and extend beyond the termination of the
63 | lower level's annotation. Handling these scenarios leads us into the overlapping markup
64 | problem which presently does not have a solution supported by W3C standards.
65 |
66 |
The approach taken here handles multiple rows of annotation by duplicating the base text and formatting each copy with a single row
67 | of Ruby annotation independently. These independently annotated copies of the base text are then overlaid on top of one
68 | another so that the base text is superimposed precisely and only a single copy of the base text remains visible. The position of the
69 | Ruby annotation text is then raised to successively higher levels on each copy, creating the effect of multiple rows of overlapping
70 | annotation.
71 |
72 |
A solution for multiple rows of independently bound and formatted annotation is needed to support the
73 | Zaima interlinear notation, which is fully described in the developing
74 | model document.
75 |
76 |
77 |
78 |
79 |
Baseline
80 |
Reference Lines As Undecorated Text
81 |
The sample text that we will be working with:
82 |
ABCDEFGHIJKLMNOPQURSTUVWXYZ
83 |
ሀለሐመሠረሰሸቀቐበቨተቸኀነኘአከኸወዐዘዠየደጀገጠጨጰጸፀፈፐ
84 |
85 |
Four Overlays Without Rubies
86 |
We will rely on CSS layers set with the z-index property to overlay independent Ruby annotations
87 | on top of one another (with offsets) to create the Zaima rows. Establish here that layers work as expected. Text may appear
88 | bolder:
Unfortunately layout policies appear to have changed under Chrome 61 and the positioning of Ruby text (via bottom:npx)
216 | also impacts the position of the base text. Ruby text can no longer be raised indepently of the base text by the approach used previously. Until a better
217 | solution is found, a work around is to simply ignore the raising of the base text along with the annotation text. This approach appears to work by
218 | virtue of the base text being hidden from view but may have other consequences on layout.
Repeat Approaches with <rb style="visibility: visible">
235 |
Exposing the base text again to reveal their position with respect to the anchor (base text of first row) and
236 | to help understand any layout side effects (numeric indexes are added to the base text for clarity):
61 | This document provides samples of Zaima annotation presented in the ASCII table style found in the current
62 | draft of the CSS Ruby Annotation Layout Module Level 1 document.
63 |
64 |
65 |
66 |
67 |
Use Case 1
68 |
69 | The first use case presented as an ASCII table.
70 |
71 |
72 |
73 |
Figure 1 Target annotation from Selot Kidassie p. 113 and decomposition.
A simplification to corresponding markup may be possbile if empty cells can be removed without impacting the table structure. This has been done in the follwing where
191 | the cells wihtout content have been removed at the tops of their respective columns.
192 |
193 |
194 |
Figure 3b Zimarie Wemewasit p. 34 with empty cells removed from the top levels.
61 | In a 2019 post, Richard Ishida devised a clever CSS definition for markup and display of
62 | Linguistic glosses.
63 | The approach proved successful and easy to use for the glossing use cases.
64 | This page presents attempts to apply the same interlinear gloss styling to the
65 | first use case sample of the Zaima Uses Cases.
66 |
67 |
68 |
69 |
Figure 1 Target annotation from Selot Kidassie p. 113 and decomposition.
96 | With interlinear glosses, columns align words in a vertical arrangement. The column as a container also provides the interlinear
97 | association between the base text and the text of other rows, the semantic context of a row will be set with a style class. With Zaima annotation
98 | characters are the alignment tokens whereas glosses use word-level tokens. This difference in grandularity will lead to difficulty in
99 | the horizontal alignment of one element relative to another across the interlinear rows. Horizontal positioning of symbols in the
100 | annotation rows is achieved with some success by applying non-breaking spaces.
101 |
102 |
103 |
Figure 2 Interlinear alignment over rows using word-columns.
143 | The main deficit with this approach is that column spanning can not vary across rows. once a column width is set, it can not be subdivided
144 | Thus to have cells spanning two columns on the top rows, the corresponding bottom rows cells must also be identically column spanning.
145 |
146 |
147 |
Figure 3 Interlinear alignment over rows using character-columns.
208 | The following presents the originally layered ruby approach where each <ruby> group is given a different
209 | z-index value and layers after "1" hide the base (<rb>) text. This approach was found to have the display
210 | shortcoming that the spacing between the letters of the base text may vary with each layer as driven by the <rt>
211 | content width requirements. This can lead to the "columns" shifting laterally across layers slightly and leading to an
212 | imperfect layout.
213 |
214 |
215 |
Figure 4 Interlinear alignment over rows using Ruby overlays.
281 | The exercise helped illuminate the distinction between word level alignment across rows, version character level alignment.
282 | In the Zaima practice, annotation is associated with one or more base letters. This is different from glossing where
283 | the need is to manage the association of an annotation with one or more words. Under this consideration, Zaima annotation
284 | is more akin to the Ruby annotation practice. Like Ruby layout, fascilities to control the horizontal alignment of the
285 | annotation text with respect to the extents of the base is essential.
286 |
287 |
288 | Difficulties with the interlinear gloss approach were revealed with the horizontal positioning of the annotation over specific
289 | base characters. Non-breaking spaces were used as a solution to adjust the annotation text slightly leftward or rightward
290 | but this approach is not believed to be dependable since space width is not guaranteed across platforms and the character
291 | alignments are likely to change in unpredictable ways as text is scaled upward or downward in size.
292 |
Zaima Playpen for CSS Development & Browser Testing
412 |
This page is both exploratory and demonstrative of CSS capabilities in positioning and styling Zaima under Ruby Markup.
413 | Ruby markup and style properties are applied to Zaima samples to evaluate their suitability in presenting Zaima under user expectations in digital documents.
414 | A goal of the page is to identify and note any short comings in the ability of markup and style languages to support Zaima requirements,
415 | uncover browser limitations in rendering,
416 | and ultimately to determine if Zaima presentation requirements necessitate their own markup model and standards additions.
417 |
Zaima Playpen for CSS Development & Browser Testing
350 |
This page is both exploratory and demonstrative of CSS capabilities in positioning and styling of the
351 | interlinear notation of Zaima under Ruby Markup.
352 | Ruby markup and style properties are applied to Zaima samples to evaluate their suitability in presenting Zaima notation
353 | under user expectations in digital documents. A goal of the page is to identify and note any short comings in the ability
354 | of markup and style languages to support Zaima requirements, uncover browser limitations in rendering,
355 | and ultimately to determine if Zaima presentation requirements necessitate their own markup model and standards additions.
356 |
357 |
358 |
359 |
360 |
Browser support
361 |
The article describes behavior for the following browser versions. We will try to update the article as behavior changes.
