Editorial method & sources
Character facts come from official Unicode data. Explanations are written for this reference; the data is generated from a pinned source rather than copied from another character website.
Inclusion and classification
We parse code points, official names, general categories, combining classes, and decompositions from UnicodeData.txt. We recursively resolve canonical decompositions, retaining uppercase and lowercase Latin letters only when the result is an ASCII A to Z or a to z letter followed entirely by marks. Compatibility decompositions are excluded.
Ligatures, stroked letters, and other Latin forms that fail this rule remain separate from the primary dataset. Selected related forms are also copyable on each letter page, grouped as related letterforms, ligatures or digraphs, and phonetic letters. Their names and codes are read from the same pinned Unicode source. Related forms are an editorial selection, not a claim to catalog every Latin character. The Fahrenheit sign is a symbol, not an accented Latin letter, and is excluded. Names describe Unicode identities; we do not infer language usage from names.
Authoritative sources
Validation and limitations
The generator records source URLs, retrieval dates, and SHA-256 checksums. Automated checks compare regenerated data, reject duplicates, and test character formatting and site routes. CP1252 shortcuts are mapping-verified, not tested across every Windows setup. Browser fonts and keyboard support vary.
The text tool uses the browser’s normalization implementation. Removing marks is not full transliteration. See the tool’s limitations and the typing guide.
Corrections
Compare a questionable character with the pinned source and include its code point when documenting the discrepancy. Our contact page explains current feedback availability.
Sources, versions and limits
- Encoded properties
- Properties use Unicode 17.0.0. Normalization follows UAX #15; grapheme boundaries follow UAX #29. Script associations describe encoded properties, not language use.
- Language evidence
- CLDR 48.2and the IANA registry dated 2026-08-08. Main and auxiliary exemplars are distinct. CLDR exemplars are not complete orthographies.
- Review and limitations
- The dataset is derived from the sources above. Editorial guides cite additional scoped authorities. No native or specialist orthography approval is implied. Release scope date: 14 September 2026. Historic or specialist usage needs separate evidence. Registry-only records have unknown orthography in this release.
- Reproduction and corrections
- Downloads and licences · Coverage and held routes · Suggest a source-backed correction