Latin-1 Export Compatibility Warning
Report cells containing characters outside ISO-8859-1’s U+0000–U+00FF repertoire; Windows-1252 substitutions such as the euro sign are not accepted as Latin-1.
Description
Latin-1 represents a 256-character repertoire.
Latin-1 represents a 256-character repertoire. Text outside that repertoire needs another encoding or an explicit replacement policy; a familiar symbol such as the euro sign is not part of ISO-8859-1.1
Report cells containing characters outside ISO-8859-1’s U+0000–U+00FF repertoire; Windows-1252 substitutions such as the euro sign are not accepted as Latin-1.
When to use Latin-1 Export Compatibility Warning
Use this tool to report cells containing characters outside ISO-8859-1’s U+0000–U+00FF repertoire; Windows-1252 substitutions such as the euro sign are not accepted as Latin-1.
Choose the original CSV text, decoded cell strings, byte values or counts requested by this tool. Use the stated delimiter, encoding, indexing and number/date convention.
How to use Latin-1 Export Compatibility Warning and understand its results
- Choose the original CSV text, decoded cell strings, byte values or counts requested by this tool. Use the stated delimiter, encoding, indexing and number/date convention.
- Enter values using the field table and calculation rules, then run the tool.
- Read compatible, incompatibleIndices. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| values | Values | list of string; maximum length: 10000; minimum entries: 0; maximum entries: 10000 | Required |
Provide decoded cell strings. The tool flags each zero-based cell index containing any UTF-16 unit above 255 and reports compatible true only when no cells are flagged. Empty strings and an empty list are compatible. C0/C1 controls pass the repertoire check, even if they are unsuitable for a particular export.
compatible = every UTF-16 code unit ≤ U+00FF Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| compatible | Compatible | boolean |
| incompatibleIndices | Incompatible indices | list of integer; minimum: 0 |
{
"input": {
"values": [
"café",
"€",
"😀"
]
},
"output": {
"compatible": false,
"incompatibleIndices": [
1,
2
]
}
} Limitations and assumptions
It does not encode or write a file, check printability, distinguish Windows-1252 from ISO-8859-1, or propose substitutions. Compatibility concerns only the supplied strings; export headers and other text must be checked separately.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Cell-string lists also have a combined text budget of 100,000 UTF-16 units per list. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Latin-1 Mojibake Sequence Detector: Flag a narrow mojibake heuristic: Latin-1 characters corresponding to UTF-8 C2/C3 lead bytes followed by an 80–BF continuation byte; this is evidence rather than encoding identification. For a complementary task, use Emoji/Non-ASCII Headers Flagger: Find headers containing any non-ASCII UTF-16 unit, including accented characters and emoji, without claiming to identify emoji or reject Unicode names.
References
-
Latin-1 Export Compatibility Warning — tool.io
Similar or alternative tools
- Latin-1 Mojibake Sequence Detector
Flag a narrow mojibake heuristic: Latin-1 characters corresponding to UTF-8 C2/C3 lead bytes followed by an 80–BF continuation byte; this is evidence rather than encoding identification.
- Emoji/Non-ASCII Headers Flagger
Find headers containing any non-ASCII UTF-16 unit, including accented characters and emoji, without claiming to identify emoji or reject Unicode names.