We initially chose Entity Translation as our translation method as this seems to be the way of Drupal's future. We also use Lingotek to add translations via their module. Several patches and two languages later, continued issues with translations not working as expected and third-party module integration caused us to switch to Content Translation. This was done just before adding German translations. I will talk about how we did the switch and how the site now runs both Content and Entity Translation together. The site is not completely translated either, adding further interest to the pot.
Experience level
Intermediate
Presenter Name
Dave Myburgh
Presenter's Bio
Dave got involved with Drupal in the old days of 4.6 (almost 7 years now). His second Drupal website had to be a multilingual one, so it was a good example of learning things the hard way. He worked as a freelancer for several years before joining Acquia in 2011. He currently maintains their corporate website acquia.com.
Target Audience:
Date and time
Friday, February 22, 2013 - 5:45pm to 6:45pm
Room
FSS4007
Slides
- Date modified: