Lost in Translation: WordPress and i18n

Lost in Translation WordPress i18n for Developers Zé Fontainhas Outernationalist @ Automattic ze.wordpress.com @_ZeF

José Zee Zoe Z Zay Zé

Localizing WordPress

Will it make you rich & famous?

NO (well, maybe)

WordPress is global Exposure Feedback Make your code/theme better It’s easy

What? Themes Plugins Core BuddyPress, PollDaddy, IntenseDebate,...

How? Wrap your strings (don’t forget the textdomain) Generate the .POT ﬁle Distribute!

Wrap your strings __($string, $domain) and _e($string, $domain) replace: echo "Some string"; with: _e("Some string", "myplugin");

Wrap your strings printf(__("There are %d comments.", "myplugin"), $count);

Set the textdomain load_plugin_textdomain($domain, $path); and load_theme_textdomain($domain, $path);

Generate the .POT ﬁle On the repository? Admin->Generate POT Otherwise checkout http://svn.automattic.com/wordpress-i18n/tools/trunk/ and php makepot.php wp-plugin your-plugin-directory

Codex bit.ly/wp-i18n Mailing list bit.ly/wp-polyglots

Distribute!

GlotPress http://glotpress.org

GlotPress Totally usable. Not less than a desktop client. Keyboard only editing, shortcuts. Very small and simple, but inﬁnitely extensible. Just like WordPress. Perfect for team collaboration. Import and export gettext ﬁles. API to be sure everything is in sync.

GlotPress Also not ready! Want to help? Submit patches & ideas to http://trac.glotpress.org

GlotPress Live beta at: http://glotpress.wordpress.com

Thanks! @_ZeF http://everywhereelse.wordpress.com

Lost in Translation: WordPress and i18n

by Zé Fontainhas on Nov 14, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 8

Statistics

Lost in Translation: WordPress and i18n — Presentation Transcript