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 Gurmukhi Script

Overview

This document specifies a set of Label Generation Rules (LGR) for the Gurmukhi 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-Guru]. The format of this file follows [RFC 7940]. This LGR is adapted from the “Reference LGR for the Second Level for the Gurmukhi Script” [Ref-LGR-und-Guru], for details, see Change History below.

For details and additional background on the Gurmukhi script, see “Proposal for a Gurmukhi Script Root Zone Label Generation Ruleset (LGR)" [Proposal-Gurmukhi].

Repertoire

The repertoire contains 56 codepoints for letters used by the Punjabi language written using the Gurmukhi script. Punjabi ([EGIDS] level 2) is the only language currently using the Gurmukhi script. The repertoire is a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Gurmukhi]. (The proposal cited has been adopted for the Gurmukhi script portion of the Root Zone LGR.)

For the second level, the repertoire has been augmented with the ASCII digits, U+0030 0 to U+0039 9, plus U+002D - HYPHEN-MINUS, for a total of 67 repertoire elements.

Any code points outside the Gurmukhi 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, one or more tag values denoting character category, and one or more references documenting sufficient justification for inclusion in the repertoire, see “References” below. Comments provide alternate names 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 Bengali and Devanagari in the same zone will create potential cross-script issues. For details, see Section 6, “Variants” in [Proposal-Gurmukhi]. 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 Bengali and Devanagari LGR(s) can be found in the following LGR: [Ref-LGR-Devanagari-Full-Variant-Script]

There are no in-script variants defined for Gurmukhi. See Section 6, “Variants” in [Proposal-Gurmukhi].

Digit Variants: The Gurmukhi reference LGR does not include native digits, so there are no semantic variants defined.

Variant Disposition: All variants are of type “blocked”, making labels that differ only by these variants mutually exclusive: whichever label containing either of these variants is chosen earlier would be delegated, while any other equivalent labels should be blocked. There is no preference among these labels.

This LGR does not define allocatable variants.

The specification of variants in this LGR follows the guidelines in [RFC 8228].

Character Classes

Gurmukhi is an alphasyllabary and the heart of the writing system is the akshar. This is the unit which is instinctively recognized by users of the script. The elements of the writing system consist of Consonants, Implicit Vowel Killer: Halant, Vowels, Bindi, Tippi, Addak, Nukta and Visarga.

Consonants: Gurmukhi consonants contain an implicit vowel schwa /ə/. They are also used without any modification to represent consonant sounds without an implicit /ə/ vowel More details in Section 3.3.1, “The Consonants” in [Proposal-Gurmukhi].

Virama: Unlike the Halant in other Neo-Brahmi scripts, U+094D  ्  GURMUKHI SIGN VIRAMA is not used in general to strip a consonant letter’s implicit vowel. The Virama is only used to create a conjunct where the letter U+0A39 ਹ HA, U+0A30 ਰ RA or U+0A35 ਵ VA is the second element in a conjunct. More details in Section 3.3.2, “The Implicit Vowel Killer: Virama” in [Proposal-Gurmukhi].

Vowels and Matras: Punjabi has seven long vowels and three short vowels (ਅ /ə/, ਇ /I/, and ਉ /U/) . Each of them, except U+0A05 ਅ have a corresponding vowel sign, or matra, which is used to modify the vowel inherent in the preceding consonant. More details in Section 3.3.3, “Vowels” in [Proposal-Gurmukhi].

Bindi: Bindi represents a homo-organic nasal. Bindi is used with all long vowels and the short vowel U+0A09 ਉ, as well as with the matras of long vowels, except the matra U+0A42  ੂ . More details in Section 3.3.4.1, “The Bindi” in [Proposal-Gurmukhi].

Tippi: Tippi is used to nasalize short vowels /ə/ and /I/ at all places, as well as /U/ and /u/ after a consonant. Therefore, Tippi comes after consonants without a vowel sign (representing the matra of /ə/ “mukta”) and after the matra of /I/ ( ਿ ) following vowel carriers and consonants, such as in ਸੰ and ਸਿੰ. The matras of /U/ ( ੁ,) and /u/ ( ੂ ) following a consonant also take a Tippi. In addition, Tippi is used in gemination for nasal consonants ਙ, ਞ, ਨ and ਮ. More details in Section 3.3.4.2, “The Tippi” in [Proposal-Gurmukhi].

