multilingual

Drupal 8 includes support for a Kwalify (http://www.kuwata-lab.com/kwalify/) inspired schema/metadata language for configuration YAML files. Kwalify itself is written in Python and we needed slight adjustments in the format, so not all of the details of Kwalify are directly applicable, but it is pretty close.

Table of contents

• An introductory example
• What are schema files used for?
• Types supported in metadata files
• Properties
• Dynamic type references
• Code style to use for schema files
• PHP API
• Debugging your schema
• Even more background information

An introductory example #

Take site maintenance mode settings as a simple first example. System module has a core/modules/system/config/system.maintenance.yml file to contain the two settings related to maintenance mode (whether the site is taken offline for normal visitors):

This documentation page is based on an extensive comment by j2b. Needs rewording and style review. Will need updating once the commerce patch in #1495570: Update Entity translation integration is committed.

Basis

At the time of writing the Drupal Commerce Kickstart distribution (dev 2.x) does not work properly with Entity Translation. This document was created with the help of a clean copy of Commerce and the following modules: Search API, Facet API, Views, Entity, Commerce, Entity Translation, i18n. The Entity Cache was not installed. (@todo why?)

While building another multilingual site - this time in D7 - am back at the point of how to deal with the menus.
Note that, though the "Contact" module (the contact form) is part of Drupal core, the translation of its menu title requires the "internationalization" contributed module. See HowTo: Basic Internationalization setup.
I had a brief look at the new translation functions in D7 and they all look a good step forward - for ex. see more here:

• Drupal 7's new multilingual systems (part 1) - The basics and further parts ...

But translating a website is not a simple thing and the ins and outs are quite complex - just think about the admin language you know all the terms in (your personal default) and then look at those translation into one or another language you also master - often there is no correlation and you need to switch back and forth to work your way through things.

While simply translating a menu is great in many cases there are certain limitations.

This time I am building a website for proximity searches - the background for this project is here - Openlayers Proximity Search – D7 - the background.

Analog to 'Node Source' there is an 'Entity Sources' listing on which you can manage bulk translation with entities.

Go to Administration > Configuration > Regional and language > Translation Management > Entity Sources. Here you can access all entity types that have been marked as translatable. In the case below 'Comment' and 'Node'.

In this case we want to translate entites with 2 different source languages. Therefore 2 seperate jobs will be created. The need to be submitted to translator in sequence. With the first job the the button will say 'Submit to translator and continue' to indicate that there are more jobs to take care of.

The rest of the process works the same as in the previous cases.

Administration > Configuration > Regional and language > Translation Management > Jobs provides a good overview of all pending jobs.

The jobs and items are color coded:

A pie chart represents the items included in the job as well as the prgress that has been made so far.

From here you can execute mass operations by marking jobs with the check box and then choose an appropriate operation. Click the 'execute' button for execution.

By clicking on the 'manage' link in a job you will get the details of a job.

From here you can start activities on job items.

Good to know: You can override the default label after having requested the job and give it a name with a meaning. That can be very helpful when managing several translation jobs.

Want help getting started in D8? Maybe you should check out Core contribution mentoring?

We are hard at work on the next version of Drupal. Some of the great things planned include better HTML5 and mobile support, improved multilingual features, and setting up Drupal 8 on a modern web development framework. But we can't do any of it without your help!

Planned timeline

The D8 team has been very hard at work to compile this information, and we have a googledoc that will be a bit more detailed than this image could provide. Keep an eye on Gabor's new website www.drupal8multilingual.org your one-stop-shop for info on D8MI.

VIEW DETAILED TIMELINE WITH LINKS TO ISSUES HERE!

More information on Drupal 8 dates.
Feature Freeze Extension Announcement

Core development structure

Drupal 8 is the first development cycle introducing so called Core initiatives. These are areas with named leads to improve Drupal core in certain areas. However, this does not limit core development to these main areas, there are many community initiatives as well. If you head a community initiative and want to get on this summary, contact Shannon Vettes.

Core initiatives status overview