Reference LGR for language: German (de) | lgr-second-level-german-language-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 | 3 (Second Level Reference LGR)
Language | de (German Language)
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 German

## Overview

This document specifies a set of Label Generation Rules (LGR) for the German language using a language-specific repertoire for the second level domain or domains identified above. The format of this file follows [RFC 7940]. This LGR is adapted from the “Reference LGR for the Second Level for the German Language” [Ref-LGR-de-Latn], for details, see Change History below.

Standalone LGR: This LGR is designed to be used in a zone that does not cater to IDNs other than those valid under this LGR. This LGR lacks features that would allow its use in the context of another LGR in the same zone, and it may contain other features incompatible with such use.

## Repertoire

Almost all references converge on 30 Latin code points.

DENIC eG has published an extensive IDN character list used for the German (.de) ccTLD [700] and NIC.AT has deposited a more restrained Latin script IDN list for the Austrian (.at) ccTLD [701] that notably excludes “ß”. These lists include many code points needed for spelling personal or business names from neighboring countries. Most of them have been excluded here, since adding them would be more appropriate for a script-based LGR (or subset thereof).

### Excluded code points

Letters documented in some references, but not included:

- U+00E1 á LATIN SMALL LETTER A WITH ACUTE

- U+00E3 ã LATIN SMALL LETTER A WITH TILDE

- U+00E5 å LATIN SMALL LETTER A WITH RING ABOVE

- U+00E6 æ LATIN SMALL LETTER AE

- U+00EB ë LATIN SMALL LETTER E WITH DIAERESIS

- U+00EC ì LATIN SMALL LETTER I WITH GRAVE

- U+00ED í LATIN SMALL LETTER I WITH ACUTE

- U+00EE î LATIN SMALL LETTER I WITH CIRCUMFLEX

- U+00EF ï LATIN SMALL LETTER I WITH DIAERESIS

- U+00F0 ð LATIN SMALL LETTER ETH

- U+00F1 ñ LATIN SMALL LETTER N WITH TILDE

- U+00F2 ò LATIN SMALL LETTER O WITH GRAVE

- U+00F3 ó LATIN SMALL LETTER O WITH ACUTE

- U+00F8 ø LATIN SMALL LETTER O WITH STROKE

- U+00FA ú LATIN SMALL LETTER U WITH ACUTE

- U+00FD ý LATIN SMALL LETTER Y WITH ACUTE

- U+00FE þ LATIN SMALL LETTER THORN

- U+00FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS

- U+0101 ā LATIN SMALL LETTER A WITH MACRON

- U+0103 ă LATIN SMALL LETTER A WITH BREVE

- U+0105 ą LATIN SMALL LETTER A WITH OGONEK

- U+0107 ć LATIN SMALL LETTER C WITH ACUTE

- U+0109 ĉ LATIN SMALL LETTER C WITH CIRCUMFLEX

- U+010B ċ LATIN SMALL LETTER C WITH DOT ABOVE

- U+010D č LATIN SMALL LETTER C WITH CARON

- U+010F ď LATIN SMALL LETTER D WITH CARON

- U+0111 đ LATIN SMALL LETTER D WITH STROKE

- U+0113 ē LATIN SMALL LETTER E WITH MACRON

- U+0115 ĕ LATIN SMALL LETTER E WITH BREVE

- U+0117 ė LATIN SMALL LETTER E WITH DOT ABOVE

- U+0119 ę LATIN SMALL LETTER E WITH OGONEK

- U+011D ĝ LATIN SMALL LETTER G WITH CIRCUMFLEX

- U+011F ğ LATIN SMALL LETTER G WITH BREVE

- U+0121 ġ LATIN SMALL LETTER G WITH DOT ABOVE

- U+0123 ģ LATIN SMALL LETTER G WITH CEDILLA

- U+0129 ĩ LATIN SMALL LETTER I WITH TILDE

- U+012B ī LATIN SMALL LETTER I WITH MACRON

- U+012D ĭ LATIN SMALL LETTER I WITH BREVE

