This document is mechanically formatted from the XML file for the LGR. It provides additional summary data and explanatory text.
The XML file remains the sole normative specification of the LGR.
- Description
- Repertoire
- Variant Sets
-
Classes, Rules and Actions
- Character Classes
- Whole label evaluation and context rules
- Actions
- Table of References
| Number of elements in repertoire |
3 |
| Number of ranges in repertoire |
0 |
| Number of code point sequences |
3 |
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 the 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, the link to the associated variant set, or if mapped to itself, the
variant type of that mapping is provided in the Variants column.
| # |
Code
Point |
Glyph |
Script |
Name |
Tags |
Required Context |
Variants |
Comment |
References |
| 1 |
U+1B12 U+1B13 U+002D U+1B44 |
ᬒ ᬓ - ᭄ [ᬒᬓ-᭄] |
Balinese |
BALINESE LETTER OKARA TEDUNG BALINESE LETTER KA HYPHEN-MINUS BALINESE ADEG ADEG |
|
|
|
|
|
| 2 |
U+1B19 U+1B3B U+002D U+1B40 |
ᬙ ᬻ - ᭀ [ᬙᬻ-ᭀ] |
Balinese |
BALINESE LETTER CA LACA BALINESE VOWEL SIGN RA REPA TEDUNG HYPHEN-MINUS BALINESE VOWEL SIGN TALING TEDUNG |
|
|
|
|
|
| 3 |
U+1B44 U+1B12 U+1B13 |
᭄ ᬒ ᬓ [᭄ᬒᬓ] |
Balinese |
BALINESE ADEG ADEG BALINESE LETTER OKARA TEDUNG BALINESE LETTER KA |
|
|
|
|
|
Legend
- Code Point
- A code point or code point sequence.
- Name
- Shows the character or sequence name from the Unicode Character Database.
- 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.
- References
- 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.
- Required Context
- Link to the rule defining the required context a code point or sequence must satisfy. If prefixed by "not:", identifies a context that must not occur.
- Variants
- A 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
- If the comment in this row consists only of the code point or sequence name it is suppressed in this view.
| Number of variant sets |
0 |
| Largest variant set |
0 |
| Ordinary Variants by Type |
|
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(s) column, otherwise the types for forward and reverse mappings, as well as comments and references are listed above one another.
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 “≡”.
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
- Source of the mapping pair.
- Target
- Destination of the mapping pair.
- Glyph
- The shape displayed for source or target depends on the fonts available to your browser.
- → - forward
- Indicates that variant Type, References and Comment apply to the mapping from source to target.
- ← - reverse
- Indicates that variant Type, References and Comment apply to the reverse mapping from target to source.
- ↔ - both
- Indicates that variant Type, References and Comment apply to both forward and reverse mapping.
- ≡ - reflexive
- Indicates that variant Type, References and Comment are for a reflexive mapping where source equals target.
- 🞩 - not in LGR
- Indicates that variant is not in LGR.
- Type
- The type of the variant mapping. There are some predefined variant types such as “allocatable” and “blocked”, while others are defined specifically for each LGR.
- References
- 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.
The following table lists all top-level classes with their definition and the regular expression defining their members.
| Name |
Definition |
Count |
Members |
References |
Comment |
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
- An anonymous class implicitly defined based on tag value.
- [: :] - named character set
- Reference to a named character set [:name:].
- (∩,∪,\,△) - set operators
- Sets may be combined by set operators (∩ = intersection, ∪ = union, \ = difference, △ = symmetric difference).
The following table lists all the top-level, or 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. (Any use of context rules for variants is not indicated).
| Name |
Regular Expression |
Used as
Trigger |
Used as
Context |
Anchor |
References |
Comment |
Legend
- Used as Trigger
- This rule triggers one of the actions listed below.
- Used as Context
- This rule defines a required context for a code point.
- Anchor
- This has a placeholder for the code point for which it is evaluated.
- Regular Expression
- A regular expression equivalent to the rule, shown in the standard notation with some extensions as noted:
- ⚓ - context anchor
- In a regex the ⚓ signifies a 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.
- (: :) - rule reference
- Non-recursive reference to a named rule.
- [: :] - character set either named, implicit or property
- Reference to a named character set [:name:], an implicit character set [:class tag=val:] or a given Unicode property [:class property:prop=val:]. A leading "^" before name or tag indicates the set complement.
- (|) - choice operator
- When there are various choices in a rule, choices are separated by the set operator (|) and each choice is represented by a set enclosed in parenthesis.
- (∩,∪,\,△) - set operators
- Sets may be combined by set operators (∩ = intersection, ∪ = union, \ = difference, △ = symmetric difference).
- Ø - empty set
- Indicated that the following set is empty because of the result of set operations or because non of its elements are part of the repertoire defined here.
- An empty set that is not optional means that a rule can never match.
- {m}, {m, n}, {m,} - count
- Indicates that the preceding element is evaluated from m to n times. Only {m} means the preceding element is evaluated exactly m times (equivalent to {m,m}), {m,} means the preceding element is evaluated at least m times.
- No count indicated the elements is evaluated once (equivalent to "{1}").
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 |
References |
Comment |
Legend
- {...} - variant type set
- In the "Rule/Variant Set" column the notation {...} means a set of variant types.