Addak: Addak is used to mark the gemination of the following consonant. In Punjabi, addak usually can follow mukta, aunkar ( ੁ ) and sihari ( ਿ ), and the vowel signs of the short vowels /ə/, /u/ and /i/. It geminates the consonant that follows it; therefore it cannot occur at the end of a label. More details in Section 3.3.4.3 “The Addak” in [Proposal-Gurmukhi].

Nukta: Called pairin bindi in Punjabi, Nukta is used with the six consonants (ਸ, ਖ, ਗ, ਜ, ਫ and ਲ ) defined as set C1 to represent the phonemes of words of Sanskrit and Perso-Arabic sources. More details in Section 3.3.4.4, “Nukta” in [Proposal-Gurmukhi].

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].

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].

Gurmukhi-specific Rules

These rules have been drafted to ensure that the prospective Gurmukhi label conforms to akshar formation norms as desired in Gurmukhi script. These norms are exclusively presented as context rules.

The following symbols are used in the WLE rules:
C → Consonant
M → Matra
V → Vowel
B → Bindi
D → Tippi
A → Addak
H → Virama / Halant
N → Nukta
M1 → { ਿ(U+0A3F), ੁ (U+0A41) } (Short matras)
M2 → M - M1 (Long matras)
V1 → { ਅ (U+0A05), ਇ (U+0A07), ਉ (U+0A09)} (Short Vowels)
V2 → V - V1 (Long Vowel)
C1 → {ਖ (U+0A16), ਗ (U+0A17), ਜ (U+0A1C), ਫ (U+0A2B), ਲ (U+0A32), ਸ (U+0A38)}
C2 → { ਰ (U+0A30), ਵ (U+0A35), ਹ (U+0A39)}
C3 → C – {ਙ (U+0A19), ਞ (U+0A1E), ਣ (U+0A23), ਹ (U+0A39), ੜ (U+0A5C)}

The rules are:

• 7.1 N: must be preceded by C1
• 7.2 H: must be preceded by C or N and followed by C2
• 7.3 M: must be preceded by C or N
• 7.4 B: must be preceded by specific V or M
• 7.5 D: must be preceded by C, N or specific V or M
• 7.6 A: must be preceded by C, N or specific V or M and followed by C3

More details in Section 7, “Whole Label Evaluation Rules (WLE)” in [Proposal-Gurmukhi].

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 Gurmukhi Script was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Gurmukhi script and information contained or referenced therein; see [RZ-LGR-Guru]. 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 Gurmukhi script, that this reference LGR is based on, was developed by the Neo-Brahmi Generation Panel (NBGP). For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Gurmukhi], as well as [RZ-LGR-Overview].

Changes from Version Dated 15 December 2020

Unicode Version has been updated.

Changes from Version Dated 24 January 2024

Adopted from the Second Level Reference LGR for the Gurmukhi Script [Ref-LGR-und-Guru] without normative changes.

References

The following general references are cited in this document:

[EGIDS]

Lewis and Simons, “EGIDS: Expanded Graded Intergenerational Disruption Scale,” documented in [SIL-Ethnologue] and summarized here:
https://en.wikipedia.org/wiki/Expanded_Graded_Intergenerational_Disruption_Scale_(EGIDS)

[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

[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, 24 January 2024),
https://www.icann.org/en/system/files/files/level2-lgr-overview-summary-24jan24-en.pdf

[Gurmukhi-Chart]

Gurmukhi Unicode chart (Accessed on 21 May 2018)
https://unicode.org/charts/PDF/U0A00.pdf

[Proposal-Gurmukhi]

Neo-Brahmi Generation Panel, “Proposal for a Gurmukhi Script Root Zone Label Generation Ruleset (LGR)”, 22 April 2019,
https://www.icann.org/en/system/files/files/proposal-gurmukhi-lgr-22apr19-en.pdf

[Ref-LGR-und-Guru]

ICANN, Second Level Reference Label Generation Rules for the Gurmukhi Script (und-Guru), 24 January 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-gurmukhi-script-24jan24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-gurmukhi-script-24jan24-en.html

[Ref-LGR-Devanagari-Full-Variant-Script]

ICANN, Second Level Reference Label Generation Rules for the Devanagari Script (und-Deva), 24 January 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-devanagari-full-variant-script-24jan24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-devanagari-full-variant-script-24jan24-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-Guru]

ICANN, Root Zone Label Generation Rules for the Gurmukhi Script (und-Guru), 26 May 2022 (XML)
https://www.icann.org/sites/default/files/lgr/rz-lgr-5-gurmukhi-script-26may22-en.xml