- U+012F į LATIN SMALL LETTER I WITH OGONEK

- U+0131 ı LATIN SMALL LETTER DOTLESS I

- U+0135 ĵ LATIN SMALL LETTER J WITH CIRCUMFLEX

- U+0137 ķ LATIN SMALL LETTER K WITH CEDILLA

- U+0138 ĸ LATIN SMALL LETTER KRA

- U+013A ĺ LATIN SMALL LETTER L WITH ACUTE

- U+013C ļ LATIN SMALL LETTER L WITH CEDILLA

- U+013E ľ LATIN SMALL LETTER L WITH CARON

- U+0142 ł LATIN SMALL LETTER L WITH STROKE

- U+0144 ń LATIN SMALL LETTER N WITH ACUTE

- U+0146 ņ LATIN SMALL LETTER N WITH CEDILLA

- U+0148 ň LATIN SMALL LETTER N WITH CARON

- U+014B ŋ LATIN SMALL LETTER ENG

- U+014D ō LATIN SMALL LETTER O WITH MACRON

- U+014F ŏ LATIN SMALL LETTER O WITH BREVE

- U+0151 ő LATIN SMALL LETTER O WITH DOUBLE ACUTE

- U+0153 œ LATIN SMALL LIGATURE OE

- U+0155 ŕ LATIN SMALL LETTER R WITH ACUTE

- U+0157 ŗ LATIN SMALL LETTER R WITH CEDILLA

- U+0159 ř LATIN SMALL LETTER R WITH CARON

- U+015B ś LATIN SMALL LETTER S WITH ACUTE

- U+015D ŝ LATIN SMALL LETTER S WITH CIRCUMFLEX

- U+015F ş LATIN SMALL LETTER S WITH CEDILLA

- U+0161 š LATIN SMALL LETTER S WITH CARON

- U+0163 ţ LATIN SMALL LETTER S WITH CEDILLA

- U+0165 ť LATIN SMALL LETTER T WITH CARON

- U+0167 ŧ LATIN SMALL LETTER T WITH STROKE

- U+0169 ũ LATIN SMALL LETTER U WITH TILDE

- U+016B ū LATIN SMALL LETTER U WITH MACRON

- U+016D ŭ LATIN SMALL LETTER U WITH BREVE

- U+016F ů LATIN SMALL LETTER U WITH RING

- U+0171 ű LATIN SMALL LETTER U WITH DOUBLE ACUTE

- U+0173 ų LATIN SMALL LETTER U WITH OGONEK

- U+0175 ŵ LATIN SMALL LETTER W WITH CIRCUMFLEX

- U+0177 ŷ LATIN SMALL LETTER Y WITH CIRCUMFLEX

- U+017A ź LATIN SMALL Z WITH ACUTE

- U+017C ż LATIN SMALL LETTER Z WITH DOT ABOVE

- U+017E ž LATIN SMALL Z WITH CARON

A few sources, among them [700], provide in their repertoire for code points from all the European languages, Danish, Polish, Turkish, Romanian, Czech and so on. These have been excluded.

### Extended code points

A number of letters not considered essential to writing the core vocabulary of the language are nevertheless in common use. Where they have not been added to the core repertoire, they are flagged as “extended-cp” in the table of code points. A context rule is provided that by default will prohibit labels with such extended code points. To support extended single code points or code point sequences, delete the context “extended-cp” from their repertoire definition.

The code points specified as extended are mostly those used for loanwords from French, which are accessible on German keyboards and commonly retained in spelling.

## Variants

U+00DF ß LATIN SMALL LETTER SHARP S is used in Germany and Austria, but not in Switzerland, where the spelling “ss” is used instead. In addition, the letter is normally uppercased as “SS”. This might suggest it as a candidate for a variant mapping. While both the Latin Variant Issues Report [VIP] as well as DENIC, the operator of the .de ccTLD orginally decided that no variant mapping was warranted, several registries show “ß” and “ss” as simple variants in their IDN tables. The Root Zone LGR for the Latin script [RZ-LGR-Latn] has come to a somewhat nuanced conclusion. The variant scheme developed there attempts to address IDNA 2003 compatibility issues by making “ss” an allocatable fallback variant of U+00DF ß. An original label may contain U+00DF ß in any position, and if it does, the version with “ss” substituted for all instances of U+00DF ß would be “allocatable”, but not the other way around. By default, this “fallback” variant scheme is enabled in this LGR. (See “Optionally-Enabled Variants” below).

No other variants are applicable when using the LGR in a standalone fashion.

Variants Limited to Standalone Use This LGR is not intended for use with LGRs for other languages or scripts in the same zone. The LGR does not define any “blocked” variants with code points in other languages or script that would prevent malicious registration of duplicate labels perceived as the same by users. As a result of transitivity, the scheme of internal variants defined here would have to be imposed on other LGRs that contain copies or variants of the affected code points.

If it is desired to support multiple languages in the same zone, the preferred method would be to support the corresponding script LGRs, which cater to the use of multiple languages, and are designed with the possibility of concurrent use in mind.

### Optionally-enabled Variants

Certain variants in this LGR are defined as optionally enabled. They are using the context rule “enabled”. This context rule matches any label (it always succeeds). Any variant marked with when=“enabled” (in the XML file) is in force, while marking it with not-when=“enabled” causes the variant definition to be ignored in processing. This allows these variants to be disabled, for example, to better match legacy practice for a given zone.

Care must be taken to enable or disable variants so that all variant mappings to and from the same code point are either enabled or disabled at the same time, ensuring that all enabled variant mappings remain symmetric and transitive.

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

## Character Classes

This LGR does not define named character classes.

## Rules

### Common Rules

The LGR includes the rules and actions to implement the following restrictions, some of which are mandated by the IDNA protocol. They are marked with ⍟ and included here by default. A special context rule enables optional variants by default.

- 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].
- Enabled — matches any label. Used as variant context rule; any variant with `when="enabled"` in the xml will be active, while any with `not-when="enabled"` will be inactive.

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

Because this LGR defines allocatable fallback variants the following default actions are applicable.

- blocked — a variant label containing a blocked variant will receive a disposition of “blocked”.
- r-original — a label containing one or more of this reflexive variant type and no others represents an original label and receives a disposition of “valid”.
- fallback — a label containing one or more of these variant types and no others represents a label that contains only fallback variants and receives a disposition of “allocatable”.
- fallback plus other — any label remaining containing both this variant type and any others receives a disposition of “blocked”.

These actions resolve as “allocatable” any label where all variants are of type “fallback”, and as “valid” any label where all variants are of type “r-original”. Labels with a mix of variant types are resolved as “blocked”.

To account for original code points in a permuted variant, reflexive variant mappings with an “r-” prefix are used. (See [RFC 7940]). In particular, the mapping type “r-original” is given to any code point that has a fallback mapping, but that appears in its non-fallback form in the original label, and thus “maps to itself”.

Default actions that are triggered by the LGR-specific variant types described above limit the “allocatable” variant labels to those variants resulting from the substitution of U+00DF ß by “ss”, while disallowing mixed use of variants with or without subsitution, except as in the original applied-for label. The use of such variants is "optionally_enabled_variants">optionally enabled in this LGR.

Note that the mapping types for variants are not symmetric: they depend on which code point is considered the source or the target in a given mapping. As specified in [RFC 7940], when mapping types are evaluated code points in a label that are unchanged use the type of their “reflexive” mapping. Per [RFC 7940] the actions are always applied one after the other, and the evaluation stops at the first action that assigns a disposition to a given label.

## 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 German Language was developed by Michel Suignard and Asmus Freytag, including input by Michael Everson, Nicholas Ostler, and Wil Tan, and based on multiple open public consultations.

### Changes from Version Dated 10 October 2016

Language tag has been updated.

### Changes from Version Dated 18 May 2021

Unicode Version has been updated.

Variant for U+00DF ß has been defined to match [RZ-LGR-Latn]. This fallback variant is enabled here by default, but is marked as “enabled” to allow registries to deactivate it if required.

