~/talk

Enable truly global use of your code – avoid the typical i18n pitfalls

Talkat WordCamp Europe 2023 · 2023-06-08..06-10· [wordpress]
links:none on file
slides:none on file

Volunteer translators from Polyglots report recurring i18n bugs and show concrete fixes: always use _n with the numeric variable inside the translatable string and format with printf (include n in string), never build sentences by concatenating tiny strings (don't concatenate short strings), avoid huge single strings that break review, and escape percent signs inside printf (the Japanese Enigma is a percent-sign vs printf clash). They demo using repo issues, GitHub pull requests, Slack, and caution against publishing unchecked machine translations.

AI-written summary · about

  1. 0:00Introduction and Japanese Enigma
  2. 5:27Top five i18n pitfalls
  3. 15:26Making code reachable for translators
  4. 20:14Plurals and underscore n misuse
  5. 26:41Solving the Japanese Enigma
  6. 28:27Summary and doubling reach
  7. 30:43Q&A session begins
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.