Hebrew (script)
Second-Level Reference Label Generation Rules, 25 October 2024 Current
Summary
| Version | 2 — Second Level Reference LGR |
|---|---|
| Date | |
| Tag |
und-Hebr (Hebrew)
|
| Unicode | 11.0.0 |
| Source file | lgr-second-level-hebrew-script-25oct24-en.xml (19.9kb) |
Description
INSTRUCTIONS
- These instructions cover how to adopt an LGR based on this reference LGR for a given zone and how to prepare the file for deposit in the IANA Repository of IDN Practices.
- As described the IANA procedure (https://www.iana.org/help/idn-repository-procedure) an
LGR MUST contain the following elements in its header:
- Script or Language Designator (see below for guidance)
- Version Number (this must increase with each amendment to the LGR, even if the updates are limited to the header itself)
- Effective Date (the date at which the policy becomes applicable in operational use)
- Registry Contact Details (contact name, email address, and/or phone number)
- The following information is optional:
- Document creation date
- Applicable Domain(s)
- Changes made to the Reference LGR before adopting
Please add or modify the following items in the XML source code for this file before depositing the document in the IANA Repository. (https://www.iana.org/domains/idn-tables)
Meta Data
Note: version numbers start at 1. RFC 7940 recommends using simple integers. The version comment is optional, please replace or delete the default comment. Version comments may be used by some tools as part of the page header.
<version comment="[Please replace (or delete) the optional comment]">[Please fill in version number, starting at 1]</version>
<date>[Please fill in with publication date, in YYYY-MM-DD format]</date>
<validity-start>[Please fill in effective date, in YYYY-MM-DD format]</validity-start>
Note: the scope element may be repeated, so that the same document can serve for multiple domains.
<scope type="domain">[Please provide, in ".domain" format]</scope>
Registry Contact Information:
Please fill in the Registry Contact Details.
Change History
If you made technical modifications to the LGR, please summarize them in the Change History (and also note the details in the appropriate section of the description).
PLEASE DELETE THESE INSTRUCTIONS BEFORE DEPOSITING THE DOCUMENT
Read the rest of the description Show less
Registry Contact Details
- Contact Name: [Please fill in Contact Name]
- Email address: [Please fill in Email address]
- Phone Number: [Please fill in optional Phone Number]
Label Generation Rules for the Hebrew Script
Overview
This document specifies a set of Label Generation Rules (LGR) for the Hebrew script for the second level domain or domains identified above. The starting point for the development of this LGR can be found in the related Root Zone LGR [RZ-LGR-Hebr]. The format of this file follows [RFC 7940]. This LGR is adapted from the “Reference LGR for the Second Level for the Hebrew Script” [Ref-LGR-und-Hebr], for details, see Change History below.
For details and additional background on the Hebrew script, see “Proposal for Hebrew Script Root Zone LGR”, Version 1.2, February 2019 [Proposal-Hebrew].
Repertoire
The repertoire contains 27 code points for letters, 5 of which are variants (final forms) of 5 others. The repertoire supports the Hebrew and Yiddish languages with restrictions appropriate for domain names. The repertoire is a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Hebrew]. (The proposal cited has been adopted for the Hebrew script portion of the Root Zone LGR.)
The Hebrew script is written from right to left. More details can be found in Section 3, “Background About the Script and Languages Using it” in [Proposal-Hebrew].
For the second level, the repertoire has been augmented with the ASCII digits, U+0030 to U+0039, plus U+002D HYPHEN-MINUS, for a total of 38 repertoire elements.
Any code points outside the Hebrew Script repertoire that are targets for out-of-repertoire variants would be included here only if the variant is listed in this file. In this case they are identified as a reflexive (identity) variant of type “out-of-repertoire-var”. Whether or not they are listed, they do not form part of the repertoire.
Repertoire Listing: Each code point or range is tagged with the script or scripts with which the code point is used. For each repertoire element, one or more references document sufficient justification for inclusion in the repertoire; see the “References” below. Comments provide additional information for some code points.
Variants
The variants defined in this LGR are limited to those required for use in zones not shared with any other script. As such, this LGR does not define cross-script variants. However, using this LGR concurrently with any LGR for Latin in the same zone will create potential cross-script issues. For details, see Section 6, “Variants” in [Proposal-Hebrew]. Mitigation of these cross-script variants can be addressed by using the Common LGR. For details, see Section 3, “Use of Multiple Reference LGRs in the Same Zone” in [Level-2-Overview]. In addition to variants defined by this LGR, the full variant information related to this script and required for concurrent use with the Latin LGR(s) can be found in the following LGR: [Ref-LGR-Latin-Full-Variant-Script]
This LGR defines five in-script variants that are final forms of Hebrew letters. For details, see Section 6, “Variants”, in “[Proposal-Hebrew]”.
Character Classes
This LGR does not define named character classes.
Whole Label Evaluation (WLE) and Context Rules
Common Rules
By default, the LGR includes the rules and actions to implement the following restrictions mandated by the IDNA protocol. They are marked with ⍟.
- Hyphen Restrictions — restrictions on the allowable placement of hyphens (no leading/ending hyphen and no hyphen in positions 3 and 4). These restrictions are described in Section 4.2.3.1 of RFC 5891 [150]. They are implemented here as context rule on U+002D (-) HYPHEN-MINUS.
- Leading Combining Marks — restrictions on the allowable placement of combining marks (no leading combining mark). This rule is described in Section 4.2.3.2 of RFC 5891 [150].
Right-To-Left Rules
- leading-digit — restrictions on the allowable placement of digits in a right-to-left context (no leading digit), (see section 2.1 of RFC 5893 [160]); implemented here as a context rule on each digit.
Default Actions
This LGR includes the default actions for LGRs as well as the action needed to invalidate labels with misplaced combining marks. They are marked with ⍟. For a description see [RFC 7940].
Hebrew-specific Rules
This LGR does not define rules specific to the Hebrew script.
Methodology and Contributors
The LGR in this document has been adapted from the corresponding Reference LGR for the Second Level. The Second Level Reference LGR for the Hebrew Script was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Hebrew script and information contained or referenced therein; see [RZ-LGR-Hebr]. Suitable extensions for the second level have been applied according to the [Guidelines] and with community input. The original proposal for a Root Zone LGR for the Hebrew script, that this LGR is based on, was developed by the Hebrew Generation Panel. For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Hebrew], as well as [RZ-LGR-Overview].
[IL-IDN] was consulted during the work on this LGR.
Changes from Version Dated 22 April 2021
Unicode Version has been updated.
Changes from Version Dated 25 October 2024
Adopted from the Second Level Reference LGR for the Hebrew Script [Ref-LGR-und-Hebr] without normative changes.
References
The following general references are cited in this document:
- [Guidelines]
- ICANN, “Guidelines for Developing Reference LGRs for the Second Level”, (Los Angeles, California: ICANN, 27 May 2020), https://www.icann.org/en/system/files/files/lgr-guidelines-second-level-27may20-en.pdf
- [IL-IDN]
- Hebrew IDN Table for .IL https://www.iana.org/domains/idn-tables/tables/il_he_1.0.html
- [Level-2-Overview]
- Internet Corporation for Assigned Names and Numbers, (ICANN),“Reference Label Generation Rules (LGR) for the Second Level: Overview and Summary” (PDF), (Los Angeles, California: ICANN, 25 October 2024), https://www.icann.org/en/system/files/files/level2-lgr-overview-summary-25oct24-en.pdf
- [Proposal-Hebrew]
- Hebrew Generation Panel, “Proposal for a Hebrew Script Root Zone Label Generation Ruleset (LGR)”, 24 April 2019, https://www.icann.org/en/system/files/files/proposal-hebrew-lgr-24apr19-en.pdf
- [Ref-LGR-Latin-Full-Variant-Script]
- ICANN, Second Level Reference Label Generation Rules for the Latin Script (und-Latn), 25 October 2024 (XML) https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-latin-full-variant-script-25oct24-en.xml non-normative HTML presentation: https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-latin-full-variant-script-25oct24-en.html
- [Ref-LGR-und-Hebr]
- ICANN, Second Level Reference Label Generation Rules for the Hebrew Script (und-Hebr), 25 October 2024 (XML) https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-hebrew-script-25oct24-en.xml non-normative HTML presentation: https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-hebrew-script-25oct24-en.html
- [RFC 7940]
- Davies, K. and A. Freytag, “Representing Label Generation Rulesets Using XML”, RFC 7940, August 2016, https://www.rfc-editor.org/info/rfc7940
- [RFC 8228]
- A. Freytag, “Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels”, RFC 8228, August 2017, https://www.rfc-editor.org/info/rfc8228
- [RZ-LGR-Overview]
- Integration Panel, “Root Zone Label Generation Rules (RZ LGR-5): Overview and Summary”, 26 May 2022 (PDF), https://www.icann.org/sites/default/files/lgr/rz-lgr-5-overview-26may22-en.pdf
- [RZ-LGR-Hebr]
- ICANN, Root Zone Label Generation Rules for the Hebrew Script (und-Hebr), 26 May 2022 (XML) https://www.icann.org/sites/default/files/lgr/rz-lgr-5-hebrew-script-26may22-en.xml
- [Unicode 11.0.0]
- The Unicode Consortium. The Unicode Standard, Version 11.0.0, (Mountain View, CA: The Unicode Consortium, 2018. ISBN 978-1-936213-19-1) https://www.unicode.org/versions/Unicode11.0.0/
For references consulted particularly in designing the repertoire for the Hebrew Script for the second level please see details in the Table of References below.
Reference [0] refers to the Unicode Standard version in which the corresponding code points were initially encoded. Reference [101] corresponds to a source justifying the inclusion of the corresponding code points. Entries in the table may have multiple source reference values. In the listing of whole label evaluation and context rules, references [150] and [160] indicate the source for common rules.
Repertoire
| Glyph | Code point | Tags and context | Variants |
|---|---|---|---|
| - | U+002D HYPHEN-MINUS 0 HYPHEN-MINUS; |
|
|
| 0 | U+0030 DIGIT ZERO 0 DIGIT ZERO; |
|
|
| 1 | U+0031 DIGIT ONE 0 DIGIT ONE; |
|
|
| 2 | U+0032 DIGIT TWO 0 DIGIT TWO; |
|
|
| 3 | U+0033 DIGIT THREE 0 DIGIT THREE; |
|
|
| 4 | U+0034 DIGIT FOUR 0 DIGIT FOUR; |
|
|
| 5 | U+0035 DIGIT FIVE 0 DIGIT FIVE; |
|
|
| 6 | U+0036 DIGIT SIX 0 DIGIT SIX; |
|
|
| 7 | U+0037 DIGIT SEVEN 0 DIGIT SEVEN; |
|
|
| 8 | U+0038 DIGIT EIGHT 0 DIGIT EIGHT; |
|
|
| 9 | U+0039 DIGIT NINE 0 DIGIT NINE; |
|
|
| א | U+05D0 HEBREW LETTER ALEF 0 101 |
|
|
| ב | U+05D1 HEBREW LETTER BET 0 101 |
|
|
| ג | U+05D2 HEBREW LETTER GIMEL 0 101 |
|
|
| ד | U+05D3 HEBREW LETTER DALET 0 101 |
|
|
| ה | U+05D4 HEBREW LETTER HE 0 101 |
|
|
| ו | U+05D5 HEBREW LETTER VAV 0 101 |
|
|
| ז | U+05D6 HEBREW LETTER ZAYIN 0 101 |
|
|
| ח | U+05D7 HEBREW LETTER HET 0 101 |
|
|
| ט | U+05D8 HEBREW LETTER TET 0 101 |
|
|
| י | U+05D9 HEBREW LETTER YOD 0 101 |
|
|
| ך | U+05DA HEBREW LETTER FINAL KAF 0 101 Final form |
|
כ
U+05DB
blocked
Nominal form variant
|
| כ | U+05DB HEBREW LETTER KAF 0 101 Nominal form |
|
ך
U+05DA
blocked
Final form variant
|
| ל | U+05DC HEBREW LETTER LAMED 0 101 |
|
|
| ם | U+05DD HEBREW LETTER FINAL MEM 0 101 Final form |
|
מ
U+05DE
blocked
Nominal form variant
|
| מ | U+05DE HEBREW LETTER MEM 0 101 Nominal form |
|
ם
U+05DD
blocked
Final form variant
|
| ן | U+05DF HEBREW LETTER FINAL NUN 0 101 Final form |
|
נ
U+05E0
blocked
Nominal form variant
|
| נ | U+05E0 HEBREW LETTER NUN 0 101 Nominal form |
|
ן
U+05DF
blocked
Final form variant
|
| ס | U+05E1 HEBREW LETTER SAMEKH 0 101 |
|
|
| ע | U+05E2 HEBREW LETTER AYIN 0 101 |
|
|
| ף | U+05E3 HEBREW LETTER FINAL PE 0 101 Final form |
|
פ
U+05E4
blocked
Nominal form variant
|
| פ | U+05E4 HEBREW LETTER PE 0 101 Nominal form |
|
ף
U+05E3
blocked
Final form variant
|
| ץ | U+05E5 HEBREW LETTER FINAL TSADI 0 101 Final form |
|
צ
U+05E6
blocked
Nominal form variant
|
| צ | U+05E6 HEBREW LETTER TSADI 0 101 Nominal form |
|
ץ
U+05E5
blocked
Final form variant
|
| ק | U+05E7 HEBREW LETTER QOF 0 101 |
|
|
| ר | U+05E8 HEBREW LETTER RESH 0 101 |
|
|
| ש | U+05E9 HEBREW LETTER SHIN 0 101 |
|
|
| ת | U+05EA HEBREW LETTER TAV 0 101 |
|
Variants
Code points grouped into sets of mutual variants. Every member of a set produces the same set of variant labels, so a registration of one has implications for all the others. Sets of a single member are omitted, as are the identity mappings RFC 7940 requires each member to declare.
Rules
Conditions evaluated against a whole label, or against the context around a
single code point. The notation borrows from regular expressions:
^ and $ anchor to the start and end of a label,
. matches any code point, (?= ) and
(?<= ) look ahead and behind, and * and
+ repeat. Two symbols are specific to rulesets:
◆ is the code point being tested, and
⟨name⟩ refers to another rule.
leading-combining-mark MSR default 150
RFC 5891 restrictions on placement of combining marks
^ ({gc:Mn} ∪ {gc:Mc})
Structure
-
^start -
({gc:Mn} ∪ {gc:Mc})union-
{gc:Mn}class -
{gc:Mc}class
-
Referenced by 1 definition
- action 1 (invalid)
hyphen-minus-disallowed MSR default 150
RFC 5891 restrictions on placement of U+002D HYPHEN-MINUS
( ( (?<= ^ ) ◆ ) │ ( ◆ (?= $ ) ) │ ( (?<= ^ . . U+002D ) ◆ ) )
Structure
-
( ( (?<= ^ ) ◆ ) │ ( ◆ (?= $ ) ) │ ( (?<= ^ . . U+002D ) ◆ ) )choice-
(?<= ^ ) ◆rule-
(?<= ^ )look-behind-
^start
-
-
◆anchor
-
-
◆ (?= $ )rule-
◆anchor -
(?= $ )look-ahead-
$end
-
-
-
(?<= ^ . . U+002D ) ◆rule-
(?<= ^ . . U+002D )look-behind-
^start -
.any -
.any -
U+002Dchar
-
-
◆anchor
-
-
Referenced by 1 definition
- negative context of U+002D
leading-digit MSR default 160
RFC 5893 RTL labels cannot start with a digit
(?<= ^ ) ◆
Structure
-
(?<= ^ )look-behind-
^start
-
-
◆anchor
Referenced by 10 definitions
- negative context of U+0030
- negative context of U+0031
- negative context of U+0032
- negative context of U+0033
- negative context of U+0034
- negative context of U+0035
- negative context of U+0036
- negative context of U+0037
- negative context of U+0038
- negative context of U+0039
Actions
Actions are evaluated in the order shown. The first action whose conditions match determines the disposition of the label.
| # | Disposition | Conditions |
|---|---|---|
| 1 |
invalid
|
label matches leading-combining-mark 150 labels with leading combining marks are invalid MSR default |
| 2 |
invalid
|
any variant is out-of-repertoire-var any variant label with a code point out of repertoire is invalid MSR default |
| 3 |
blocked
|
any variant is blocked any variant label containing blocked variants is blocked MSR default |
| 4 |
allocatable
|
all variants are allocatable variant labels with all variants allocatable are allocatable MSR default |
| 5 |
valid
|
any label default catch all (default action) MSR default |