Report from the Budapest sprint on Drupal 8 Multilingual Initiative issues

We just held a one-day sprint in person in Budapest (sponsored by the NIIF Institute, heavy Drupal users themselves) and over IRC on #drupal-i18n this past weekend to make significant progress on some of the D8MI issues. Given almost all in-person attendees were new to Drupal 8, some new to working on Drupal core, I chose issues which were easier to pick up but great help for D8MI to roll along, as well as asked people to help review existing issues and work on (upgrade) tests. All-in-all, we had the following people in attendance in person: @balagan, @csg, @Desire, @eager, @hairqles, @kalman.hosszu, @pkiraly, @roderik, @tanarurkerem, @zly and myself. In attendance over IRC were @clemens.tolboom, @fubhy, @reyero and @tstoeckler. (Hope I did not leave anybody out).

We made very good progress on the following issues.

Added missing langcode schema elements on entities

To add the possibility to track language information on entities where this support is/was missing. User interface and settings to be added later by generalization of the extended node settings, see below.

• #1444992: Add langcode property in file schema
• #1444966: Add langcode property in taxonomy schema

Made good progress converting existing 'language' schema keys to 'langcode'

As part of the unification effort to improve DX (by using 'language' only where we have a full language object available).

• #1439686: Rename $node language property to langcode
• #1439680: Rename $user language property to langcode
• #1439692: Rename field language properties to langcode

Reviewed/verified issues with existing patch/tests

• #655048: Plural formula information blanked when importing a poorly-formed .po file

Reviewed patch, cleaned up tests, wrote upgrade tests

• #673020: Add the Content-Language HTTP header to the generated page
• #1272840: Add upgrade path for language domains and validation

Reviewed and improved

• #158803: Hide "Language" column in content overview table if only one language is enabled

Finally made good progress on implementing two new features!

• #1445004: Implement custom/community string bit on translations which would let locale module differentiate between community sourced and locally customized translations, making easier to keep and share customizations (part of migrating l10n_update module into core)
• #258785: Provide more flexible settings for language on content types which extends content language features with all i18n options merged in but with a user experience re-thought from the ground-up; should eventually be used across entity types and applicable to taxonomy, users, etc.

Further reviews and help in these issues is of course very welcome. We still need to drive these home to land in Drupal 8! I sincerely hope we can complete and land the ones not yet done soon and continue the work on even more advanced issues at the Denver D8MI sprint.

Thanks again for everybody who attended and helped to make this a great event.