Root Zone LGR for script: Tamil (Taml)	rz-lgr-6-tamil-script-23sep25-en

This document is mechanically formatted from the above XML file for the LGR. It provides additional summary data and explanatory text. The XML file remains the sole normative specification of the LGR.

Date	2025-09-23
LGR Version	6 (Root Zone LGR for the Tamil Script)
Language	und-Taml (Tamil Script)
Scope	domain: "." (Root)
Unicode Version	16.0.0

Description

Root Zone Label Generation Rules for the Tamil Script

Overview

This file contains a set of Label Generation Rules (LGR) for the Tamil script for the Root Zone. For more details on this LGR and additional background on the script, see “Proposal for a Tamil Script Root Zone Label Generation Rule-Set (LGR)” [Proposal-Tamil]. This file is one of a set of LGR files that together form an integrated LGR for the DNS Root Zone [RZ-LGR-6]. The format of this file follows [RFC 7940].

Repertoire

According to Section 5, “Repertoire” in [Proposal-Tamil] the Tamil LGR contains 48 single code points and 4 , for a total of 52 repertoire elements. This LGR caters to the Tamil language written using Tamil script.

The repertoire is contained in [MSR-6], which is a subset of [Unicode 16.0.0].

As part of the Root Zone, this LGR includes neither decimal digits nor the HYPHEN-MINUS.

Repertoire Listing: Each code point or range is tagged with the script or scripts with which the code point is used and one or more other character categories. For each repertoire element, one or more references document sufficient justification for inclusion in the repertoire; see the “References” below. Comments provide alternate names for some code points.

Code points outside the Tamil script repertoire that are listed in this file are targets for out-of-repertoire variants and are identified by a reflexive (identity) variant of type “out-of-repertoire-var”. They do not form part of the repertoire.

Variants

According to Section 6, “Variants”, in [Proposal-Tamil], this LGR defines four sequences as in-script variants. Two of them are variants to single code points; the other two are variants of each other; all defined variants look exactly alike and can cause confusion even to a careful observer.

In addition to these, this LGR defines 6 cross-script variants with the Malayalam script.

Variant Disposition: Except as noted, 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 label should be blocked.

For historical reasons, there are two sequences that both represent the same akshar (Shri) with exactly the same rendered form. These two sequences are thus semantically identical and users may choose either one, except that a single label must use one of these forms consistently. This variant pair is thus being defined as “allocatable” variant. (For more details see Section 6.1 in [Proposal-Tamil].)

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

Character Classes

Tamil 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 writing system of Tamil could be summed up as composed of Consonants, the Implicit Vowel Killer: Halant, Vowels and Visarga/Aytham.

Consonants: More details in Section 3.3.1, “The Consonants” in [Proposal-Tamil].

Halant / Virama: All consonants contain an implicit vowel /a/. A special sign is needed to denote that this implicit vowel is stripped off. This is known as the Pulli and encoded as U+0BCD ் TAMIL SIGN VIRAMA. The virama thus joins two adjacent consonants. In Tamil, there are only two cases where this forms conjuncts. More details in Section 3.3.2, “Virama/Pulli” of the [Proposal-Tamil].

Vowels and Matras: Separate symbols exist for all Vowels that are pronounced independently either at the beginning or after another vowel sound. To indicate a Vowel sound other than the implicit one following a consonant, a Vowel sign (matra) is attached to the consonant. Since the consonant has a built-in /a/, there are equivalent Matras for all vowels excepting the அ. More details in Section 3.3.3, “Vowels” in [Proposal-Tamil].

Visarga: The Visarga (or Aytham) is used in Tamil to represent a sound very close to /ḵ/. More details in Section 3.3.4, “Visarga/Aytham” in [Proposal-Tamil].

Whole Label Evaluation (WLE) and Context Rules

Default Whole Label Evaluation Rules and Actions

The LGR includes the set of required default WLE rules and actions applicable to the Root Zone and defined in [MSR-6]. They are marked with ⍟. The default prohibition on leading combining marks is equivalent to ensuring that a label only starts with a consonant or vowel. The actions compute a label disposition based on WLE rules or variant mapping types.

Tamil-specific Rules and Action

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

