Your SlideShare is downloading. ×
  • Like
Building Multilingual Sites in Drupal 7 by Yoni Steingiesser
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Building Multilingual Sites in Drupal 7 by Yoni Steingiesser

  • 1,507 views
Published

The experience I had building multilingual sites in Drupal 7. Special thanks to Suzanne Kennedy for allowing me to use some of the content from her presentations at DrupalCon Denver 2012 and DrupalCon …

The experience I had building multilingual sites in Drupal 7. Special thanks to Suzanne Kennedy for allowing me to use some of the content from her presentations at DrupalCon Denver 2012 and DrupalCon Munich 2012.

Published in Design , Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,507
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
15
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Searching for information in a different language. People will not find your information if it is not translated.
  • Things to keep in mind

Transcript

  • 1. About Me Senior Web Coordinator at Information Services at the University of WA Founder of Stemaco Technology  UX Design, Consulting, Drupal  stemaco.com.au Twitter: @stemaco
  • 2. Drupal at UWA News System Information Services Suggestions System Trialling CiviCRM
  • 3. Why I needed to create aMultilingual Experience ? My Wedding – becandyoni.com The User Experience:  reaching the target audience in their language
  • 4. Why Multilingual? Reach a wider audience Expand to new markets Improve usability Search engine optimization Government regulations Company policy
  • 5. Things to consider whenbuilding multilingual sites How many languages do you need to support? Does the user interface need to be fully translated? Do you have content in all the languages? Is all the content translated? What happens to content that has not been translated?
  • 6. What is Multilingual in Drupal?Type of Site Core Modules Contributed Explanation ModulesForeign- Locale Install Drupal in alanguage site foreign languageMultilingual site Locale i18n User Interface and Each node in a different language Menus & Blocks TranslatedMultilingual site Locale i18n + Entity Introduce Content+ Translations Translation Translation or Content e.g About Us Translation
  • 7. What comes with core? Locale - Adds language handling functionality and enables the translation of the user interface to languages other than English
  • 8. Internationalization i18n - drupal.org/project/i18n Developing a website that enables localization of content and other elements Separating elements that should be localized so they can be specified for each locale
  • 9. Localization l10n Process of adapting a website for a certain locale including:  Translation of text and graphics  Numeric, date and time formats  Currency  Time zones  Legal requirements Localized Drupal Distribution to install Drupal with user interface translations pulled automatically from localize.drupal.org
  • 10. Other ContributedModules I used Entity Translation – Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation Language Icons – provides icons for language links
  • 11. Fully Symmetric Experience
  • 12. Asymmetric Experience
  • 13. What about untranslatedcontent? You can either show it in the language where you have the content for all languages OR Hide the untranslated content
  • 14. Content TranslationMethods Node-Level Translations Field-Level Translation Other Entity Types  Core Entities e.g Comments, Taxonomy terms, Users  Entities from contributed modules e.g Commerce Product Entities
  • 15. Right to Left Languages
  • 16. Types of Text
  • 17. Cost of Translation Time-consuming UX – Context, local awareness, jargon etc Expensive How can you speed up the process and reduce the amount of text to be translated?
  • 18. Content TranslationWorkflow
  • 19. Creating a TranslationWorkflow from Scratch Permissions for translators Rules and Flag to trigger translation requests Views for Translators
  • 20. Permissions forTranslation Node-Level Translation: Translators need to be able to create content Field-Level Translation: Permissions to edit the entity
  • 21. Typical UI for Translators
  • 22. Challenges Different UI for Entity Translation/Content Translation is confusing Professional translators need to learn Drupal Need to build system for reviewing translations
  • 23. Demo Enabling Locale Module Add Language (Language Name or Custom) Detection and Selection Enabling i18n module
  • 24. Demo – EnablingLanguage Support1. Content Types > Basic Page > Translate > Edit2. Publishing Options – Enabled, with translation3. Save4. Multilingual Settings  Require language  Normal
  • 25. Acknowledgement Suzanne Kennedy’s presentations in:  DrupalCon Denver - denver2012.drupal.org  DrupalCon Munich - munich2012.drupal.org