You can get a translator account and commit your translation freely. There is, for example, japanese translation included in the official package. If you commit yours, it will be included in the next release.
Sure, why not. Haven't contributed to CVS before.
Got an account right away!
Now I have committed the Swedish translation. Should I make an issue every time I make a translation to a module just to inform the manager of the module and also other people interested?
Anything I should do different next time I commit a translation?
I saw your commit to HEAD. You should also commit it to the Drupal-6--1 branch so that it can be included in the next IMCE 6.x-1.1 release. Translations are committed independent of the project. You don't need to do anything extra.
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
ufku commentedYou can get a translator account and commit your translation freely. There is, for example, japanese translation included in the official package. If you commit yours, it will be included in the next release.
Comment #2
magnus commentedSure, why not. Haven't contributed to CVS before.
Got an account right away!
Now I have committed the Swedish translation. Should I make an issue every time I make a translation to a module just to inform the manager of the module and also other people interested?
Anything I should do different next time I commit a translation?
Comment #3
magnus commentedComment #4
ufku commentedI saw your commit to HEAD. You should also commit it to the Drupal-6--1 branch so that it can be included in the next IMCE 6.x-1.1 release. Translations are committed independent of the project. You don't need to do anything extra.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
magnus commentedI have updated the Swedish translation and POT for 6.x-1.x.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #8
magnus commentedUpdated Swedish translation and committed to CVS.
Comment #10
magnus commentedImported Swedish translation to localization server and removed CVS file.
If anyone wonder why the translation is gone, please see Maintainer News dec 7 2010:
Comment #11
magnus commented