-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathindex.html
291 lines (148 loc) · 11.7 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Hebrew Layout Requirements</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer></script>
<script class="remove">
var respecConfig = {
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
specStatus: "ED",
//publishDate: "2015-07-21",
noRecTrack: true,
shortName: "hlreq",
copyrightStart: "2017",
edDraftURI: "https://w3c.github.io/hlreq/",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "Richard Ishida", company: "W3C", w3cid: 3439 },
],
group: "i18n",
github: 'w3c/hlreq',
postProcess: [
async function importStyleSheet() {
const elems = document.querySelectorAll(`link[rel='stylesheet'][data-import]`)
await Promise.all(
[...elems].map(async link => {
const text = await fetch(link.href).then(r => r.text())
const style = document.createElement("style")
style.textContent = text
link.replaceWith(style)
})
)
}
],
};
</script>
<link rel="stylesheet" data-import href="https://w3c.github.io/i18n-drafts/style/respec_2022.css">
<!--<link rel="stylesheet" href="local.css">-->
</head>
<body>
<div id="abstract">
<p>This document describes requirements for the layout and presentation of text in languages that use the Hebrew script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.</p>
</div>
<div id="sotd">
<p>This document describes the basic requirements for Hebrew 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 Hebrew script. Currently the document focuses on Hebrew as used for the Hebrew language. The information here is developed in conjunction with a <a href="../gap-analysis">document that summarises gaps</a> in support on the Web for Hebrew.</p>
<p>The editor's draft of this document is being developed by the <a href="https://w3c.github.io/hlreq/homepage/">Hebrew Layout Task Force</a>, part of the W3C <a href="https://www.w3.org/International/ig/">Internationalization Interest Group</a>. It is published by the <a href="https://www.w3.org/International/core/">Internationalization Working Group</a>. The end target for this document is a Working Group Note.</p>
</div>
<section id="h_introduction">
<h2>Introduction</h2>
<section id="h_acknowledgements">
<h3>Contributors</h3>
<p>Amir Aharoni provided most of the original technical content. Richard Ishida reorganised the content along standardised lines.</p>
<!--<p>Thanks to the following people who contributed information that is used in this document (contributors' names listed in in alphabetic order): XXXX.</p>
-->
<p data-lang="en">See also the <a href="https://github.com/w3c/hlreq/graphs/contributors">GitHub contributors list</a> for the Hebrew Language Enablement project, and the <a href="https://github.com/w3c/hlreq/issues?q=is%3Aopen+is%3Aissue">discussions related to Hebrew script</a>.</p>
</section>
<section id="h_about_this_document">
<h3>About this document</h3>
<p>The <abbr title="World Wide Web Consortium">W3C</abbr> has to ensure that the needs of scripts and languages around the world are built into technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.</p>
<p>The aim of this document is to describe basic requirements for Hebrew script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of Hebrew scripts.</p>
<p>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.</p>
</section>
<section id="h_gap_analysis">
<h3>Gap analysis</h3>
<p>This document is pointed to by a separate document, <a href="gap-analysis/">Hebrew Gap Analysis</a>, which describes gaps in support for Hebrew on the Web, and prioritises and describes the impact of those gaps on the user.</p>
<p>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.</p>
</section>
<section id="h_info_requests">
<h3>Other related resources</h3>
<p>The <a href="https://w3c.github.io/typography/">Language enablement index</a> points to this document and others, and provides a central location for developers and implementers to find information related to various scripts.</p>
<p>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 <a href="https://w3c.github.io/i18n-activity/textlayout/?filter=type-info-request">what information developers are currently seeking</a>, and the resulting list can also be filtered by script.</p>
</section>
</section>
<section id="h_script_overview">
<h2>Hebrew Script Overview</h2>
<p>Hebrew is an <a class="termref" href="https://www.w3.org/TR/i18n-glossary/#dfn-abjad">abjad</a>. This means that in normal use the script represents only consonant and long vowel sounds. This approach is helped by the strong emphasis on consonant patterns in Semitic languages.</p>
<p>The Hebrew script is written right-to-left across the page, and Hebrew characters are not joined cursively as they are in, for example, Arabic text.</p>
<p>The script is unicameral.</p>
<p>Words are separated by spaces, and these provide the predominant break points for line-breaking, and adjustment points for justification.</p>
<p>See also this <a href="https://r12a.github.io/scripts/hebr/he.html">overview of the Hebrew script</a>.</p>
</section>
<section id="h_shaping">
<h2>Glyph shaping & positioning</h2>
<section id="h_letterforms">
<h3>Letterform slopes, weights, & italics</h3>
<p>The use of italic fonts in Hebrew is controversial. Some designers say that slanted fonts shouldn't be used at all. Some say that only meticulously designed slanted fonts can be used (although this is true also for Latin text).</p>
<p>Slanted fonts are not used in newspapers. Bold type is more likely to be used where English newspapers would use italics, although a different typeface is often used for that.</p>
<p>Bold type can be used for emphasis, or for highlighting specific items in text.</p>
<figure id="fig_bold">
<img src="images/bold.jpg" alt="Newpaper cutting">
<figcaption>Bold type used to highlight people's names. (The red lines were added to the image to show the location.)</figcaption>
</figure>
</section>
</section>
<section id="h_units">
<h2>Typographic units</h2>
<section id="h_encoding">
<h3>Characters & encoding</h3>
<p>Most of the time Hebrew is written without diacritical marks, however there are two notable uses for diacritics:</p>
<dl>
<dt>Vowel diacritics, also known as niqqud or vocalization</dt>
<dd>The diacritics are not used in most texts, but they are frequently used in texts for children, in poetry, in religious texts, and occasionally in prose and casual writing.</dd>
<dt>Cantillation, also known as teamim, teamei miqra, or trop</dt>
<dd>Cantillation marks are used in Biblical texts, usually together with vocalization marks.</dd>
</dl>
<p>Some known issues:</p>
<ul>
<li>A text that uses vocalization marks may have to be styled differently from the rest of the text. For example, it may need to use a different font that ensures that the vocalization marks are displayed correctly and clearly (some fonts don't display them well because they are relatively rare). It may also be desirable to show the vocalized text in larger size.</li>
<li>It is occasionally useful to give the diacritics a different color, for example for the purpose of teaching. For an example of how it would appear, see the <a href="https://he.wikipedia.org/wiki/%D7%97%D7%95%D7%9C%D7%9D">Hebrew Wikipedia article Holam</a>, which shows diacritics in a different color using images. </li>
</ul>
</section>
<section id="h_segmentation">
<h3>Grapheme/word segmentation & selection</h3>
<p>Hebrew text is generally similar to Latin text in this regard. The only issue to note is selecting and moving through text that includes the character maqaf, the Hebrew hyphen. It should behave like a hyphen.</p>
</section>
</section>
<section id="h_inline">
<h2>Punctuation & inline features</h2>
<section id="h_quotations">
<h3>Quotations</h3>
<p>According to the section on quotation marks (<span dir="rtl" lang="he">מירכאות</span>) <a href="https://hebrew-academy.org.il/topic/hahlatot/punctuation/">Academy of the Hebrew Language's punctuation rules</a>, both single and double quotes are acceptable when there's no nesting. When there is nesting, different quotes are supposed to be used for the nested quote. In most of the examples in the document itself, the examples are written with double quotation marks in non-nested quotes and in the outer quote, and with single quotation marks in the nested quote.</p>
<p>Most of the examples in the document use the characters <span class="codepoint" translate="no"><span lang="he" dir="rtl">"</span> [<span class="uname">U+0022 QUOTATION MARK</span>]</span> and <span class="codepoint" translate="no"><span lang="he" dir="rtl">'</span> [<span class="uname">U+0027 APOSTROPHE</span>]</span>, however it also notes the following: "In handwriting and in traditional printing the opening quotation marks are low: <span dir="rtl" lang="he">„–”; ‚–’</span> On devices that don't support typing the low quotation marks, the high quotation marks are used." Typing the low and high quotation marks is defined in the SI 1452 standard (2012 version) on the keys Alt-;, Alt-L, Alt-., and Alt-,. This standard is implemented in Windows 8, as well as in desktop Linux distributions, and in the Gboard keyboard for Android and iOS.</p>
</section>
</section>
<section id="h_para">
<h2>Lines & paragraph layout</h2>
<section id="h_spacing">
<h3>Text spacing</h3>
<p>Hebrew uses letter-spacing (tracking) to emphasise or highlight text (eg. people names, concepts, terms etc.).</p>
<figure id="tracking">
<img src="images/tracking.png" alt="Picture of tracking">
<figcaption>Terms in a medical dictionary that are highlighted using letter-spacing. (Red lines added to draw attention.)</figcaption>
</figure>
</section>
<section id="h_initials">
<h3>Styling initials</h3>
<p>Drop caps are used in Hebrew occasionally. If the text uses vowel or cantilation diacritics, all the diacritics on the letter must be included in the drop cap and styled accordingly.</p>
</section>
</section>
<section id="a_changes" class="appendix">
<h2>Change log</h2>
<ul>
<li>Reorganised sections to conform to the standard page structure for layout requirements.</li>
</ul>
</section>
</body>
</html>