ASCII 133
EllipsisLowercase a with grave accent
ASCII 133 is … on Windows and à in old DOS.
… (Ellipsis) is byte 133 in Windows-1252, Unicode U+2026. It's a single character that looks like three periods, and Word's AutoCorrect swaps it in when you type three dots. That swap is where the trouble starts: a search for ... won't find it, and a JavaScript spread like ...args pasted from a document becomes …args and stops parsing. On the web it breaks as …, which is its UTF-8 bytes E2 80 A6 read as Windows-1252. There's a stranger failure too. In ISO-8859-1 the same byte 0x85 is NEL, a control character Unicode counts as a line break, so a Windows-1252 file decoded as Latin-1 turns every … into U+0085, and Python's str.splitlines() then splits the line right there. The HTML entity is ….
à (Small A with Grave) is byte 133 in code page 437, the original IBM PC character set, and maps to Unicode U+00E0. Windows-1252 has the ellipsis … at 133, so DOS text read as Windows-1252 turns voilà into voil…, which looks like a sentence trailing off. Code page 850 kept à at 133 too. Code page 437 has no capital À at all, and code page 850 added one at 183.
Technical Details
Technical Details
Code Example
</>
#include <stdio.h>int main(void) {/* On Windows (code page 1252) byte 133 is ….Modern terminals expect UTF-8, so print the code point, not the byte. */printf("\u2026\n"); /* UTF-8: E2 80 A6 */unsigned char b = 133; /* the raw Windows-1252 byte */printf("%d 0x%02X\n", b, b); /* 133 0x85 */return 0;}
Code Example
</>
#include <stdio.h>int main(void) {/* Byte 133 is à only on a console using code page 437(chcp 437 on Windows, or DOSBox). On a UTF-8 terminal thelone byte 0x85 is invalid and prints as garbage, often �. */putchar(133);/* char is signed on x86, so a plain char holding 0x85 is -123.Use unsigned char when you compare or index by byte value. */char c = (char)133;unsigned char u = 133;printf("\n%d %d\n", c, u); /* -123 133 *//* Portable: print the Unicode character as UTF-8 instead. */printf("\u00E0\n"); /* C3 A0 */return 0;}
How to Type It
- Windows
- Hold Alt and type 0133 on the numeric keypad, with Num Lock on. The leading zero picks the Windows code page. No numeric keypad? In Word, type 2026 and press Alt+X.
- Mac
- Press Option+;.
- Linux
- In GNOME, or any desktop running IBus, press Ctrl+Shift+U, type 2026, then Space. With a Compose key set up, press Compose, period, period.
- Phone
- iPhone: open the 123 keyboard, long-press the period key and pick …. Android (Gboard): tap the character at the top of this page to copy it.
How to Type It
- Windows
- Hold Alt and type 133 on the numeric keypad, with no leading zero. Windows reads it as a DOS code and inserts à.
à is also ASCII 224 on Windows, which has the full guide.
Frequently Asked Questions
Give the element a set width (a block, not an inline span) and add `overflow: hidden; white-space: nowrap; text-overflow: ellipsis;`. The browser then draws … where the text stops fitting. That only covers a single line. For two or three lines, use -webkit-line-clamp together with display: -webkit-box and -webkit-box-orient: vertical, which current browsers support despite the prefix.
The program printed … as UTF-8, E2 80 A6, to a console still reading code page 850, which draws those bytes as Ô, Ç and ª. On a US console with code page 437 you get ΓǪ instead. In PowerShell, run `[Console]::OutputEncoding = [Text.Encoding]::UTF8` before starting the program so the console reads UTF-8.
Because … isn't in the GSM 7-bit alphabet that plain SMS uses. A single character outside it switches the whole message to UCS-2, which cuts the limit from 160 characters to 70. Replace it with three periods before sending and the message goes back to the 160 limit, as long as nothing else in it needs UCS-2.
Two letters broke at once. In code page 437 é is byte 130 and à is byte 133, and Windows-1252 reads those bytes as ‚ and …. French text full of ‚ and … is a reliable sign the whole file is DOS-encoded, not just damaged in spots. In Python, opening it with encoding='cp437' reads it correctly.
Frequently Asked Questions
Two letters broke at once. In code page 437 é is byte 130 and à is byte 133, and Windows-1252 reads those bytes as ‚ and …. French text full of ‚ and … is a reliable sign the whole file is DOS-encoded, not just damaged in spots. In Python, opening it with encoding='cp437' reads it correctly.