The following symbols are used in the WLE rules:
C → Consonant
M → Matra
H → Halant / Virama = Pulli
X → Visarga = Aytham

The rules are:

H: must be preceded by C
M: must be preceded by C
X: cannot be preceded by X

The following whole-label rule and associated action prevent the mixing of two allocatable variants of the same sequence within the same label. This reduces overproduction of variant labels.

Two representations of ‘Shri’ cannot be mixed in the same label

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

Methodology and Contributors

The Root Zone LGR for the Tamil Script was developed by the Neo-Brahmi Generation Panel (NBGP), the members of which have experience in linguistics and computational linguistics in a wide variety of languages written with Neo-Brahmi scripts. Under the Neo-Brahmi Generation Panel, there are nine scripts belonging to separate Unicode blocks. Each of these scripts has been assigned a separate LGR, with the Neo-Brahmi GP ensuring that the fundamental philosophy behind building each LGR is in sync with all other Brahmi-derived scripts. For further details on methodology and contributors, see Sections 4 and 8 in [Proposal-Tamil], as well as [RZ-LGR-6-Overview].

Changes from RZ LGR-4

RZ LGR-5 changed the implementation of rule “preceded-by-X” to use “look-behind” instead of “look-ahead”. As the rule prevents two adjacent Visargas, the change has no effect on the restriction imposed, but the change makes it easier for a reader to verify that the rule is correctly implemented.

References

The following general references are cited in this document:

[MSR-6]: Integration Panel, “Maximal Starting Repertoire — MSR-6 Overview and Rationale”, 23 September 2025,
https://www.icann.org/en/system/files/files/msr-6-overview-23sep25-en.pdf
[Proposal-Tamil]: Neo-Brahmi Generation Panel, “Proposal for a Tamil Script Root Zone Label Generation Rule-Set (LGR)”, 6 March 2019,
https://www.icann.org/en/system/files/files/proposal-tamil-lgr-06mar19-en.pdf
[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-6-Overview]: Integration Panel, “Root Zone Label Generation Rules (RZ LGR-6): Overview and Summary”, 23 September 2025,
https://www.icann.org/sites/default/files/lgr/rz-lgr-6-overview-23sep25-en.pdf
[RZ-LGR-6]: Integration Panel, “Root Zone Label Generation Rules (RZ-LGR-6)”, 23 September 2025 (XML),
https://www.icann.org/sites/default/files/lgr/rz-lgr-6-common-23sep25-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/lgr/rz-lgr-6-common-23sep25-en.html
[Unicode 16.0.0]: The Unicode Consortium. The Unicode Standard, Version 16.0.0, (South San Francisco: The Unicode Consortium, 2024. ISBN 978-1-936213-34-4)
https://www.unicode.org/versions/Unicode16.0.0/

For references consulted, particularly in designing the repertoire for the Tamil script for the Root Zone, please see details in the Table of References below. References [0] and [7] refer to the Unicode Standard versions in which the corresponding code points were initially encoded. References [101] and above correspond to sources given in [Proposal-Tamil] justifying the inclusion of the corresponding code points. Entries in the table may have multiple source reference values.

Repertoire

Repertoire Summary

Number of elements in repertoire

Out-of-repertoire variants

Total entries in table

Number of code points
for each script

Malayalam	6
Tamil	48

Number of code points

Number of sequences

Longest code point sequence

Repertoire by Code Point

The following table lists the repertoire by code point (or code point sequence). The data in the Script and Name column are extracted from the Unicode character database. Where a comment in the original LGR is equal to the character name, it has been suppressed.

For any code point or sequence for which a variant is defined, additional information is provided in the Variants column. Some code points or sequences listed in the following table are not part of the repertoire itself; they document targets for out-of-repertoire variant mappings as indicated. See also the legend provided below the table.

