| Reference LGR for language: Spanish (es) | lgr-second-level-spanish-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 | es (Spanish 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 Spanish
Overview
This document specifies a set of Label Generation Rules (LGR) for the Spanish 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 Spanish Language” [Ref-LGR-es-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
Most references converge on 33 Latin code points.
There is no IDN table published in the IANA Repository of IDN Practices by a Spanish-language ccTLD, but several registries’ policies were investigated [700][701][703] for information on IDN repertoire policies.
Excluded Code Points
Letters documented in some references but not included:
U+00E4 ä LATIN SMALL LETTER A WITH DIAERESIS
U+00E5 å LATIN SMALL LETTER A WITH RING ABOVE
U+00E6 æ LATIN SMALL LETTER AE
U+00EB ë LATIN SMALL LETTER E WITH DIAERESIS
U+00EE î LATIN SMALL LETTER I WITH CIRCUMFLEX
U+00F6 ö LATIN SMALL LETTER O WITH DIAERESIS
U+00F9 ù LATIN SMALL LETTER U WITH GRAVE
U+00FB û LATIN SMALL LETTER U WITH CIRCUMFLEX
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+0113 ē LATIN SMALL LETTER E WITH MACRON
U+0115 ĕ LATIN SMALL LETTER E WITH BREVE
U+012B ī LATIN SMALL LETTER I WITH MACRON
U+012D ĭ LATIN SMALL LETTER I WITH BREVE
U+014D ō LATIN SMALL LETTER O WITH MACRON
U+014F ŏ LATIN SMALL LETTER O WITH BREVE
U+0153 œ LATIN SMALL LIGATURE OE
U+016B ū LATIN SMALL LETTER U WITH MACRON
U+016D ŭ LATIN SMALL LETTER U WITH BREVE
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.
Spanish being used in a large number of countries complicates the question of determining an extended set. The extended code points defined here include both the extensions for Catalan, for Spanish users in Spain (see [700]), and for Portuguese, for Spanish users in, for example, Argentina (see [701]). Spanish users in other countries may need extensions for words or names from additional minority languages.
The extensions for Catalan include U+00B7 · MIDDLE DOT for use in the sequence “l·l” for the Ela Geminada in Catalan. The LGR adds a context rule to satisfy the CONTEXTO constraint on U+00B7 · MIDDLE DOT from RFC 5892 [122]. Note that the precomposed U+0140 ŀ LATIN LETTER SMALL L WITH MIDDLE DOT is DISALLOWED under IDNA 2008 [IDNAREG].
Variants
The LGR defines certain allocatable fallback variants as described in Section 4.5.5 “Allocatable Fallback Variants” in [Level-2-Overview]. A fallback variant is a variant label that uses substitute code points for code points or sequences not available (or not allowed) in some contexts, that would otherwise be required for a linguistically accurate rendering of some label.
When “fallback” variants are defined, two labels may be allocated: a single label with the spelling preferred by the applicant, plus a single fallback variant for that label. The fallback exclusively uses the fallback characters for any characters for which fallbacks are defined, while the “preferred” label may use any otherwise valid mix of code points. If the fallback variant is the one applied for, no other variant label is allocatable.
An allocatable fallback variant exists for the following pair where the second element is the fallback:
U+00B7 · MIDDLE DOT and U+002D - HYPHEN-MINUS — the use of the hyphen as fallback for the middle dot in the Catalan Ela Geminada follows registry practice, see [704]. The variant is limited to an Ela Geminada context.
In-script Variant Mapping Types
In each of the fallback variant pairs defined above, the mapping type from the first element to the second is of type “fallback”, while the variant type for the other direction is “blocked”. In addition, the first element of each pair uses the reflexive mapping “r-original”. (By convention, the prefix “r-” marks a type used in a reflexive variant mapping, that is, it represents an instance of the original code point at that location in a variant label, see Section 5.3.4 in [RFC 7940].)
Variant Disposition: Except for limited exceptions for the fallback variants defined above, variants defined here result in a variant label disposition of “blocked”.
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.
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
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].
Language-specific Rules
The following context rule applies to U+00B7 · MIDDLE DOT and its variants. It ensures that the middle dot is part of an Ela Geminada sequence and variants between it and HYPHEN-MINUS are only defined in that context.
- surrounded-by-L — code points are invalid and variants undefined when not surrounded by “l”
The following WLE rule invalidates labels in which two Ela Geminada sequences overlap.
- dot-L-dot — labels sharing a single “l” with two different middle dots are invalid
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”.
Language-specific Actions
An action has been defined to invalidate labels containing the sequence U+00B7 U+006C U+00B7 ·l· which could otherwise result in two Ela Geminada sequences overlapping.
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 Spanish 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.
Changes from Version Dated 24 January 2024
The treatment of U+00B7 · MIDDLE DOT has been changed to match that of the Latin script LGR. This adds a fallback variant between "l·l" and "l-l".
Changes from Version Dated 25 October 2024
Adopted from the Second Level Reference LGR for the Spanish Language [Ref-LGR-es-Latn] without normative changes.
References
General references for the language:
Maria Moliner, Diccionario del uso del español, Rba; 3rd edition (September 30, 2007), ISBN 978-8424928865
Alvar Ezquerra, Manuel, ed. 1997. Diccionario avanzado lengua española. Barcelona: Vox. ISBN 84-7153-947-0
Castillo, Carlos, & Otto F. Bond. 1987. The University of Chicago Spanish dictionary. Chicago&London: University of Chicago Press. ISBN 0-226-10400-8
Wikipedia: “Spanish orthography”,
https://en.wikipedia.org/wiki/Spanish_alphabetOmniglot: “Spanish (español/castellano)”
https://www.omniglot.com/writing/spanish.htm
Other references cited in this document:
- [IDNAREG]
- IANA Registry: “IDNA Parameters”. For Unicode 11.0 available at:
https://www.iana.org/assignments/idna-tables-11.0.0/idna-tables-11.0.0.xml
accessed on 2015-11-24 - [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 - [Ref-LGR-es-Latn]
- ICANN, Second Level Reference Label Generation Rules for the Spanish Language (es-Latn), 25 October 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-spanish-language-25oct24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-spanish-language-25oct24-en.html - [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 - [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/
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 | 45 | ||||
|---|---|---|---|---|---|
| Number of extended elements | 11 | ||||
| Total entries in table | 56 | ||||
| Number of code points for each script |
|
||||
| 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.
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] | not: hyphen-minus-disallowed | ✔ | set 1 | ||
| U+0030 | 0 | Common | DIGIT ZERO | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0031 | 1 | Common | DIGIT ONE | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0032 | 2 | Common | DIGIT TWO | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0033 | 3 | Common | DIGIT THREE | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0034 | 4 | Common | DIGIT FOUR | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0035 | 5 | Common | DIGIT FIVE | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0036 | 6 | Common | DIGIT SIX | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0037 | 7 | Common | DIGIT SEVEN | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0038 | 8 | Common | DIGIT EIGHT | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0039 | 9 | Common | DIGIT NINE | [0], [100], [301], [401], [601] | Common-digit | ✔ | ⍟ | ||
| U+0061 | a | Latin | LATIN SMALL LETTER A | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0062 | b | Latin | LATIN SMALL LETTER B | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0063 | c | Latin | LATIN SMALL LETTER C | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0064 | d | Latin | LATIN SMALL LETTER D | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0065 | e | Latin | LATIN SMALL LETTER E | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0066 | f | Latin | LATIN SMALL LETTER F | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0067 | g | Latin | LATIN SMALL LETTER G | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0068 | h | Latin | LATIN SMALL LETTER H | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0069 | i | Latin | LATIN SMALL LETTER I | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006A | j | Latin | LATIN SMALL LETTER J | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006B | k | Latin | LATIN SMALL LETTER K | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006C | l | Latin | LATIN SMALL LETTER L | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006D | m | Latin | LATIN SMALL LETTER M | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006E | n | Latin | LATIN SMALL LETTER N | [0], [100], [301], [401], [601] | ✔ | ||||
| U+006F | o | Latin | LATIN SMALL LETTER O | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0070 | p | Latin | LATIN SMALL LETTER P | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0071 | q | Latin | LATIN SMALL LETTER Q | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0072 | r | Latin | LATIN SMALL LETTER R | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0073 | s | Latin | LATIN SMALL LETTER S | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0074 | t | Latin | LATIN SMALL LETTER T | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0075 | u | Latin | LATIN SMALL LETTER U | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0076 | v | Latin | LATIN SMALL LETTER V | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0077 | w | Latin | LATIN SMALL LETTER W | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0078 | x | Latin | LATIN SMALL LETTER X | [0], [100], [301], [401], [601] | ✔ | ||||
| U+0079 | y | Latin | LATIN SMALL LETTER Y | [0], [100], [301], [401], [601] | ✔ | ||||
| U+007A | z | Latin | LATIN SMALL LETTER Z | [0], [100], [301], [401], [601] | ✔ | ||||
| U+00B7 | · | Common | MIDDLE DOT | [0], [100], [122], [702], [703] | surrounded-by-L | ✔ | set 1 | Catalan L·L - CONTEXTO for MIDDLE DOT in RFC 5892 | |
| U+00E0 | à | Latin | LATIN SMALL LETTER A WITH GRAVE | [0], [402], [700], [701] | extended-cp | ◯ | |||
| U+00E1 | á | Latin | LATIN SMALL LETTER A WITH ACUTE | [0], [100], [200], [301], [401], [604], [700], [701] | ✔ | ||||
| U+00E2 | â | Latin | LATIN SMALL LETTER A WITH CIRCUMFLEX | [0], [402], [701] | extended-cp | ◯ | |||
| U+00E3 | ã | Latin | LATIN SMALL LETTER A WITH TILDE | [0], [402], [701] | extended-cp | ◯ | |||
| U+00E7 | ç | Latin | LATIN SMALL LETTER C WITH CEDILLA | [0], [402], [603], [700], [701] | extended-cp | ◯ | |||
| U+00E8 | è | Latin | LATIN SMALL LETTER E WITH GRAVE | [0], [402], [700] | extended-cp | ◯ | |||
| U+00E9 | é | Latin | LATIN SMALL LETTER E WITH ACUTE | [0], [100], [301], [401], [604], [700], [701] | ✔ | ||||
| U+00EA | ê | Latin | LATIN SMALL LETTER E WITH CIRCUMFLEX | [0], [402], [701] | extended-cp | ◯ | |||
| U+00EC | ì | Latin | LATIN SMALL LETTER I WITH GRAVE | [0], [200], [402] | extended-cp | ◯ | |||
| U+00ED | í | Latin | LATIN SMALL LETTER I WITH ACUTE | [0], [100], [200], [301], [401], [604], [700], [701] | ✔ | ||||
| U+00EF | ï | Latin | LATIN SMALL LETTER I WITH DIAERESIS | [0], [402], [604], [700], [701] | extended-cp | ◯ | |||
| U+00F1 | ñ | Latin | LATIN SMALL LETTER N WITH TILDE | [0], [100], [200], [301], [401], [603], [604], [700], [701] | ✔ | ||||
| U+00F2 | ò | Latin | LATIN SMALL LETTER O WITH GRAVE | [0], [402], [700] | extended-cp | ◯ | |||
| U+00F3 | ó | Latin | LATIN SMALL LETTER O WITH ACUTE | [0], [100], [200], [301], [401], [604], [700], [701] | ✔ | ||||
| U+00F4 | ô | Latin | LATIN SMALL LETTER O WITH CIRCUMFLEX | [0], [402], [701] | extended-cp | ◯ | |||
| U+00F5 | õ | Latin | LATIN SMALL LETTER O WITH TILDE | [0], [402], [701] | extended-cp | ◯ | |||
| U+00FA | ú | Latin | LATIN SMALL LETTER U WITH ACUTE | [0], [100], [200], [301], [401], [604], [700], [701] | ✔ | ||||
| U+00FC | ü | Latin | LATIN SMALL LETTER U WITH DIAERESIS | [0], [100], [200], [301], [401], [604], [700], [701] | ✔ |
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.
- 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 |
|
||
| Reflexive Variants by Type |
|
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 | |
|---|---|---|---|---|---|---|---|---|
| 002D | - | 00B7 | · | → | blocked | surrounded-by-L | [704] | Middle dot in Ela Geminada |
| ← | fallback | surrounded-by-L | Fallback | |||||
| 00B7 | · | 00B7 | · | ≡ | r-original | surrounded-by-L | Middle Dot in the original label |
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 | 44 | {0061-007A 00E0-00E3 00E7-00EA 00EC-00ED 00EF 00F1-00F5 00FA 00FC} | Any character tagged as Latin | |
| implicit | Tag=sc:Zyyy | 12 | {002D 0030-0039 00B7} | 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 | 5 |
|---|---|
| Used to trigger actions | 2 |
| Used as context rule (C) | 3 |
| Used as context rule (V) | 1 |
| 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 |
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 ⍟ | |||
| surrounded-by-L | (\u006C)← ⚓︎ →(\u006C) |
✔ | C, V | code point both follows and precedes L, required context for Ela Geminada ⍟ | ||
| dot-L-dot | \u00B7\u006C\u00B7 |
✔ | labels with one L sharing two middle dots are invalid ⍟ |
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 | by default, labels with leading combining marks are invalid | |
| 2 | if label matches | dot-L-dot | → | invalid | labels with one L sharing two middle dots are 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 | {fallback} | → | allocatable | any label with all variants of type fallback is allocatable ⍟ | |
| 5 | if at least one variant is in | {fallback} | → | blocked | any variant label with a mix of variant forms is blocked ⍟ | |
| 6 | if each variant is in | {r-original} | → | valid | any remaining label containing only original code points is valid ⍟ | |
| 7 | if any label (catch-all) | → | valid | catch all |
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 Spanish language”
https://github.com/dotse/IDN-ref-tables/blob/master/language-tables/spanish-lang-ref-table.txt accessed on 2016-10-16 |
| [122] | RFC 5982, Faltstrom, P., Ed., “The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)”, https://tools.ietf.org/html/rfc5892 |
| [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: “Spanish” https://www.evertype.com/alphabets/spanish.pdf Code points cited form the standard set |
| [302] | Everson, Michael. The Alphabets of Europe: “Spanish” https://www.evertype.com/alphabets/spanish.pdf Code points cited are from an extended set |
| [304] | Everson, Michael. The Alphabets of Europe: “Spanish” https://www.evertype.com/alphabets/spanish.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 Spanish [es] https://www.unicode.org/cldr/charts/28/summary/es.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 Spanish [es] https://www.unicode.org/cldr/charts/28/summary/es.html Code points cited are from the Auxiliary set |
| [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 |
| [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. |
| [604] | Wikipedia: “Spanish orthography” https://en.wikipedia.org/wiki/Spanish_orthography |
| [700] | Dominios “.es”, Syntax regulations, in “Other applicable Regulations"
https://www.dominios.es/dominios/en/todo-lo-que-necesitas-saber/normativa/otras-normas-aplicables#Sintaxis |
| [701] | Dirección Nacional del Registro de Dominios de Internet, Normativa vigente,
https://nic.ar/normativa-vigente.xhtml Registry for the ".ar" domain. Explicitly mentions that the repertoire includes both the Spanish and Portuguese alphabets |
| [702] | Wikipedia, Catalan Orthography,
https://en.wikipedia.org/wiki/Catalan_orthography, accessed on 28 November 2022 |
| [703] | Fundacio PuntCAT registry (.CAT), IDN table for CAT_ca Version 1.0, 12 February 2006,
https://www.iana.org/domains/idn-tables/tables/cat_ca_1.0.html |
| [704] | Fundacio PuntCAT registry (.CAT), Rules of the .cat domain,
https://domini.cat/en/rules-of-the-cat-domain/ |