### Changes from Version Dated 25 October 2024

Adopted from the Second Level Reference LGR for the German Language [Ref-LGR-de-Latn] without normative changes.

## References

General references for the language:

- Rat für deutsche Rechtschreibung, “Regeln und Wörterverzeichnis”, München und Mannheim, February 2006 (with corrections from 2010)
  https://www.rechtschreibrat.com

- Duden. 1996. Rechtschreibung der deutschen Sprache. 21. Auflage. Mannheim: Dudenverlag. ISBN 3-411-04011-4

- Wahrig, Gerhard. 1974. Deutsches Wörterbuch. Gütersloh: Bertelsmann Lexikon-Verlag. ISBN 3-570-06588-X

- Wikipedia: “German orthography”,
  https://en.wikipedia.org/wiki/German_alphabet

- Omniglot: German (deutsch)
  https://www.omniglot.com/writing/german.htm

In addition, the following references were consulted:

[RFC 7940]
  Davies, K. and A. Freytag, “Representing Label Generation Rulesets Using XML”, RFC 7940, August 2016,
  https://www.rfc-editor.org/info/rfc7940.
[Ref-LGR-de-Latn]
  ICANN, Second Level Reference Label Generation Rules for the German Language (de-Latn), 25 October 2024 (XML)
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-german-language-25oct24-en.xml
  non-normative HTML presentation:
  https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-german-language-25oct24-en.html
[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-Latn]
  ICANN, Root Zone Label Generation Rules for the Latin Script (und-Latn), 26 May 2022 (XML)
  https://www.icann.org/sites/default/files/lgr/rz-lgr-5-latin-script-26may22-en.xml
[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-5]
  Integration Panel, “Root Zone Label Generation Rules (RZ-LGR-5)”, 26 May 2022 (XML),
  https://www.icann.org/sites/default/files/lgr/rz-lgr-5-common-26may22-en.xml
  non-normative HTML presentation:
  https://www.icann.org/sites/default/files/lgr/rz-lgr-5-common-26may22-en.html