Code Point	Glyph	Script	Name	Ref	Tags	Required Context	Part of Repertoire	Variants	Comment
U+0B83	ஃ	Tamil	TAMIL SIGN VISARGA	[0], [103]	Visarga	not: preceded-by-X	✔		= aytham
U+0B85	அ	Tamil	TAMIL LETTER A	[0], [101]	Vowel		✔
U+0B86	ஆ	Tamil	TAMIL LETTER AA	[0], [101]	Vowel		✔
U+0B87	இ	Tamil	TAMIL LETTER I	[0], [101]	Vowel		✔
U+0B88	ஈ	Tamil	TAMIL LETTER II	[0], [101]	Vowel		✔
U+0B89	உ	Tamil	TAMIL LETTER U	[0], [101]	Vowel		✔
U+0B8A	ஊ	Tamil	TAMIL LETTER UU	[0], [101]	Vowel		✔
U+0B8E	எ	Tamil	TAMIL LETTER E	[0], [101]	Vowel		✔
U+0B8F	ஏ	Tamil	TAMIL LETTER EE	[0], [101]	Vowel		✔
U+0B90	ஐ	Tamil	TAMIL LETTER AI	[0], [101]	Vowel		✔
U+0B92	ஒ	Tamil	TAMIL LETTER O	[0], [101]	Vowel		✔
U+0B92 U+0BB3	ஒள	{Tamil}	TAMIL LETTER O + TAMIL LETTER LLA		[Vowel] + [Consonant]		✔	set 1	homoglyph of U+0B94 ஔ
U+0B93	ஓ	Tamil	TAMIL LETTER OO	[0], [101]	Vowel		✔
U+0B94	ஔ	Tamil	TAMIL LETTER AU	[0], [101]	Vowel		✔	set 1
U+0B95	க	Tamil	TAMIL LETTER KA	[0], [102]	Consonant		✔
U+0B99	ங	Tamil	TAMIL LETTER NGA	[0], [102]	Consonant		✔
U+0B9A	ச	Tamil	TAMIL LETTER CA	[0], [102]	Consonant		✔
U+0B9C	ஜ	Tamil	TAMIL LETTER JA	[0], [102]	Consonant		✔	set 2
U+0B9E	ஞ	Tamil	TAMIL LETTER NYA	[0], [102]	Consonant		✔
U+0B9F	ட	Tamil	TAMIL LETTER TTA	[0], [102]	Consonant		✔
U+0BA3	ண	Tamil	TAMIL LETTER NNA	[0], [102]	Consonant		✔
U+0BA4	த	Tamil	TAMIL LETTER TA	[0], [102]	Consonant		✔
U+0BA8	ந	Tamil	TAMIL LETTER NA	[0], [102]	Consonant		✔
U+0BA9	ன	Tamil	TAMIL LETTER NNNA	[0], [102]	Consonant		✔
U+0BAA	ப	Tamil	TAMIL LETTER PA	[0], [102]	Consonant		✔
U+0BAE	ம	Tamil	TAMIL LETTER MA	[0], [102]	Consonant		✔	set 3
U+0BAF	ய	Tamil	TAMIL LETTER YA	[0], [102]	Consonant		✔
U+0BB0	ர	Tamil	TAMIL LETTER RA	[0], [102]	Consonant		✔
U+0BB1	ற	Tamil	TAMIL LETTER RRA	[0], [102]	Consonant		✔
U+0BB2	ல	Tamil	TAMIL LETTER LA	[0], [102]	Consonant		✔
U+0BB3	ள	Tamil	TAMIL LETTER LLA	[0], [102]	Consonant		✔
U+0BB4	ழ	Tamil	TAMIL LETTER LLLA	[0], [102]	Consonant		✔
U+0BB5	வ	Tamil	TAMIL LETTER VA	[0], [102]	Consonant		✔	set 4
U+0BB6	ஶ	Tamil	TAMIL LETTER SHA	[7], [102]	Consonant		✔
U+0BB6 U+0BCD U+0BB0 U+0BC0	ஶ்ரீ	{Tamil}	TAMIL SYLLABLE SHRII		[Consonant] + [Halant] + [Consonant] + [Matra]		✔	set 5
U+0BB7	ஷ	Tamil	TAMIL LETTER SSA	[0], [102]	Consonant		✔
U+0BB8	ஸ	Tamil	TAMIL LETTER SA	[0], [102]	Consonant		✔
U+0BB8 U+0BCD U+0BB0 U+0BC0	ஸ்ரீ	{Tamil}	TAMIL LETTER SA + TAMIL SIGN VIRAMA + TAMIL LETTER RA + TAMIL VOWEL SIGN II		[Consonant] + [Halant] + [Consonant] + [Matra]		✔	set 5	Alternate for Tamil SHRII
U+0BB9	ஹ	Tamil	TAMIL LETTER HA	[0], [102]	Consonant		✔
U+0BBE	ா	Tamil	TAMIL VOWEL SIGN AA	[0], [102]	Matra	follows-C	✔
U+0BBF	ி	Tamil	TAMIL VOWEL SIGN I	[0], [102]	Matra	follows-C	✔	set 6
U+0BC0	ீ	Tamil	TAMIL VOWEL SIGN II	[0], [102]	Matra	follows-C	✔
U+0BC1	ு	Tamil	TAMIL VOWEL SIGN U	[0], [102]	Matra	follows-C	✔
U+0BC2	ூ	Tamil	TAMIL VOWEL SIGN UU	[0], [102]	Matra	follows-C	✔
U+0BC6	ெ	Tamil	TAMIL VOWEL SIGN E	[0], [102]	Matra	follows-C	✔	set 7
U+0BC6 U+0BB3	ெள	{Tamil}	TAMIL VOWEL SIGN E + TAMIL LETTER LLA		[Matra] + [Consonant]	follows-C	✔	set 8	homoglyph of U+0BCC ௌ
U+0BC7	ே	Tamil	TAMIL VOWEL SIGN EE	[0], [102]	Matra	follows-C	✔	set 9
U+0BC8	ை	Tamil	TAMIL VOWEL SIGN AI	[0], [102]	Matra	follows-C	✔
U+0BCA	ொ	Tamil	TAMIL VOWEL SIGN O	[0], [102]	Matra	follows-C	✔
U+0BCB	ோ	Tamil	TAMIL VOWEL SIGN OO	[0], [102]	Matra	follows-C	✔
U+0BCC	ௌ	Tamil	TAMIL VOWEL SIGN AU	[0], [102]	Matra	follows-C	✔	set 8
U+0BCD	்	Tamil	TAMIL SIGN VIRAMA	[0], [102]	Halant	follows-C	✔		= pulli
U+0D16	ഖ	Malayalam	MALAYALAM LETTER KHA	[0]			✗	set 4	Not part of repertoire
U+0D1C	ജ	Malayalam	MALAYALAM LETTER JA	[0]			✗	set 2	Not part of repertoire
U+0D25	ഥ	Malayalam	MALAYALAM LETTER THA	[0]			✗	set 3	Not part of repertoire
U+0D3F	ി	Malayalam	MALAYALAM VOWEL SIGN I	[0]			✗	set 6	Not part of repertoire
U+0D46	െ	Malayalam	MALAYALAM VOWEL SIGN E	[0]			✗	set 7	Not part of repertoire
U+0D47	േ	Malayalam	MALAYALAM VOWEL SIGN EE	[0]			✗	set 9	Not part of repertoire

