Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
A. If you are a translation maintainer: you've already been contacted, and
your team is in the process of moving from drupal.org to localize.drupal.org.
B. If you are a translator: stop working on .po files in CVS (either for
Drupal core or contrib), instead import existing .po files from CVS to
localize.drupal.org (if not already), remove the imported file from CVS and
work on localize.drupal.org from now on.
C. If you are a drupal.org project maintainer: do not accept .po files
anymore in your issue queues and remove your .pot files from CVS; tell people
to use localize.drupal.org.
Comments
Comment #1
berdirI must have missed this.
Privatemsg 1.0 has been released now, it would be great if you could update the translation so that we can include it in the next bugfix release.
Comment #2
berdirI'm closing old translation related issues, translation should be handled on localize.drupal.org now.
Please see Maintainer News dec 7 2010 for more information:
A. If you are a translation maintainer: you've already been contacted, and
your team is in the process of moving from drupal.org to localize.drupal.org.
B. If you are a translator: stop working on .po files in CVS (either for
Drupal core or contrib), instead import existing .po files from CVS to
localize.drupal.org (if not already), remove the imported file from CVS and
work on localize.drupal.org from now on.
C. If you are a drupal.org project maintainer: do not accept .po files
anymore in your issue queues and remove your .pot files from CVS; tell people
to use localize.drupal.org.