The document discusses the process of internationalizing WordPress, outlining how to install language files and edit configuration settings. It highlights the need for improved language support in themes and plugins, and addresses technical challenges associated with localization. The document emphasizes the importance of translation and aims for enhanced multilingual capabilities in future WordPress releases.

1. WordPress in
not English
Yoav Farhi

2. yoavfarhi.com
@yoavf
Yoav Farhi
Iñtërnâtiônàlizætiønër
Automattic

3. 2.7 2.8 2.9 3.0 3.1
3.2 3.3 3.4 3.5 3.6
3.7 3.8 3.9

4. Today
• What's broken
• How we're going to fix it
• Questions

5. Auf deutsch, bitte!
cc by-nc
https://flic.kr/p/c1APuC

6. Install

9. 1. Get and upload language files (?)
2. Edit wp-config.php
3. Some things are still in English
Change language

11. Themes & Plugins

26. Update

29. Let's fix it

30. Let’s get to work
cc-by galato901
http://yoav.fr/towork

31. Install & Core
Upgrades

33. • No more locales builds*
• Language can easily be changed
(during or after install)
• Updates to language packs can happen
between WordPress releases too
Core Language Packs

34. • Builds with custom PHP/CSS
• Translation of Readmes, licences etc
Technical Challenges

35. Themes & Plugins

36. • Localized directories
• Plugins/Themes in the directories will
show supported languages (available
via search too)
• Also in your WordPress Install
Themes and Plugins

37. • Detecting what is translated to what
• Get more plugins and themes translated
• Set translations free from developers (and
developers free from translations)
Challenges

38. • For themes and plugins in the repository.
• Independent from plugin/theme authors
• All translations at
http://translate.wordpress.org
Think: translation-memory, fuzzy matching...
Language Packs

39. cc by-nc-sa thewmatt
http://flic.kr/p/3QMH8y

40. • Internationalization goals for 4.0
http://wp.me/p2AvED-2ID
• http://make.wordpress.org/core/
components/i18n/
Help!

41. Thanks!