What I was thinking is that I have understood if a project do a pre-release (beta, RC or similar) l.d.o will parse it and make it available for translations. Then it can be translated, and merged with the final release. Otherwise translations will always be a step behind releases. I have no actual experience with this side.
Translators will need some time to do the translation, but if you give a notice that there are a new release on the way, it should be possible to speed things up.
#1
Added translation in 6.x-1.x-dev. Please review that the translation remains complete in this version.
#2
it is up to date for 1.8 at l.d.o
please do a pre-release and give a notice, and we can keep translations up to date over at l.d.o
i have attached the 1.8 from l.d.o
#3
New translation updated. (And in the same commit made the extensive filter tips translatable.)
This is my first encounter with the localization process. Could you explain what you mean by "please do a pre-release and give a notice"?
#4
Short story, I don't really know.
You can start here: http://localize.drupal.org/faq
What I was thinking is that I have understood if a project do a pre-release (beta, RC or similar) l.d.o will parse it and make it available for translations. Then it can be translated, and merged with the final release. Otherwise translations will always be a step behind releases. I have no actual experience with this side.
Translators will need some time to do the translation, but if you give a notice that there are a new release on the way, it should be possible to speed things up.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.