[SIL-Ethnologue]

David M. Eberhard, Gary F. Simons & Charles D. Fennig (eds.). 2021. Ethnologue: Languages of the World, Twenty fourth edition. Dallas, Texas: SIL International. Online version available as
https://www.ethnologue.com

[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 Gurmukhi 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. References [105] and above correspond to sources given in [Proposal-Gurmukhi] 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, reference [150] indicates the source for common rules.

Character Classes

Number of named classes	11
Implicit (except script)	5
Implict defined by script tag	2

The following table lists all named and implicit classes with their definition and a list of their members intersected with the current repertoire (for larger classes, this list is elided).

Name	Definition	Count	Members or Ranges	Ref	Comment
C	Tag=Consonant	32	{0A15-0A28 0A2A-0A30 0A32 0A35 0A38-0A39 0A5C}		Any Gurmukhi consonant
V	Tag=Vowel	10	{0A05-0A0A 0A0F-0A10 0A13-0A14}		Any Gurmukhi independent vowel
M	Tag=Matra	9	{0A3E-0A42 0A47-0A48 0A4B-0A4C}		Any Gurmukhi vowel sign (matra)
N	Tag=Nukta	1	{0A3C}		The Gurmukhi Nukta
V1	Tag=V1	3	{0A05 0A07 0A09}		Specific vowels that are used with Gurmukhi Addak
V2	combined = [[:V:] ∖ [:V1:]]	7	{0A06 0A08 0A0A 0A0F-0A10 0A13-0A14}		Specific vowels that are used with Gurmukhi Bindi
M1	Tag=M1	2	{0A3F 0A41}		Gurmukhi short matras
M2	combined = [[:M:] ∖ [:M1:]]	7	{0A3E 0A40 0A42 0A47-0A48 0A4B-0A4C}		Gurmukhi long matras
C1	Tag=C1	6	{0A16-0A17 0A1C 0A2B 0A32 0A38}		Specific consonants preceding Gurmukhi Nukta
C2	Tag=C2	3	{0A30 0A35 0A39}		Specific consonants following Gurmukhi Halant
C3	combined = [[:C:] ∖ [0A19 0A1E 0A23 0A39 0A5C]]	27	{0A15-0A18 0A1A-0A1D 0A1F-0A22 0A24-0A28 0A2A-0A30 0A32 0A35 0A38}		Specific consonants following Gurmukhi Addak
implicit	Tag=Addak	1	{0A71}		The character tagged as Addak
implicit	Tag=Bindi	1	{0A02}		The character tagged as Bindi
implicit	Tag=Common-digit	10	{0030-0039}		Any character tagged as Common-digit
implicit	Tag=Tippi	1	{0A70}		The character tagged as Tippi
implicit	Tag=Virama	1	{0A4D}		The character tagged as Virama
implicit	Tag=sc:Guru	56	{0A02 0A05-0A0A 0A0F-0A10 0A13-0A28 0A2A-0A30 0A32 0A35 0A38-0A39 0A3C 0A3E-0A42 0A47-0A48 0A4B-0A4D 0A5C 0A70-0A71}		Any character tagged as Gurmukhi
implicit	Tag=sc:Zyyy	11	{002D 0030-0039}		Any character tagged as Common

Legend

Members or Ranges

Lists the members of the class as code points (xxx) or as ranges of code points (xxx-yyy). Any class too numerous to list in full is elided with "...".

Tag=ttt

A named or implicit class defined by all code points that share the given tag value (ttt).

Implicit

An anonymous class implicitly defined based on tag value and for which there is no named equivalent.

Combined

A named class defined by set operations on other classes using the following syntax:

[ ] - explicit character set

For explicit character sets that are part of a rule, only those members are shown that are defined in this LGR.

[: :] - named or implicit character set

Reference to a named character set [:name:] or an implicit character set [:tag:]. A leading “^” before name or tag indicates the set complement.

∪, ∩, ∖, ∆ - set operators

Sets may be combined by set operators (∪ = union, ∩ = intersection, ∖ = difference, ∆ = symmetric difference).

Whole label evaluation and context rules

Number of rules	8
Used to trigger actions	1
Used as context rule (C)	7
Anchored context rules	7

The following table lists all named rules defined in the LGR and indicates whether they are used as trigger in an action or as context (when or not-when) for a code point or variant.

Name	Regular Expression	Used as Trigger	Anchor	Used as Context	Ref	Comment
leading-combining-mark	(start)[[\p{gc=Mn}] ∪ [\p{gc=Mc}]]	✔			[150]	RFC 5891 restrictions on placement of combining marks ⍟
hyphen-minus-disallowed	(((start))← ⚓︎)|(⚓︎ →((end)))|(((start)..\u002D)← ⚓︎)		✔	C	[150]	RFC 5891 restrictions on placement of U+002D - ⍟
follows-C1	([:C1:])← ⚓︎		✔	C		Section 7.1. N: must be preceded by C1
follows-C-or-N-and-precedes-C2	([:C:]|[:N:])← ⚓︎ →([:C2:])		✔	C		Section 7.2. H: must be preceded by C or N and followed by C2
follows-C-or-N	([:C:]|[:N:])← ⚓︎		✔	C		Section 7.3. M: must be preceded by C or N
follows-specific-V-or-M	([:V2:]|\u0A09|([[:M2:] ∖ [\u0A42]]))← ⚓︎		✔	C		Section 7.4. Bindi must be preceded by specific V or M
follows-C-N-or-specific-V-or-M	([:C:]|[:N:]|([[:V1:] ∖ [\u0A09]])|[:M1:]|\u0A42)← ⚓︎		✔	C		Section 7.5. Tippi must be preceded by C, N or specific V or M
follows-C-N-or-specific-V-or-M-and-precedes-C3	([:C:]|[:N:]|[:V1:]|\u0A10|[:M1:]|\u0A48)← ⚓︎ →([:C3:])		✔	C		Section 7.6. Addak must be preceded by C, N or specific V or M and followed by C3

Legend

Used as Trigger

This rule triggers one of the actions listed below.

Used as Context

This rule defines a required or prohibited context for a code point C or variant V.

Anchor

This rule has a placeholder for the code point for which it is evaluated.

Regular Expression

A regular expression equivalent to the rule, shown in a modified notation as noted:

⚓︎ - context anchor

Placeholder for the actual code point when a context is evaluated. The code point must occur at the position corresponding to the anchor. Rules containing an anchor cannot be used as triggers.

(...)← - look-behind

If present encloses required context preceding the anchor.

→(..) - look-ahead

If present encloses required context following the anchor.

( ) - group

An anonymous nested rule is used to group match operators.

(... | ...) - choice

When there is more than one alternative in a rule, the choices are separated by the alternation operator (...|...).

start or end

(start) matches the start of the label; (end) matches the end of the label.

. - any code point

. matches any code point.

[ ] - explicit character set

For explicit character sets that are part of a rule, only those members are shown that are defined in this LGR.

[: :] - named or implicit character set

Reference to a named character set [:name:] or an implicit character set [:tag:]. A leading “^” before name or tag indicates the set complement.

[\p{ }] - property

Set of all characters matching a given value for a Unicode property [\p{prop=val}]. Note: uppercase “\P” defines the complement of a property set.

∪, ∩, ∖, ∆ - set operators

Sets may be combined by set operators (∪ = union, ∩ = intersection, ∖ = difference, ∆ = symmetric difference).

⍟ - default rule

Rules marked with ⍟ are included by default and may or may not be triggered by any possible label under this LGR.

Actions

The following table lists the actions that are used to assign dispositions to labels and variant labels based on the specified conditions. The order of actions defines their precedence: the first action triggered by a label is the one defining its disposition.

#	Condition	Rule / Variant Set		Disposition	Ref	Comment
1	if label matches	leading-combining-mark	→	invalid	[150]	labels with leading combining marks are invalid ⍟
2	if at least one variant is in	{out-of-repertoire-var}	→	invalid		any variant label with a code point out of repertoire is invalid ⍟
3	if at least one variant is in	{blocked}	→	blocked		any variant label containing blocked variants is blocked ⍟
4	if each variant is in	{allocatable}	→	allocatable		variant labels with all variants allocatable are allocatable ⍟
5	if any label (catch-all)		→	valid		catch all (default action) ⍟

Legend

{...} - variant type set

In the “Rule/Variant Set” column, the notation {...} means a set of variant types.

⍟ - default action

Actions marked with ⍟ are included by default and may or may not be triggered by any possible label under this LGR.

Note: The following variant types are used in one or more actions, but are not defined in this LGR: allocatable, out-of-repertoire-var. This is not necessarily an error.