TSCII TSCII (Tamil Script Code for Information Interchange) Legacy & Platform-Specific
A Tamil-specific legacy encoding that predates and competed with ISCII's Tamil coverage — reflecting Tamil computing's early, somewhat independent development path.
What it is
TSCII (Tamil Script Code for Information Interchange) is a Tamil-specific legacy encoding that developed somewhat independently of, and in some contexts competed with, ISCII's own Tamil script coverage. Tamil had an active, relatively mature computing and publishing ecosystem prior to widespread ISCII/Unicode adoption, which led to TSCII seeing real independent use rather than the Tamil-script portion of ISCII being the only game in town, unlike some other Indic scripts where ISCII faced less direct competition.
Byte structure
| Byte range | Content |
|---|---|
| 0x00–0x7F | Identical to ASCII |
| 0xA0–0xFF | Tamil characters and glyph components, laid out differently from ISCII's Tamil-script byte assignments |
Notably, TSCII's byte layout is optimized somewhat differently from ISCII's shared multi-script logical structure — since TSCII only needs to cover Tamil rather than sharing byte space across ten different scripts the way ISCII does, its internal organization reflects different design priorities.
Why your text is garbled (symptom → cause)
| Symptom | Likely cause |
|---|---|
| Tamil text is completely unreadable | TSCII being read as ISCII, Latin-1, or another encoding, or vice versa — byte layouts genuinely differ |
| Text correct in older Tamil-specific software, garbled in general-purpose modern tooling | Legacy TSCII data needing explicit, TSCII-aware conversion rather than a generic ISCII or Latin-1 assumption |
| Tamil conjunct/ligature characters display incorrectly even after correct byte decoding | A rendering/shaping issue distinct from encoding — Tamil, like other Indic scripts, needs shaping-aware font rendering for correctly composed character clusters |
Compatibility & gotchas
- Distinct from ISCII's Tamil coverage — despite both encoding the same script, TSCII and ISCII use different byte layouts for Tamil, so text genuinely needs to be identified as one or the other before conversion, not assumed interchangeable.
- Reflects Tamil computing's relatively early and independent development — Tamil had significant pre-Unicode digital publishing activity, which is part of why a Tamil-specific encoding path developed somewhat separately rather than the broader multi-script ISCII being the sole legacy standard for Tamil text.
- Largely superseded by UTF-8 for new development — Unicode's Tamil block provides comprehensive coverage without requiring TSCII-vs-ISCII disambiguation.
Fixing it
- Command-line conversion: TSCII is less universally supported in generic tools like
iconvcompared to more common encodings — dedicated TSCII-to-Unicode conversion tools or libraries (several exist given Tamil's substantial legacy digital publishing history) are generally more reliable than attempting a generic single-byte conversion. - Confirming TSCII vs. ISCII: if a generic ISCII conversion produces garbled or nonsensical Tamil output, the source is likely genuinely TSCII rather than ISCII's Tamil-script mode, and needs TSCII-specific conversion instead.
Comparison
| Encoding | Key difference from TSCII |
|---|---|
| ISCII | Covers Tamil among ten shared-structure Indic scripts, using a different byte layout than TSCII's Tamil-specific approach |
| Unicode Tamil block | Full, unambiguous Tamil character coverage, the modern default that resolves the TSCII/ISCII disambiguation problem entirely |
FAQ
Why does Tamil have two different legacy encodings (TSCII and ISCII)?
Tamil had an active, relatively mature pre-Unicode computing and publishing ecosystem, which led to TSCII developing somewhat independently rather than ISCII's shared multi-script approach being the only widely adopted option — a pattern of parallel development not seen as strongly with some other Indic scripts.
Should I use TSCII for new Tamil-language development?
No — use UTF-8 with Unicode's Tamil block, which provides comprehensive, unambiguous coverage without needing to worry about which of two legacy encodings a given piece of Tamil text uses.
Fun fact
Tamil's relatively early and independent digital publishing history — driven in part by a large, geographically dispersed Tamil-speaking population with strong print and later digital media traditions — made it one of the more actively contested pre-Unicode Indic encoding spaces, with TSCII and ISCII's Tamil coverage representing two genuinely different technical communities' approaches to the same underlying script.