Code page 862
digital text encoding
Code page 862 (CCSID 862) (also known as CP 862, IBM 00862, OEM 862 (Hebrew),
MS-DOS Hebrew) is a code page used under DOS in Israel for Hebrew.
Like ISO 8859-8, it encodes only letters, not vowel-points or cantillation marks. As DOS had no inherent bidirectionality support, Hebrew text encoded using code page 862 was usually stored in visual order; nevertheless, a few DOS applications, notably a word processor named EinsteinWriter, stored Hebrew in logical order.
Code page 862 was replaced by Windows-1255 in Windows 3.x and 9x systems, and later by Unicode in Windows NT onwards. It is now obsolete.
Character set
The following table shows code page 862. It has the Hebrew letters in code positions 128–154 (80–9Ahex), but otherwise it is identical to code page 437. Each character is shown with its equivalent Unicode code point. Only the second half of the table (code points 128–255) is shown, the first half (code points 0–127) being the same as code page 437.
“Code page 862” enters the record as digital text encoding. Crown Archives preserves that source wording while asking what Code, page and digital can confirm, complicate or overturn.
Why this record matters
“Code page 862” is worth following because a concise public description often conceals a longer documentary argument. Here, Code, page and digital provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Dec 16, 2025. The linked authority identifier is Q1105760. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1255.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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 “Code page 862”, its source revision and the description used here.
- Expand the search: follow Code page 862 primary sources, Code page 862 archive and Code 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 “Code page 862”?
- 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 “Code page 862” 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.