Hebrew Script Resources

W3C Group Draft Note

More details about this document
This version:
https://www.w3.org/TR/2024/DNOTE-hebr-lreq-20240716/
Latest published version:
https://www.w3.org/TR/hebr-lreq/
Latest editor's draft:
https://w3c.github.io/hlreq/hebr/
History:
https://www.w3.org/standards/history/hebr-lreq/
Commit history
Editor:
(W3C)
Feedback:
GitHub w3c/hlreq (pull requests, new issue, open issues)

Abstract

This document points to resources for the layout and presentation of text in languages that use the Hebrew script. The target audience includes developers of Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode, as well as implementers of web browsers, ebook readers, and other applications that need to render Hebrew text.

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document points to resources 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 languages written using the Hebrew script. The information here is developed in conjunction with a document that summarises gaps where the Web fails to adequately support the Hebrew script.

The editor's draft of this document is being developed in the GitHub repository Hebrew Language Enablement (hlreq), with contributors from the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.

To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on using a URL.

This document was published by the Internationalization Working Group as a Group Draft Note using the Note track.

Group Draft Notes are not endorsed by W3C nor its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

The W3C Patent Policy does not carry any licensing requirements or commitments on this document.

This document is governed by the 03 November 2023 W3C Process Document.

Some links on this page point to repositories or pages to which information will be added over time. Initially, the link may produce no results, but as issues, tests, etc. are created they will show up.

Links that have a gray color led to no content the last time this document was updated. They are still live, however, since relevant content could be added at any time. When the document is updated, links that now point to results will have their live colour restored.

1. Introduction

1.1 Contributors

The initial version of this document was prepared by Richard Ishida.

See also the GitHub contributors list for the Hebrew Language Enablement project, and the discussions related to Hebrew script.

1.2 About this document

This document points to resources for Hebrew script layout and text support on the Web and in eBooks. These resources provide information for developers of Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support languages written using the Hebrew script. They include requirements, tests, GitHub discussions, type samples, and more,

The document focuses on typographic layout issues. For a deeper understanding of the Hebrew script and how it works see Hebrew Orthography Notes, which includes topics such as: Phonology, Vowels, Consonants, and Numbers.

1.3 Gap analysis

This document should be used alongside a separate document, Hebrew Gap Analysis, which describes gaps in language support for users of the Hebrew script, and prioritises and describes the impact of those gaps on the user.

Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. (Filter for Hebrew script items)

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.

The W3C also has a repository with discussion threads related to the Hebrew script, including requests from developers to the user community for information about how scripts/languages work, and a notification system that tracks issues in W3C working groups related to the Hebrew script. See a list of unresolved questions for Hebrew experts. Each section below points to related discussions. See also the repository home page.

2. Hebrew Script Overview

The Hebrew script is essentially an abjad. This means that in normal use the script represents consonants but not all vowels. This approach is helped by the strong emphasis on consonant patterns in Semitic languages.

Note that the focus of this page is on everyday use for contemporary Israeli Hebrew, including educational materials, but not including biblical texts, prayer books, and the like. The latter tend to include additional characters, such as cantillation marks.

Hebrew text runs right-to-left in horizontal lines, but numbers and embedded Latin text are read left-to-right.

There is no case distinction. Words are separated by spaces.

The Modern Israeli Hebrew alphabet uses 22 letters, plus 5 word-final letters that have their own code points. Additional sounds can be represented using dagesh, shin/sin dots, or geresh.

Hebrew has 11 vowel diacritics in regular use to express vowel sounds (called niqqud or points), but rarely uses them in normal text. Hebrew readers are usually able to understand the pronunciation from the context and the regular structure of Hebrew words. These and other phonetic diacritics are written, however, where needed to clarify ambiguities or for educational purposes.

Vowel locations can be marked by 4 matres lectionis (consonants indicating vowel locations).

A spelling innovation introduced by modern Hebrew uses matres lectionis to spell certain short vowels that would not have been marked in older texts. Although the hiding of short vowel niqqud would generally qualify Hebrew as an abjad, this 'full spelling' approach makes it partially alphabetic.

In vowelled text, there is a diacritic to indicate the absence of a vowel in consonant clusters.

Modern Hebrew uses both European digits, and ASCII punctuation marks.

3. All topics

4. Text direction

4.1 Bidirectional text

5. Glyph shaping & positioning

5.1 Fonts & font styles

5.2 Context-based shaping & positioning

5.3 Letterform slopes, weights, & italics

6. Typographic units

6.1 Characters & encoding

6.2 Grapheme/word segmentation & selection

7. Punctuation & inline features

7.1 Phrase & section boundaries

7.2 Quotations & citations

7.3 Emphasis & highlighting

7.4 Abbreviation, ellipsis & repetition

7.5 Inline notes & annotations

7.6 Text decoration & other inline features

8. Line & paragraph layout

8.1 Line breaking & hyphenation

8.2 Text alignment & justification

8.3 Text spacing

8.4 Baselines, line height, etc.

8.5 Lists, counters, etc.

8.6 Styling initials

9. Page & book layout

9.1 General page layout & progression

9.2 Grids & tables

9.3 Footnotes, endnotes, etc

9.4 Page headers, footers, etc

9.5 Forms & user interaction

A. Change log