Oversetting

We are planning several changes for Drupal 8 to improve the user experience around translations of the Drupal software (including its modules, themes and distributions). We plan to build in the Localization update module into Drupal 8 core, and we are on track doing some of those steps. We also want to improve the general user experience of some software translation tools we have in Drupal, and your feedback on both counts would be very appreciated.

Improvements to the built-in software translation interface

We have fixed a long standing bug of idenification of singular/plural string pairs such as "1 minute"/"@count minutes". If you did not load in a .po file in Drupal 7 and before, the identification of these source strings never related them to each other, and translating them properly was impossible on the user interface. We fixed this bug by changing the storage for singular/plural pairs, and introduced a temporary complication to the built-in translation UI. We kept the search/overview screen as-is in Drupal 7 and before. See the third and second images at http://drupal.org/node/532512#comment-5641302.

We think that people go to the translation screen to actually translate things, and also that it is more likely that people want to translate multiple things into one language (which the current UI does not support at all) versus translating one thing to many languages (which the current UI is optimized for). So we have an ongoing discussion at http://drupal.org/node/1452188 with various UI idea to move forward. The most up to date list of options we considered is at http://drupal.org/node/1452188#comment-5777686

Because there are so many directions we can go, and we don't necessarily agree on the exact goals of the UI either, feedback from translators would be extremely valuable. If we cannot agree, the worst thing that can happen is that we'll release with the UI as-is now in Drupal 8, which I think is not ideal. Your feedback welcome!

Custom string translation tracking

We already centralized .po file lookup into one directory, so Drupal 8 will not look at various places under modules, etc. for .po files. This is very useful to support distribution and staging/deployment of translations without interference to version control of the source repositories. Adding in automated download and import of .po files from the community is still to be done.

However, because most community translations are not complete and we want to keep the possibility for people to customize translations downloaded from the community, we are building custom string tracking and customized string protection into the APIs and the UI. This is being discussed in http://drupal.org/node/1445004 with the main UI simplification / new UI additions explained in http://drupal.org/node/1445004#comment-5673836 and the following comments. I hope/believe that even though we are adding some new functionality here, we can also use this opportunity to not complicate the UI much at the same time and build in the automated translation feeding in a way that people can still customize and divert from as needed. Because the proposal does add some new concepts and UI components to the .po import/export screen to understand, it would be great if you could help provide feedback on whether the additions make sense and the simplification of the extended functionality helps make it easier to understand overall.

Future issues

If the changes proposed look exciting to you and you are interested in being involved, the Drupal 8 Multilingual Initiative is meeting every second Wednesday on IRC in the #drupal-i18n channel. Meeting announcements with exact times are posted on http://groups.drupal.org/drupal-initiatives. People from all experience levels and all angles are welcome!

read more

Drupal 7 was released 13 months ago, and while Drupalcon sites (like Denver and Munich) are built on Drupal 7, none of the permanent Drupal.org sites are on Drupal 7 yet (or started to being ported to Drupal 7). This is usually due to (a) huge custom built modules or setups used that are hard to migrate (b) ongoing improvements to introduce better user functionality. With localize.drupal.org the situation is a bit more interesting. As I wrote in my last news post in October, Dashamir Hoxha mostly updated the huge base module for the site to Drupal 7 and Organic groups has a Drupal 7 version too, so the two biggest base modules are available. There are some interesting challenges however. The drupal.org theme (bluecheese) is not yet ported to Drupal 7 (help at http://drupal.org/node/1438716), the Organic Groups User Roles module functionality is integrated in Groups for Drupal 7 but there is no upgrade path and we'd like to switch to simpler solutions from the Messaging and Notifications monolith.

The update to Drupal 7 would be great to lead by example for other sites on drupal.org as well as keep improvements to the Localization Server module suite to one active branch. With the Drupal 7 port there and the Drupal 6 version used actively on the site, feature requests and bugfixes come in for Drupal 6 and there is a lot of extra work to port them to both versions at once.

Finally, I don't personally have time to head the effort but I can help provide guidance. Sebastien Corbin signed up to help do test upgrades and would very welcome any of your help. Want to work on updating the Drupal.org theme to Drupal 7? Figure ou an upgrade path for Organic Groups User roles to Drupal 7 Groups configuration? Help migrate Messaging and Notifications signups to a simpler framework? There are lots of opportunities to help out there. If you are interested see Sebastien's issue at http://drupal.org/node/1424984 and signal your interest there!

read more