Your SlideShare is downloading. ×
Babel and Beyond - Professional Multilingual Solutions with Drupal
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Babel and Beyond - Professional Multilingual Solutions with Drupal


Published on

Published in: Business, Technology

1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. I – Introduction > About WunderkrautWunderkraut is... Drupal Service Provider, Munich, Germany Drupal-Expertise, Consulting, Training, Implementation Customers in Europe and USA Multiple years of doing Drupal → wunderkraut.comPresenting today: Reinhard Gloggengiesser Florian Lorétan
  • 2. I – Introduction > Babel and Beyond: Building multilingual websites with Drupal
  • 3. I – Introduction > • Principles of multilingual sites • Questions to ask yourself • The most important Agenda modules • Language detection and selection • Integration with external tools and services • Outlook for Drupal 8
  • 4. I – Introduction > What is a multilingual site?A site in a different language than english?A site with its interface in multiple languages?A site with content in multiple languages?A site with different content for each language or translated content?A mixture of all of the above?
  • 5. I – Introduction > A foreign language site Just one language for site visitors Interface, messages etc. need to be translated
  • 6. I – Introduction > Interface in different languages Content stays mostly the same Navigation, info-blocks, important buttons are translated Suitable for cases where you want to offer at least *some* internationalization.
  • 7. I – Introduction > Different content in multiple languages Content is different depending on the selected language Switching between languages changes the interface as well Suitable for cases where you offer highly individual content to different audiences.
  • 8. I – Introduction > Translated content in multiple languages Content is the same no matter what is the selected language Switching between languages changes the interface as well Suitable for cases where you have ample resources to translate all your content.
  • 9. I – Introduction > Question to ask yourself What resources do you have for doing translations? Shall untranslated content be visible? Do languages correlate to regions? Who will translate? What will be the default language of the site? How will language affect the design of the site?
  • 10. II – Techniques > The most important modulesDrupal CoreLocaleContent translationContributedI18n (Internationalization)Entity translationLocalization updateTranslation overviewLocalization client
  • 11. II – Techniques > Translating interface textsLocale moduleManually import, edit andexport interface translationsSearch all translatablestringsFilter by language andstatusDrupal 6 and 7
  • 12. II – Techniques > Translating interface textsLocalization updateDownload and updatecurrent translations of Drupalcore and contributedmodulesFromSelect update strategyDrupal 6 and 7
  • 13. II – Techniques > Translating interface textsLocalization clientChange and savetranslations for interfacestrings right from the pageNo need to enter admininterfaceDrupal 6 and 7
  • 14. II – Techniques >Translating content
  • 15. II – Techniques > Translating contentSettings per content typeDifferent methods for different content types are possible.
  • 16. II – Techniques > Translating contentNode translationContent translation module(Drupal core)New node for eachtranslationNodes are mappedtogether
  • 17. II – Techniques > Translating contentField level translationEntity translation module(Translation of fields instead $node->field_body[en][0][value]of nodesFields are translatable incore
  • 18. II – Techniques > Field level translationWorks for:NodesTaxonomy termsUsersComments...
  • 19. II – Techniques > Field level translationTranslatability:Can be translated: Can‘t be translated:All fields AuthorAdditional per-translation Promotedmetadata Creation and modification date Title...
  • 20. II – Techniques > Field level translationTitle module:$node->title$term->name$term->description $node->field_title $term->field_name $term->field_description
  • 21. II – Techniques > Field level translationLanguage fallback
  • 22. II – Techniques > Language detection By URL , /en, /fr ... ,, , From session User preference Browser settingFreely sortable!
  • 23. III – Using external tools > Translations fromTranslations for Drupalcore, modules, and themesEveryone can participate!Source for translations viaDrupal 5, 6 and 7
  • 24. III – Using external tools > TranslationProvides integration withexternal translationmemoriesProvides dashboard fortranslationsDrupal 6 and 7
  • 25. III – Using external tools > Translation ManagementDifferent module!Pluggable architecture forintegrating various backends  Google translate (machine)  Bing translator (machine)  Nativy (human)  MyGengo (human)  Supertext (human)  One hour translation (human)Drupal 7 only
  • 26. III – Outlook > The future of multilanguage in DrupalMultilanguage in Drupal 7: Lots of different modules Overlapping functionalityMultilanguage in Drupal 8 Interface and content translation built into core Cleanup of functionality