Let's start at the beginning - bits to character encoding in R
summary
Explains how characters map to numbers then bits with the math 2^8 = 256 so 8 bits = 1 byte and ASCII originally used 7 bits while Latin‑1 uses the full 8; shows UTF‑8 uses 1–4 bytes per code point and can cover 1 million+ Unicode code points. Shows R specifics: strings can be Latin‑1, UTF‑8, or raw, R 4.2.0 makes UTF‑8 the native encoding on modern Windows, and functions like encoding(), sys.getlocale(), and the i convert routine plus stringr/stringi handle conversions.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:54ASCII, Latin1, and Unicode
- 2:22ASCII, Latin1, and UTF-8
- 2:48Character String Encoding in R
- 4:16Character encoding, Tidyverse style
related talks
28mMaking Acquaintances with Exotic Encodings
44mA 🐍's guide to Unicode
33mPython's Transition to Multilingual Programming
35mText Is Not Text: The History of Strings in Python
25mWhy len 4 and other weird things you should know about strings in Python
59mEmbracing multi-lingual data science
29mYour Name Is Invalid!
32mInterfacing R and Python