Reference LGR for script: Georgian (Geor) | lgr-second-level-georgian-script-25oct24-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 | 2024-10-25
LGR Version | 2 (Second Level Reference LGR)
Language | und-Geor (Georgian Script)
Unicode Version | 11.0.0

# 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

## 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 Georgian Script

## Overview

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

For details and additional background on the Georgian script, see “Proposal for a Georgian Script Root Zone LGR” [Proposal-Georgian].

## Repertoire

The repertoire contains 33 code points for letters used by languages that are actively written in the Mkhedruli alphabet. The repertoire is a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Georgian]. (The proposal cited has been adopted for the Georgian 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 44 repertoire elements.

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. For code points in the repertoire, comments identify the language using the code point.

## 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 Myanmar in the same zone will create potential cross-script issues. For details, see Section 6, “Variants” in [Proposal-Georgian]. 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 Myanmar LGR(s) can be found in the following LGR: [Ref-LGR-Myanmar-Full-Variant-Script]

This version of the LGR defines no variants. For details, see Section 6, “Variants” in [Proposal-Georgian].

Additional variants When integrated to be used with another script LGR in the same zone, this LGR may inherit additional blocked cross-script variants by integration; they may not be listed here unless they reflect resulting in-script variants. Always use an applicable merged, or Common LGR created by integration for determining cross-script collisions of labels.

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

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

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

### Georgian-specific Rules

This LGR does not define rules specific to the Georgian 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 Georgian Mkhreduli was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Georgian script and information contained or referenced therein; see [RZ-LGR-Geor]. 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 Georgian script, that this LGR is based on, was developed by the Georgian Generation Panel. For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Georgian], as well as [RZ-LGR-Overview].

### Changes from Version Dated 15 December 2020

Unicode Version has been updated.

### Changes from Version Dated 25 October 2024

Adopted from the Second Level Reference LGR for the Georgian Mkhreduli [Ref-LGR-und-Geor] 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
[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-Georgian]
  Proposal for the Georgian Script Root Zone LGR, 14 November 2016,
  https://www.icann.org/en/system/files/files/proposal-georgian-lgr-24nov16-en.pdf
[Ref-LGR-und-Geor]
  ICANN, Second Level Reference Label Generation Rules for the Georgian Mkhreduli (und-Geor), 25 October 2024 (XML)
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-25oct24-en.xml
  non-normative HTML presentation:
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-25oct24-en.html
[Ref-LGR-Myanmar-Full-Variant-Script]
  ICANN, Second Level Reference Label Generation Rules for the Myanmar Script (und-Mymr), 25 October 2024 (XML)
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-25oct24-en.xml
  non-normative HTML presentation:
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-25oct24-en.html
[Unicode 11.0.0]
[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-Geor]
  ICANN, Root Zone Label Generation Rules for the Georgian Script (und-Geor), 26 May 2022 (XML)
  https://www.icann.org/sites/default/files/lgr/rz-lgr-5-georgian-script-26may22-en.xml
  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 Georgian Mkhreduli for the second level please see details in the Table of References below.

Reference [0] refers to the Unicode Standard version in which corresponding code points were initially encoded. Reference [100] corresponds to a source given in [Proposal-Georgian] for justifying the inclusion of for 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.

# Repertoire

## Repertoire Summary

Number of elements in repertoire | 44
Number of code points for each script |
Georgian | 33
Common | 11
Longest code point sequence | 1

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

See also the legend provided below the table.

