Slide 1
Slide 1 text
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
in_array( $me, $french ); // very false
Slide 4
Slide 4 text
Learned one word:
Slide 5
Slide 5 text
(supposedly fits in almost every situation)
https://twitter.com/wordpress_fr/status/421565255362150400
https://twitter.com/patriciabt70/status/421670222903250944
“Putain”
Slide 6
Slide 6 text
Slide 7
Slide 7 text
The Multilingual Blogging
Software Dilemma
…and ways to solve it.
Slide 8
Slide 8 text
2003
Slide 9
Slide 9 text
http://ma.tt/2003/01/the-blogging-software-dilemma/
“The Blogging Software Dilemma”
Slide 10
Slide 10 text
What to do?
“[…] forward compatibility has lately been
in my mind […] My logging software hasn’t
been updated for months, and the main
developer has disappeared […] could use
the existing codebase to create a fork […]”
Slide 11
Slide 11 text
Let’s do it.
“If you’re serious about forking b2 I would
be interested in contributing.”
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
2014
Slide 14
Slide 14 text
21%, YAY!
Slide 15
Slide 15 text
…in one language per site?
Slide 16
Slide 16 text
WordPress* in your language
• http://codex.wordpress.org/WordPress_in_Your_Language
• http://codex.wordpress.org/Translating_WordPress
• http://make.wordpress.org/polyglots/
*WordPress: core, themes, plugins. Not: content.
Slide 17
Slide 17 text
Language files
/languages/de_CH.mo
/languages/de_CH.po
/languages/de_DE.mo
/languages/de_DE.po
/languages/fr_FR.mo
/languages/fr_FR.po
…etc.
Slide 18
Slide 18 text
Message-level translation
__( 'Putain ce que j’ai faim!', 'domain' );
_e( 'Putain ce que j’ai faim!', 'domain' );
!
#: some-file.php:1
msgid "Putain ce que j’ai faim!"
msgstr "Gosh, I’m hungry!"
Slide 19
Slide 19 text
Provide context
_x( 'Putain ce que j’ai faim!', 'Paris', 'domain' );
!
#: some-file.php:1
#, php-format
msgctxt "Paris"
msgid "Putain ce que j'ai faim!"
msgstr "Champagne for all!"
Slide 20
Slide 20 text
Authored content
in multiple languages?
Slide 21
Slide 21 text
the_post(); // duh.
Slide 22
Slide 22 text
The Multilingual Blogging
Software Dilemma
Slide 23
Slide 23 text
The Multilingual Blogging
Software Dilemma
Slide 24
Slide 24 text
Def: dilemma
function faire_A() {
return 'putain';
}
!
function faire_B() {
return 'putain encore';
}
Slide 25
Slide 25 text
function multilingual_site() {
return 'not use WordPress'; // putain
}
!
function multilingual_wordpress_site() {
return 'depend on a plugin'; // putain encore
}
Slide 26
Slide 26 text
What to do?
“[…] forward compatibility has lately been
in my mind […] My logging software hasn’t
been updated for months, and the main
developer has disappeared […] could use
the existing codebase to create a fork […]”
Slide 27
Slide 27 text
–random international user
“Make it a core feature!!”
Slide 28
Slide 28 text
–random core developer
“Putain, no!”
Slide 29
Slide 29 text
Multilingual WordPress
• Not a core feature, because multilingual content is an edge case.
• Can be achieved with a plugin.
→ Forward compatibility depends on plugin developers.
→ When plugin is disabled, content must still work.
Slide 30
Slide 30 text
The Multilingual Core Feature
#enquelquesorte
Slide 31
Slide 31 text
WordPress Multisite
/**
* 1 installation
* multiple sites = multiple languages
*/
function multilingual_wordpress_site() {
return 'use core with multisite'; // YAY, putain!
}
Slide 32
Slide 32 text
✔ Clean, SEO-friendly URLs.
✔ Performance as good as WordPress gets, no extra rewrites.
✔ Varying plugins[, themes, users, custom post types] per language.
✔ Rock-solid, because it’s part of core.
✔ Future-proof, because it’s part of core and wordpress.com uses it.
Slide 33
Slide 33 text
Setup Multisite
• Create a network. http://codex.wordpress.org/Create_A_Network
• Create a site for each language inside the network
• That’s it, start blogging! ← Your site is multilingual here.
• Core, theme, plugins: localized by language files (message based).
• Authored content: localized by author(s).
Slide 34
Slide 34 text
–you
“What about media libraries?”
Slide 35
Slide 35 text
–Multisite
“Putain all the things!”
Slide 36
Slide 36 text
Media @ Multisite
• Shared media libraries don’t exist in WordPress.
• WordPress does not allow for multiple post-to-post relationships.
• Attachments and post images are unique and need to be physically
present in the media library of the site their parent post belongs to.
Slide 37
Slide 37 text
–you
“Duplicated media libraries SUCK!!”
Slide 38
Slide 38 text
Media libraries are key
• Meta data (alt-text, title, description/caption) should be translatable.
• Audio files can be recorded/overdubbed in multiple languages.
• Videos can have subtitles or overdubs.
→ Unique* media libraries are key for multilingual content!
*Physical assets could/should be assignable to multiple post objects.
Slide 39
Slide 39 text
Plugin Candy
Want some?
Slide 40
Slide 40 text
• Connect translated posts[, pages, custom post types].
• Display links for available languages on singular and archive pages.
• Redirect based on browser’s language settings.
• Create/edit translation in same edit screen as original post.
• Automatically duplicate post-image to media libraries of translated posts.
• Author biographic info in all languages.
• Choose back-end language independently of front-end.
• Duplicate an entire site into a new site/language.
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
No content
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
No content
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
No content
Slide 58
Slide 58 text
No content
Slide 59
Slide 59 text
No content
Slide 60
Slide 60 text
No content
Slide 61
Slide 61 text
Wrap-up
Slide 62
Slide 62 text
Multilingual WordPress Multisite
✔ Core feature.
✔ Easy setup.
✔ No extra plugin needed.
✔ Rock-solid performance.
✔ Hassle-free maintenance.
✔ Future-super-proof.
✔ Candy if you want some.
Slide 63
Slide 63 text
What’s not to like?!
Slide 64
Slide 64 text
Merci! <3
Slide 65
Slide 65 text
Caspar Hübinger
@glueckpress
!
glueckpress.com
marketpress.com
inpsyde.com
Slide 66
Slide 66 text
Photo Credits
• Matt Mullenweg: http://ma.tt/2011/05/balloon-ride/mcm_9050/ (as advised on http://ma.tt/about/)
• Mike Little: http://mikelittle.org/
• Caspar Hübinger: http://stil-etage.de