{
  "slug": "iso-8859-1",
  "term": "ISO-8859-1 (Latin-1)",
  "aliases": [
    "Latin-1",
    "Latin1",
    "ISO/IEC 8859-1"
  ],
  "definition": "ISO-8859-1, also called Latin-1, is an eight-bit single-byte coded character set for Latin-alphabet text with a graphic repertoire distinct from Windows-1252.",
  "note": "Identity: ISO-8859-1 and windows-1252 are separate registered character sets. The Latin-1 graphic repertoire does not contain the euro sign. The published Unicode mapping also includes control characters; its complete byte-to-code-point mapping should not be confused with the scope of the original graphic-character standard. [iana] [latin-map]\n\nByte contract: The Latin-1 mapping maps a byte's value directly to the corresponding Unicode code point, so 80 hexadecimal becomes U+0080 and E9 becomes U+00E9. Node Buffer.toString(\"latin1\") follows this byte-preserving mapping. It does not validate that a control is acceptable in a filename. [latin-map] [node-buffer]\n\nLabel resolution: WHATWG TextDecoder maps latin1 and iso-8859-1 to windows-1252; byte 80 then becomes U+20AC even with fatal: true. This API alias does not make the two registered encodings identical. Record the API, resolved encoding and error policy. [whatwg-labels] [whatwg-index]\n\nRecovery: Keeping every byte decodable does not recover the intended text. Retain the original bytes and their interpretation metadata when migrating a legacy inventory, and check destination-name collisions separately. [hesela-filenames]",
  "status": "shipping",
  "advantages": [],
  "limitations": [
    "A successful decode does not identify the original encoding or establish destination filename validity."
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-20",
  "related": [
    "windows-1252",
    "character-encoding",
    "ascii",
    "utf-8",
    "filename-collision"
  ],
  "citations": [
    {
      "id": "iana",
      "title": "IANA character sets: distinct ISO-8859-1 and windows-1252 registrations",
      "url": "https://www.iana.org/assignments/character-sets",
      "accessed": "2026-11-20"
    },
    {
      "id": "latin-map",
      "title": "Unicode: ISO/IEC 8859-1:1998 mapping, table 2.0, including control characters",
      "url": "https://www.unicode.org/Public/MAPPINGS/ISO8859/8859-1.TXT",
      "accessed": "2026-11-20"
    },
    {
      "id": "whatwg-labels",
      "title": "WHATWG Encoding Standard: names and labels",
      "url": "https://encoding.spec.whatwg.org/#names-and-labels",
      "accessed": "2026-11-20"
    },
    {
      "id": "whatwg-index",
      "title": "WHATWG windows-1252 index, dated 2024-09-18",
      "url": "https://encoding.spec.whatwg.org/index-windows-1252.txt",
      "accessed": "2026-11-20"
    },
    {
      "id": "node-buffer",
      "title": "Node.js 24: Buffer character encodings and WHATWG compatibility warning",
      "url": "https://nodejs.org/docs/latest-v24.x/api/buffer.html#buffers-and-character-encodings",
      "accessed": "2026-11-20"
    },
    {
      "id": "hesela-filenames",
      "title": "Hesela: Latin-1 and Windows-1252 decoder contracts in filename recovery",
      "url": "https://hesela.com/analyses/filename-identity-backup-restores/#legacy-single-byte",
      "accessed": "2026-11-20"
    }
  ],
  "provenance": [
    "Source-reviewed identity with exhaustive constructed one-byte codec observations: https://hesela.dev/research/legacy-single-byte/README.md. No filesystem experiment or encoding detector."
  ]
}
