I18n…what- Internationalization- Why and How
summary
WordPress is 53% non‑American‑English (American English ~47%) and Japanese is 5.9%, so make plugins/themes translatable by adding Text Domain and Domain Path headers with the text domain matching the repo slug, call load_plugin_textdomain or load_theme_textdomain, and use translation helpers like __ and _e, _x, _n, printf/sprintf and number_format_i18n. Avoid variables or concatenation for translatable strings; use numbered printf placeholders. For JS use the WP i18n package and wp_set_script_translations; generate POT/PO/MO/JSON via WP‑CLI for manual workflows.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:38What is it
- 1:32Why Care
- 2:52How
- 6:25String Translation
- 9:41Comment Translation
- 10:32Escape
- 12:20Common Mistakes
- 13:59Printf
- 16:22Numbers
- 17:42JavaScript
- 19:34Localization
- 20:40Easy Way
- 21:05Hard Way
- 22:32WordPress Translation Day
- 23:56Resources and References
- 27:58Translate WordPressorg
- 29:06Translation Plugin
- 30:37Gutenberg