Legend

Throughout this document, a code point sequence may be annotated with a string in ALL CAPS that is constructed on the same principle as a name for a Unicode Named Sequence. No claim is made that a sequence thus annotated is in fact a named sequence, nor that the annotation in such case actually corresponds to the formal name of a named sequence.

Code Point: A code point or code point sequence.
Glyph: The shape displayed depends on the fonts available to your browser.
Script: Shows the script property value from the Unicode Character Database. Combining marks may have the value Inherited and code points used with more than one script may have the value Common. Sequences are annotated with a set of all distinct script values.
Name: Shows the character or sequence name from the Unicode Character Database. Named sequences are listed with their normative names, for ad-hoc sequences the individual names are shown separated by “+”.
Ref: Links to the references associated with the code point or sequence, if any.
Tags: LGR-defined tag values. Any tags matching the Unicode script property are suppressed in this view. For sequences, the tags for all member code points are shown in [] for information; sequences as such do not have tags.
Required Context: Link to a rule defining the required context a code point or sequence must satisfy. If prefixed by “not:” identifies a context that must not occur.
Variants: Link to the variant set the code point or sequence is a member of, except where a coded point or sequence maps only to itself, in which case the type of that mapping is listed.
Comment: The comment as given in the XML file. However, if the comment for this row consists only of the code point or sequence name, it is suppressed in this view. By convention, comments starting with “=” denote an alias. If present, the symbol ⍟ marks a default item shared among a set of LGRs.
✔ - core repertoire: A check mark in the Part-of-repertoire column indicates a code point is part of the core repertoire.
✗ - out-of-repertoire: A code point shown with ✗ is not part of the repertoire. It is listed only because it is the target of an out-of-repertoire-var variant mapping.

