~/talk

Unicode Best Practices

Talkat Open Source Bridge 2013 · 2013-06-18..06-21· [web-platform]
github:patch
slides:none on file

Recommendations: use use utf-8 for IO everywhere—decode incoming UTF‑8 to character strings, work on characters, then encode UTF‑8 on output; keep source files UTF‑8 and use literal UTF‑8 in HTML; prefer hex numeric entities if escaping. Regex notes: \d matches digits in all scripts so use [0-9] for ASCII digits; use \p{...} properties and script values for precise matching; normalize and case‑fold for comparisons; sort with the Unicode Collation Algorithm. Tests include above 0x7F, 0xFF, 0xFFF (surrogates), emoji, grapheme clusters. Repo: unicode cookbook. case folding

AI-written summary · about

  1. 0:00Unicode best practices intro
  2. 1:15Why follow best practices
  3. 3:24UTF-8 for source code I/O
  4. 7:16Readable regex with UTF-8
  5. 10:09Ligatures in regex handling
  6. 12:37Unicode regex character classes
  7. 15:07When to use regex properties
  8. 20:10Grapheme clusters vs code points
  9. 24:09Unicode character properties
  10. 30:55Case folding & normalization
  11. 34:10Normalize input/output
  12. 35:32Fix locale sorting bugs
  13. 36:40Unicode Collation Algorithm
  14. 38:25Test Unicode awareness
  15. 40:12Test high code points
  16. 41:16UTF-8 in Perl tests
  17. 42:40Handle invalid UTF-8
  18. 45:51Q&A on Unicode edge cases
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.