Superscript oneDouble box T-junction pointing left
ASCII 185 is ¹ on Windows and ╣ in old DOS.
¹ (Superscript One) is byte 185 in Windows-1252, Unicode U+00B9. It marks footnotes in plain text (as noted¹) and shows up in science, as in ¹H NMR spectra or exponents like 10¹. Units with negative exponents are where it runs short. Per second is s⁻¹, and the superscript minus ⁻ (U+207B) isn't in Windows-1252, so text limited to that code page ends up as s-¹ with an ordinary hyphen, or s^-1. In UTF-8 there's no reason for the workaround: write s⁻¹ directly. Its own UTF-8 bytes are C2 B9, which misread as ¹. The HTML entity is ¹.
╣ (Double Vertical and Left) is byte 185 in code page 437, the original IBM PC character set, and maps to Unicode U+2563. It's the tee on the right side of an all-double frame, where a double divider ═ (205) meets the double side ║ (186); its left-side partner is ╠ at 204. Code page 850 kept this piece. It replaced every mixed single-double piece with letters and symbols but left the all-single and all-double sets in place, so a frame drawn only from pieces like ═ ║ ╔ ╗ ╠ ╣ displays correctly under either code page. In UTF-8 it's E2 95 A3, and the HTML entity is ╣.
#include <stdio.h>int main(void) {/* On Windows (code page 1252) byte 185 is ¹.Modern terminals expect UTF-8, so print the code point, not the byte. */printf("\u00B9\n"); /* UTF-8: C2 B9 */unsigned char b = 185; /* the raw Windows-1252 byte */printf("%d 0x%02X\n", b, b); /* 185 0xB9 */return 0;}
#include <stdio.h>int main(void) {/* Byte 185 is ╣ only on a console using code page 437(chcp 437 on Windows, or DOSBox). On a UTF-8 terminal thelone byte 0xB9 is invalid and prints as garbage, often �. */putchar(185);/* char is signed on x86, so a plain char holding 0xB9 is -71.Use unsigned char when you compare or index by byte value. */char c = (char)185;unsigned char u = 185;printf("\n%d %d\n", c, u); /* -71 185 *//* Portable: print the Unicode character as UTF-8 instead. */printf("\u2563\n"); /* E2 95 A3 */return 0;}
After it. Chicago style puts note numbers after any punctuation, as at the end of this sentence.¹ The one exception is a dash, which the number goes before. Keep it attached to the preceding character with no space, so a line break can't strand it at the start of the next line.
Write `[^1]` where the note belongs and `[^1]: The note text.` on its own line anywhere below. GitHub and GitLab both render the marker as a small superscript link and gather the notes at the bottom of the page. Typing ¹ by hand gives you the look but none of the links back and forth.
Because they aren't in that range. They sit in Latin-1 at U+00B9, U+00B2 and U+00B3, while ⁰ and ⁴ to ⁹ start at U+2070, and [⁰-⁹] even catches the letter ⁱ at U+2071. List them explicitly: `[⁰¹²³⁴-⁹]`. To turn them into plain digits in Python, use `str.maketrans('⁰¹²³⁴⁵⁶⁷⁸⁹', '0123456789')`.
The screen was saved in code page 437 and is being read as Windows-1252, which turns the divider pieces ╠ ═ ╣ into Ì, Í and ¹. The rest of the frame goes the same way, with ║ as º and the corners as É, », È and ¼. Decode it as 437 when you load it, for example in Go with `charmap.CodePage437.NewDecoder().String(s)`.
The screen was saved in code page 437 and is being read as Windows-1252, which turns the divider pieces ╠ ═ ╣ into Ì, Í and ¹. The rest of the frame goes the same way, with ║ as º and the corners as É, », È and ¼. Decode it as 437 when you load it, for example in Go with `charmap.CodePage437.NewDecoder().String(s)`.