Variants

Variant Set Summary

Number of variant sets

Largest variant set

Ordinary Variants by Type

allocatable	2
blocked	16

Reflexive Variants by Type

out-of-repertoire-var

Variant Sets

The following tables list all variant sets defined in this LGR, except for singleton sets. Each table lists all variant mapping pairs of the set; one per row. Mappings are assumed to be symmetric: each row documents both forward (→) and reverse (←) mapping directions. In each table, the mappings are sorted by Source value in ascending code point order; shading is used to group mappings from the same source code point or sequence.

Where the type of both forward and reverse mappings are the same, a single value is given in the Type column; otherwise the types for forward and reverse mappings, as well as comments and references, are listed above one another. For summary counts, both forward and reverse mappings are always counted separately.

A mapping where source and target are the same is reflexive. Variant sets consisting of only a single reflexive mapping are not shown as a set. Instead, the variant type of the mapping is listed in the Variants column of the Repertoire by Code Point table. Reflexive mappings that are part of a larger set are indicated with a “≡” and are counted once per entry.

In any LGR with variant specifications that are well behaved, all members within each variant set are defined as variants of each other; the mappings in each set are symmetric and transitive; and all variant sets are disjoint.

Common Legend

Source: By convention, the smaller of the two code points in a variant mapping pair.
Target: By convention, the larger of the two code points in a variant mapping pair.
Glyph: The shape displayed for source or target depends on the fonts available to your browser.
→ - forward: Indicates that Type, Ref and Comment apply to the mapping from source to target.
← - reverse: Indicates that Type, Ref and Comment apply to the reverse mapping from target to source.
↔ - both: Indicates that Type, Ref and Comment apply to both forward and reverse mapping.
≡ - reflexive: Indicates that Type, Ref and Comment are for a reflexive mapping where source equals target.
Type: The type of the variant mapping, including predefined variant types such as “allocatable” and “blocked”; or any that are defined specifically for this LGR. A reflexive variant type “out-of-repertoire-var” designates the target as not part of the repertoire; it is required as target for one or more variant mappings that cross repertoire boundaries. In this LGR, types for variant mappings between out-of-repertoire code points are shown in italic while types for pure in-repertoire variant mappings are shown in bold.
Ref: One or more reference IDs (optional). A “/” separates references for reverse / forward mappings, if different.
Comment: A descriptive comment (optional). A “/” separates comments for reverse / forward mappings, if different.

Variant Set 1 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0B92 0BB3	ஒள	0B94	ஔ	↔	blocked		Tamil homoglyph

Variant Set 2 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0B9C	ஜ	0D1C	ജ	↔	blocked		Cross-script homoglyph
0D1C	ജ	0D1C	ജ	≡	out-of-repertoire-var		Out-of-repertoire

Variant Set 3 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BAE	ம	0D25	ഥ	↔	blocked		Cross-script homoglyph
0D25	ഥ	0D25	ഥ	≡	out-of-repertoire-var		Out-of-repertoire

Variant Set 4 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BB5	வ	0D16	ഖ	↔	blocked		Cross-script homoglyph
0D16	ഖ	0D16	ഖ	≡	out-of-repertoire-var		Out-of-repertoire

Variant Set 5 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BB6 0BCD 0BB0 0BC0	ஶ்ரீ	0BB8 0BCD 0BB0 0BC0	ஸ்ரீ	↔	allocatable		Alternate for Tamil SHRII

Variant Set 6 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BBF	ி	0D3F	ി	↔	blocked		Cross-script homoglyph
0D3F	ി	0D3F	ി	≡	out-of-repertoire-var		Out-of-repertoire

