Enable truly global use of your code – avoid the typical i18n pitfalls
summary
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