[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/
[VIP]
  ICANN VIP Study Group for the Latin script, “Considerations in the use of the Latin script in variant internationalized top-level domains”,
  https://archive.icann.org/en/topics/new-gtlds/latin-vip-issues-report-07oct11-en.pdf

In the listing of the repertoire by code point, references starting from [0] refer to the version of the Unicode Standard in which the corresponding code point was initially encoded. Other references (starting from [100]) document usage of 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. For more details, see the Table of References below.

# Repertoire

## Repertoire Summary

Number of elements in repertoire | 42
Number of extended elements | 9
Total entries in table | 51
Number of code points for each script |
Latin | 39
Common | 11
Number of code points | 50
Number of sequences | 1
Longest code point sequence | 2

## 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 or optional code points 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+002D | - | Common | HYPHEN-MINUS | [0], [100], [301], [401], [601], [701] |  | not: hyphen-minus-disallowed | ✔ |  |
U+0030 | 0 | Common | DIGIT ZERO | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0031 | 1 | Common | DIGIT ONE | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0032 | 2 | Common | DIGIT TWO | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0033 | 3 | Common | DIGIT THREE | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0034 | 4 | Common | DIGIT FOUR | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0035 | 5 | Common | DIGIT FIVE | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0036 | 6 | Common | DIGIT SIX | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0037 | 7 | Common | DIGIT SEVEN | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0038 | 8 | Common | DIGIT EIGHT | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0039 | 9 | Common | DIGIT NINE | [0], [100], [301], [401], [601], [701] | Common-digit |  | ✔ |  | ⍟
U+0061 | a | Latin | LATIN SMALL LETTER A | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0062 | b | Latin | LATIN SMALL LETTER B | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0063 | c | Latin | LATIN SMALL LETTER C | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0064 | d | Latin | LATIN SMALL LETTER D | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0065 | e | Latin | LATIN SMALL LETTER E | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0066 | f | Latin | LATIN SMALL LETTER F | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0067 | g | Latin | LATIN SMALL LETTER G | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0068 | h | Latin | LATIN SMALL LETTER H | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0069 | i | Latin | LATIN SMALL LETTER I | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006A | j | Latin | LATIN SMALL LETTER J | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006B | k | Latin | LATIN SMALL LETTER K | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006C | l | Latin | LATIN SMALL LETTER L | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006D | m | Latin | LATIN SMALL LETTER M | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006E | n | Latin | LATIN SMALL LETTER N | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+006F | o | Latin | LATIN SMALL LETTER O | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0070 | p | Latin | LATIN SMALL LETTER P | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0071 | q | Latin | LATIN SMALL LETTER Q | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0072 | r | Latin | LATIN SMALL LETTER R | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0073 | s | Latin | LATIN SMALL LETTER S | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0073 U+0073 | ss | {Latin} | LATIN SMALL LETTER S + LATIN SMALL LETTER S |  |  | enabled | ✔ | set 1 | Sequence added for variant mapping
U+0074 | t | Latin | LATIN SMALL LETTER T | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0075 | u | Latin | LATIN SMALL LETTER U | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0076 | v | Latin | LATIN SMALL LETTER V | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0077 | w | Latin | LATIN SMALL LETTER W | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0078 | x | Latin | LATIN SMALL LETTER X | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+0079 | y | Latin | LATIN SMALL LETTER Y | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+007A | z | Latin | LATIN SMALL LETTER Z | [0], [100], [301], [401], [601], [701] |  |  | ✔ |  |
U+00DF | ß | Latin | LATIN SMALL LETTER SHARP S | [0], [100], [200], [301], [401], [603], [604], [700] |  |  | ✔ | set 1 |
U+00E0 | à | Latin | LATIN SMALL LETTER A WITH GRAVE | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00E2 | â | Latin | LATIN SMALL LETTER A WITH CIRCUMFLEX | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00E4 | ä | Latin | LATIN SMALL LETTER A WITH DIAERESIS | [0], [100], [200], [301], [401], [603], [604], [700], [701] |  |  | ✔ |  |
U+00E7 | ç | Latin | LATIN SMALL LETTER C WITH CEDILLA | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00E8 | è | Latin | LATIN SMALL LETTER E WITH GRAVE | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00E9 | é | Latin | LATIN SMALL LETTER E WITH ACUTE | [0], [301], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00EA | ê | Latin | LATIN SMALL LETTER E WITH CIRCUMFLEX | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00F4 | ô | Latin | LATIN SMALL LETTER O WITH CIRCUMFLEX | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00F6 | ö | Latin | LATIN SMALL LETTER O WITH DIAERESIS | [0], [100], [200], [301], [401], [603], [604], [700], [701] |  |  | ✔ |  |
U+00F9 | ù | Latin | LATIN SMALL LETTER U WITH GRAVE | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00FB | û | Latin | LATIN SMALL LETTER U WITH CIRCUMFLEX | [0], [402], [605], [700], [701] |  | extended-cp | ◯ |  |
U+00FC | ü | Latin | LATIN SMALL LETTER U WITH DIAERESIS | [0], [100], [200], [301], [401], [603], [604], [700], [701] |  |  | ✔ |  |

Legend

Throughout this LGR, 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.
◯ - extended repertoire
  An open circle indicates a code point is part of an optional extended repertoire, which is normally disabled but could be supported by removing the relevant context restriction.

# Variants

## Variant Set Summary

Number of variant sets | 1
Largest variant set | 2
Ordinary Variants by Type |
blocked 1
fallback 1
Reflexive Variants by Type |
r-original 1

## 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 variant sets for each context are disjoint, but code points that have variants with multiple contexts are members of more than one set.

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.
Required Context
  Link to the rule defining a required context the source must satisfy for the variant mapping to be defined. If prefixed by “not:”, identifies a context that must not occur.
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 | Required Context | Ref | Comment
--- | --- | --- | --- | --- | --- | --- | --- | ---
0073 0073 | ss | 00DF | ß | → | blocked | enabled |  | IDNA2003 Compatibility
← | fallback | enabled |  | IDNA2003 Compatibility
00DF | ß | 00DF | ß | ≡ | r-original | enabled |  | Eszett

# 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:Latn | 39 | {0061-007A 00DF-00E0 00E2 00E4 00E7-00EA 00F4 00F6 00F9 00FB-00FC} |  | Any character tagged as Latin
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 | 4
Used to trigger actions | 1
Used as context rule (C) | 3
Used as context rule (V) | 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 ⍟
extended-cp | `(start)(end)` |  |  | C |  | context to gate off code points from the extended range, matches no label ⍟
enabled | `(start).*(end)` |  |  | C, V |  | use as when-context to enable: matches any 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 (...|...).
^ or $ - start or end
  ^ matches the start of the label; $ 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.
[\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.
(^.*$) - any label
  The regex (^.*$) matches any label. Used as a context rule, it always matches, thus not affecting the validity of a label containing the code point. By convention, it is used to explicitly mark a preferred code point for review purposes.
⍟ - 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 |  | labels with leading combining marks are invalid ⍟
2 | if at least one variant is in | {blocked} | → | blocked |  | any variant label containing blocked variants is blocked ⍟
3 | if each variant is in | {fallback} | → | allocatable |  | any label with all variants of type fallback is allocatable ⍟
4 | if at least one variant is in | {fallback} | → | blocked |  | any variant label with a mix of variant forms is blocked ⍟
5 | if each variant is in | {r-original} | → | valid |  | any remaining label containing only original code points is valid ⍟
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 Code points cited were originally encoded in Unicode Version 1.1
[100] | Internetstiftelsen i Sverige (IIS), “IDN Reference table for German language” https://github.com/dotse/IDN-ref-tables/blob/master/language-tables/german-lang-ref-table.txt accessed on 2016-10-16
[150] | RFC 5891, Internationalized Domain Names in Applications (IDNA): Protocol https://tools.ietf.org/html/rfc5891
[200] | ISO/IEC 6937 Third Ed. 2001-12-17- Information technology — Coded graphic character set for text communication — Latin alphabet: Table D.1 (p 35) Use of Latin alphabetic characters. This table lists only the characters outside the set a-z
[301] | Everson, Michael. The Alphabets of Europe: “German” https://www.evertype.com/alphabets/german.pdf Code points cited form the standard set
[302] | Everson, Michael. The Alphabets of Europe: “German” https://www.evertype.com/alphabets/german.pdf Code points cited are from an extended set
[304] | Everson, Michael. The Alphabets of Europe: “German” https://www.evertype.com/alphabets/german.pdf Code points cited are rare or archaic
[401] | The Unicode Consortium, Common Locale Data Repository (CLDR) Version 28 (2015-09-16) - Locale Data Summary for German [de] https://www.unicode.org/cldr/charts/28/summary/de.html Code points cited are from the set of Main Letters
[402] | The Unicode Consortium, Common Locale Data Repository (CLDR) Version 28 (2015-09-16) - Locale Data Summary for German [de] https://www.unicode.org/cldr/charts/28/summary/de.html Code points cited are from the Auxiliary set
[603] | ISO/IEC 646:1991 — Information technology — ISO 7-bit coded character set for information interchange Code points cited are supported in a national edition of ISO-646.
[601] | Wikipedia: “Latin Alphabets” https://en.wikipedia.org/wiki/Latin_alphabets - accessed 2015-10-31 According to this reference, the alphabet is listed as using the full basic set A-Z
[604] | Wikipedia: “Latin Alphabets” https://en.wikipedia.org/wiki/Latin_alphabets. accessed 2015-10-31 The table only lists code points beyond A-Z
[605] | Wikipedia: “German orthography” https://en.wikipedia.org/wiki/German_orthography-Alphabet Code points cited are listed as in extended use
[700] | DENIC eG, “IDN Character List”, https://www.denic.de/en/know-how/idn-domains/idn-character-list/ The table only lists code points beyond ASCII
[701] | NIC.AT, Latin script table for .at TLD, https://www.iana.org/domains/idn-tables/tables/at_latn_1.0.txt