Georgian (script)
Second-Level Reference Label Generation Rules, 25 October 2024 Current
Summary
| Version | 2 — Second Level Reference LGR |
|---|---|
| Date | |
| Tag |
und-Geor (Georgian)
|
| Unicode | 11.0.0 |
| Source file | lgr-second-level-georgian-script-25oct24-en.xml (18.4kb) |
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 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 to U+0039, 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
| 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+10D0 GEORGIAN LETTER AN 0 100 Georgian |
|
|
| ბ | U+10D1 GEORGIAN LETTER BAN 0 100 Georgian |
|
|
| გ | U+10D2 GEORGIAN LETTER GAN 0 100 Georgian |
|
|
| დ | U+10D3 GEORGIAN LETTER DON 0 100 Georgian |
|
|
| ე | U+10D4 GEORGIAN LETTER EN 0 100 Georgian |
|
|
| ვ | U+10D5 GEORGIAN LETTER VIN 0 100 Georgian |
|
|
| ზ | U+10D6 GEORGIAN LETTER ZEN 0 100 Georgian |
|
|
| თ | U+10D7 GEORGIAN LETTER TAN 0 100 Georgian |
|
|
| ი | U+10D8 GEORGIAN LETTER IN 0 100 Georgian |
|
|
| კ | U+10D9 GEORGIAN LETTER KAN 0 100 Georgian |
|
|
| ლ | U+10DA GEORGIAN LETTER LAS 0 100 Georgian |
|
|
| მ | U+10DB GEORGIAN LETTER MAN 0 100 Georgian |
|
|
| ნ | U+10DC GEORGIAN LETTER NAR 0 100 Georgian |
|
|
| ო | U+10DD GEORGIAN LETTER ON 0 100 Georgian |
|
|
| პ | U+10DE GEORGIAN LETTER PAR 0 100 Georgian |
|
|
| ჟ | U+10DF GEORGIAN LETTER ZHAR 0 100 Georgian |
|
|
| რ | U+10E0 GEORGIAN LETTER RAE 0 100 Georgian |
|
|
| ს | U+10E1 GEORGIAN LETTER SAN 0 100 Georgian |
|
|
| ტ | U+10E2 GEORGIAN LETTER TAR 0 100 Georgian |
|
|
| უ | U+10E3 GEORGIAN LETTER UN 0 100 Georgian |
|
|
| ფ | U+10E4 GEORGIAN LETTER PHAR 0 100 Georgian |
|
|
| ქ | U+10E5 GEORGIAN LETTER KHAR 0 100 Georgian |
|
|
| ღ | U+10E6 GEORGIAN LETTER GHAN 0 100 Georgian |
|
|
| ყ | U+10E7 GEORGIAN LETTER QAR 0 100 Georgian |
|
|
| შ | U+10E8 GEORGIAN LETTER SHIN 0 100 Georgian |
|
|
| ჩ | U+10E9 GEORGIAN LETTER CHIN 0 100 Georgian |
|
|
| ც | U+10EA GEORGIAN LETTER CAN 0 100 Georgian |
|
|
| ძ | U+10EB GEORGIAN LETTER JIL 0 100 Georgian |
|
|
| წ | U+10EC GEORGIAN LETTER CIL 0 100 Georgian |
|
|
| ჭ | U+10ED GEORGIAN LETTER CHAR 0 100 Georgian |
|
|
| ხ | U+10EE GEORGIAN LETTER XAN 0 100 Georgian |
|
|
| ჯ | U+10EF GEORGIAN LETTER JHAN 0 100 Georgian |
|
|
| ჰ | U+10F0 GEORGIAN LETTER HAE 0 100 Georgian |
|
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
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 |
References
| Ref | Source |
|---|---|
| 0 | The Unicode Standard, 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 |