Code Point | Glyph | Script | Name | Ref | Tags | Required Context | Comment
--- | --- | --- | --- | --- | --- | --- | ---
U+002D | - | Common | HYPHEN-MINUS | [0] |  | not: hyphen-minus-disallowed | ⍟
U+0030 | 0 | Common | DIGIT ZERO | [0] | Common-digit |  | ⍟
U+0031 | 1 | Common | DIGIT ONE | [0] | Common-digit |  | ⍟
U+0032 | 2 | Common | DIGIT TWO | [0] | Common-digit |  | ⍟
U+0033 | 3 | Common | DIGIT THREE | [0] | Common-digit |  | ⍟
U+0034 | 4 | Common | DIGIT FOUR | [0] | Common-digit |  | ⍟
U+0035 | 5 | Common | DIGIT FIVE | [0] | Common-digit |  | ⍟
U+0036 | 6 | Common | DIGIT SIX | [0] | Common-digit |  | ⍟
U+0037 | 7 | Common | DIGIT SEVEN | [0] | Common-digit |  | ⍟
U+0038 | 8 | Common | DIGIT EIGHT | [0] | Common-digit |  | ⍟
U+0039 | 9 | Common | DIGIT NINE | [0] | Common-digit |  | ⍟
U+10D0 | ა | Georgian | GEORGIAN LETTER AN | [0], [100] |  |  | Georgian
U+10D1 | ბ | Georgian | GEORGIAN LETTER BAN | [0], [100] |  |  | Georgian
U+10D2 | გ | Georgian | GEORGIAN LETTER GAN | [0], [100] |  |  | Georgian
U+10D3 | დ | Georgian | GEORGIAN LETTER DON | [0], [100] |  |  | Georgian
U+10D4 | ე | Georgian | GEORGIAN LETTER EN | [0], [100] |  |  | Georgian
U+10D5 | ვ | Georgian | GEORGIAN LETTER VIN | [0], [100] |  |  | Georgian
U+10D6 | ზ | Georgian | GEORGIAN LETTER ZEN | [0], [100] |  |  | Georgian
U+10D7 | თ | Georgian | GEORGIAN LETTER TAN | [0], [100] |  |  | Georgian
U+10D8 | ი | Georgian | GEORGIAN LETTER IN | [0], [100] |  |  | Georgian
U+10D9 | კ | Georgian | GEORGIAN LETTER KAN | [0], [100] |  |  | Georgian
U+10DA | ლ | Georgian | GEORGIAN LETTER LAS | [0], [100] |  |  | Georgian
U+10DB | მ | Georgian | GEORGIAN LETTER MAN | [0], [100] |  |  | Georgian
U+10DC | ნ | Georgian | GEORGIAN LETTER NAR | [0], [100] |  |  | Georgian
U+10DD | ო | Georgian | GEORGIAN LETTER ON | [0], [100] |  |  | Georgian
U+10DE | პ | Georgian | GEORGIAN LETTER PAR | [0], [100] |  |  | Georgian
U+10DF | ჟ | Georgian | GEORGIAN LETTER ZHAR | [0], [100] |  |  | Georgian
U+10E0 | რ | Georgian | GEORGIAN LETTER RAE | [0], [100] |  |  | Georgian
U+10E1 | ს | Georgian | GEORGIAN LETTER SAN | [0], [100] |  |  | Georgian
U+10E2 | ტ | Georgian | GEORGIAN LETTER TAR | [0], [100] |  |  | Georgian
U+10E3 | უ | Georgian | GEORGIAN LETTER UN | [0], [100] |  |  | Georgian
U+10E4 | ფ | Georgian | GEORGIAN LETTER PHAR | [0], [100] |  |  | Georgian
U+10E5 | ქ | Georgian | GEORGIAN LETTER KHAR | [0], [100] |  |  | Georgian
U+10E6 | ღ | Georgian | GEORGIAN LETTER GHAN | [0], [100] |  |  | Georgian
U+10E7 | ყ | Georgian | GEORGIAN LETTER QAR | [0], [100] |  |  | Georgian
U+10E8 | შ | Georgian | GEORGIAN LETTER SHIN | [0], [100] |  |  | Georgian
U+10E9 | ჩ | Georgian | GEORGIAN LETTER CHIN | [0], [100] |  |  | Georgian
U+10EA | ც | Georgian | GEORGIAN LETTER CAN | [0], [100] |  |  | Georgian
U+10EB | ძ | Georgian | GEORGIAN LETTER JIL | [0], [100] |  |  | Georgian
U+10EC | წ | Georgian | GEORGIAN LETTER CIL | [0], [100] |  |  | Georgian
U+10ED | ჭ | Georgian | GEORGIAN LETTER CHAR | [0], [100] |  |  | Georgian
U+10EE | ხ | Georgian | GEORGIAN LETTER XAN | [0], [100] |  |  | Georgian
U+10EF | ჯ | Georgian | GEORGIAN LETTER JHAN | [0], [100] |  |  | Georgian
U+10F0 | ჰ | Georgian | GEORGIAN LETTER HAE | [0], [100] |  |  | Georgian

Legend

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.
Name
  Shows the character or sequence name from the Unicode Character Database.
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.
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.
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.

# Variants

This LGR does not specify any variants.

# Classes, Rules and Actions

## Character Classes

Implicit (except script) | 1
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 | Ref | Comment
--- | --- | --- | --- | --- | ---
implicit | Tag=Common-digit | 10 | {0030-0039} |  | Any character tagged as Common-digit
implicit | Tag=sc:Geor | 33 | {10D0-10F0} |  | Any character tagged as Georgian
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.

## Whole label evaluation and context rules

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

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 - HYPHEN-MINUS ⍟

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 (...|...).
^ or $ - start or end
  ^ matches the start of the label; $ matches the end of the label.
. - any code point
  . matches any code point.
[\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 (&& = intersection, - = difference, ^ = symmetric difference) or concatenated (union).
∅= - empty set
  Indicates that the following set is empty because of the result of set operations, or because none of its elements is part of the repertoire defined here. A rule with a non-optional empty set never matches.
⍟ - 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, blocked, out-of-repertoire-var. This is not necessarily an error.

# 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
[100] | Omniglot Georgian Mkhedruli, https://www.omniglot.com/writing/georgian.htm#mkhedruli
[150] | RFC 5891, Internationalized Domain Names in Applications (IDNA): Protocol https://tools.ietf.org/html/rfc5891