Variant Set 7 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BC6	ெ	0D46	െ	↔	blocked		Cross-script homoglyph
0D46	െ	0D46	െ	≡	out-of-repertoire-var		Out-of-repertoire

Variant Set 8 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BC6 0BB3	ெள	0BCC	ௌ	↔	blocked		Tamil Homoglyph

Variant Set 9 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
0BC7	ே	0D47	േ	↔	blocked		Cross-script homoglyph
0D47	േ	0D47	േ	≡	out-of-repertoire-var		Out-of-repertoire

Classes, Rules and Actions

Character Classes

Number of named classes	2
Implicit (except script)	3
Implicit 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	Comment
C	Tag=Consonant	23	{0B95 0B99-0B9A 0B9C 0B9E-0B9F 0BA3-0BA4 0BA8-0BAA 0BAE-0BB9}	Any Tamil consonant
X	Tag=Visarga	1	{0B83}	The Tamil Visarga (aytham)
implicit	Tag=Halant	1	{0BCD}	The character tagged as Halant
implicit	Tag=Matra	11	{0BBE-0BC2 0BC6-0BC8 0BCA-0BCC}	Any character tagged as Matra
implicit	Tag=Vowel	12	{0B85-0B8A 0B8E-0B90 0B92-0B94}	Any character tagged as Vowel
implicit	Tag=sc:Mlym	6	{0D16 0D1C 0D25 0D3F 0D46-0D47}	Any character tagged as Malayalam
implicit	Tag=sc:Taml	48	{0B83 0B85-0B8A 0B8E-0B90 0B92-0B95 0B99-0B9A 0B9C 0B9E-0B9F 0BA3-0BA4 0BA8-0BAA 0BAE-0BB9 0BBE-0BC2 0BC6-0BC8 0BCA-0BCD}	Any character tagged as Tamil

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.

Whole Label Evaluation and Context Rules

Number of rules	4
Used to trigger actions	2
Used as context rule (C)	2
Anchored context rules	2

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	Comment
leading-combining-mark	`(start)[[\p{gc=Mn}] ∪ [\p{gc=Mc}]]`	✔			Default WLE rule matching labels with leading combining marks ⍟
follows-C	`([:C:])← ⚓︎`		✔	C	Section 7, WLE 1, 2: H and M must be preceded by C
preceded-by-X	`([:X:])← ⚓︎`		✔	C	Section 7, WLE 3 , X cannot be preceded by X
no-mix-sri-shri	`((\u0BB6\u0BCD\u0BB0\u0BC0.\u0BB8\u0BCD\u0BB0\u0BC0)\|(\u0BB8\u0BCD\u0BB0\u0BC0.\u0BB6\u0BCD\u0BB0\u0BC0))`	✔			Section 7: WLE 4: Two representations of ‘Shri’ cannot be mixed in the same label

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.
*, +, ?, {n,m} - count operators: * indicates 0 or more, + indicates one or more, and ? indicates up to one instance. {n,m} indicates at least n and at most m instances.
[: :] - 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	Comment
1	if label matches	leading-combining-mark	→	invalid	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 label matches	no-mix-sri-shri	→	invalid	do not mix two representations of ‘Shri’ in the same label
4	if at least one variant is in	{blocked}	→	blocked	any variant label containing blocked variants is blocked ⍟
5	if each variant is in	{allocatable}	→	allocatable	variant labels with all variants allocatable are allocatable ⍟
6	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.

Table of References

The following lists the references cited for specific code points, variants, classes, rules or actions in this LGR. For General references refer to the References section in the Description.

[0]	The Unicode Standard, Version 1.1 Any code point originally encoded in Unicode Version 1.1
[7]	The Unicode Standard, Version 4.1 Any code point originally encoded in Unicode Version 4.1
[101]	Omniglot, “Tamil”, https://www.omniglot.com/writing/tamil.htm (Accessed on 21 Nov. 2017)
[102]	Unicode 11.0.0, South and Central Asia-I, Page 488-493, R5 and R5a, https://www.unicode.org/versions/Unicode11.0.0/ch12.pdf (Accessed on 5 July. 2018)
[103]	Tamil Sign Visarga, https://charbase.com/0b83-unicode-tamil-sign-visarga (Accessed on 27 Nov. 2017)