Single-byte character set
Character encoding using one byte per character
A single-byte character set (SBCS) is a character encoding that uses exactly one byte for each graphic character. A SBCS can accommodate a maximum of 256 symbols, and is useful for scripts that do not have many symbols or accented letters, such as the Latin, Greek, and Cyrillic scripts used mainly for European languages. Examples of SBCS encodings include ISO/IEC 646, the various ISO 8859 encodings, and the various Microsoft/IBM code pages.
Single-byte character sets are contrasted against double-byte and triple-byte character sets as well as multi-byte character sets. Multi-byte character sets are used to accommodate languages with scripts that have large numbers of characters and symbols, predominantly Asian languages such as Chinese, Japanese, and Korean (sometimes referred to as "CJK"). In these character encodings, SBCS are traditionally associated with half-width characters, so-called because such single-byte characters would traditionally occupy half the width of a double-byte character on a computer terminal screen which used a duospaced font.
Modern use
Though single-byte character sets have largely been supplanted by Unicode encodings in modern systems, they have found a niche in code golfing, where the smaller size of characters allows participants to gain an edge if they use SBCS with programming languages which facilitate their use for increased code compactness, such as Vyxal and GolfScript.
“Single-byte character set” enters the record as character encoding using one byte per character. Crown Archives preserves that source wording while asking what Single-byte, character and Character can confirm, complicate or overturn.
Why this record matters
“Single-byte character set” is worth following because a concise public description often conceals a longer documentary argument. Here, Single-byte, character and Character provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Nov 8, 2025. The linked authority identifier is Q2289247. None of the 0 selected statements returned an explicit reference.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Single-byte character set”, its source revision and the description used here.
- Expand the search: follow Single-byte character set primary sources, Single-byte character set archive and Single-byte research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Single-byte character set”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Single-byte character set” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.