Be Kind and Localize!
summary
Explains that internationalization must be done from the start and shows concrete steps: use DynamicBundle.getMessage for UI strings, prefer Unicode property files, and avoid changing the JVM default locale; marketplace data shows about 90% of third‑party translations are Simplified Chinese and only ~10% of plugins are internationalized; demonstrates tooling and workflows—Gradle keys, resource‑bundle lookup order, and automated Chinese screenshots to validate rendering and conversions.
AI-written summary · about
chapters (20)
- 0:00Introduction and context
- 2:55Common localization pitfalls
- 4:22IDE settings for localization
- 6:04When and why to localize
- 13:45Internationalization basics
- 14:21Formatting and lookup logic
- 18:46Localization for actions
- 19:46Inspections and resource paths
- 21:11Intentions and templates
- 22:31Live templates and settings
- 23:12Searchable options
- 24:00Help and documentation
- 24:37Marketplace presentation
- 25:09External website and support
- 25:33Known issues and resources
- 29:33Final remarks
- 29:46Audience Q&A: Part 1
- 30:58Audience Q&A: Part 2
- 35:30Audience Q&A: Part 3
- 37:53Closing and UI testing
related talks
01mRuth Cheesley shares key insights on communicating with an international team
46mTackling Language Barriers in Open Source Docs: A Case Study of openEuler's...
33mToward the broader globalization of Open Source
14mContributors wanted: encouraging diversity in your OSS project
14mIncreasing accessibility for Right To Left
22mRe-inventing the Rosetta Stone Together
45mLeveraging US specifications for the world
37mThe path from local to global Drupal developer