multilingual solutions florian loretan

Multilingual solutions

Florian LoretanCo-FounderWunderkraut

[email protected]

Wednesday, June 13, 2012

Sponsors

Генеральный спонсор

Серебряный спонсор Серебряный спонсор

Бронзовый спонсор Бронзовый спонсор

Организатор

Suzanne Kennedy

Co-founder

Evolving Web in Montreal

evolvingweb.ca

@suzanne_kennedy


Florian Loretan

Co-founder

Wunderkraut in Munich

wunderkraut.com

@floretan

Before you start• What kind of site are you building?• Planning your multilingual site

Building a Multilingual Site• Getting Set Up• Translating the UI• Translating Content• Translating Everything Else

What’s Next?• Challenges in Drupal 7 Multilingual• Learn More & Contribute


What Kind of MultilingualSite are You Building?


Foreign Language Site


Multilingual Site


Multilingual Site + Translation


Questions to AskBefore You Start


1. What Language SupportAre You Providing?


Souce: http://www.flickr.com/photos/caribb/89857146/Wednesday, June 13, 2012

Source: http://www.lilith-ezine.com

Fully Symmetric ExperienceEnglish


Polish

Asymmetric ExperienceFrench


English

Mixed Language ExperienceFrench


English

2. Do You Want to ShowUntranslated Content?


Showing Untranslated Content


Hiding Untranslated ContentFrench


English

3. Are language and regionrelated?


Language = Region


4. Who’s Doing theTranslation?


Translation Workflow


Translating the Admin UI


5. Default Language of theSite?


Default Language

Site User


Content Language Fallback

Default Language

Site Builder


Language used User-entered Strings

6. How Will Language Affectthe Design?


Space Requirements

English

French


Right-to-Left Languages


7. What Type of Text areYou Translating?


Different Types of Text


UI: Variables


UI: Text in Code


UI: User-Entered Strings


Content: Nodes


Content: Other Entities


Text Groups


Translation Checklist:UI Text

Variables

Text in CodeUser-Entered Strings

ContentNodes

Entities (comments, users, terms...)

Text Groups (blocks, paths, menu items...)


Building YourMultilingual Website


STEP 1:Setting up Languages


Installing a LanguageConfiguration > Regional & language > Languages


Configuring a Language


Choosing a DefaultConfiguration > Regional & language > Languages


Detection and SelectionConfiguration > Regional & language > Languages > Detection and Selection


Detection and Selectionexample.com/fr/user


Detection and Selectionexample.com/user


STEP 2:Translating UI Text


Translating Variables


Translating VariablesConfiguration > Regional & language > Multilingual Settings > Variables


Translating Variables


Translating Text from Code


Translating Text from CodeConfiguration > Regional & language > Translation Interface > Translate


Translating Text from Code


User-Entered Strings


User-Entered StringsConfiguration > Regional & language > Translation Interface > Translate


User-Entered Strings


STEP 3:Translating Content


Translating Content


Settings per Content Type


Node Translation

• Content Translation module (core)

• New node for each translation

• Nodes are mapped together


Translating a Node


Field-Level Translation

• Entity Translation module (contrib)

• Translation of fields instead of nodes

• Fields are translatable in core


$node->field_body['en'][0]['value']


Semantic structure


Setting up Field Translation


works fornodesusers

taxonomy termscomments

...Wednesday, June 13, 2012

• •

• •••

TranslatabilityCan be translated Can’t be translated

•All fields •Author

Additionalper-translationmetadata


•

Promoted

Creation date

Modification date

Title...

Title Module$node->title$term->name$term->description

$node->field_title$term->field_name$term->field_description


Use field_title inviews, not title


Language fallback


Combination with i18n

•Enable •Disable

••

i18n_menu

i18n_fields••

i18n_select

i18n_taxonomy


:-)


:-(

integration with other modulesneeds work


:-(

revisioning


:-(

menu items needs to betranslated separately


:-)

for many use cases,it’s still a lot better than the standard

content translation


Adding a Translation


Comments per Language


STEP 4:Translating Everything Else


Other Elements to Translate

• Blocks

• Field settings

• Menu items

• Taxonomy terms

• Paths


Translating Field Settings



• Field Translation module (i18n)

• Translate field settings

• Only core field settings


Translating Menus


Translating Menu Items

• Menu Translation module (i18n)

• Menu per language OR

• Menu items per language


Translating Menu ItemsMenu Link to a Node


Translating Menu ItemsMenu Link to a Single-Language Page

i.e. Events View



Menu Link to a Generic Pagei.e. Home Page


STEP 5:Extending Multilingual

Functionality


Localization Updatelocalize.drupal.org


Localization Client


Drupal 8

• Clean Up• Entity translation

• Symphony localization component


Спасибо за внимание

Florian LorétanCo-FounderWunderkraut

[email protected]


Sponsors

Генеральный спонсор

Серебряный спонсор Серебряный спонсор

Бронзовый спонсор Бронзовый спонсор

Организатор

multilingual solutions florian loretan

Technology