Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Do you know people who contribute to that server and would jump on contributing here? I'd love to get the language list cleaned out on drupaler.ru too, so we can point people to the official language list.
Unfortunately I'm only aware of the people contributing to the Estonian translation project.
I know that Serbian translation is managed on a separate server as well even though it is listed on drualer.ru - http://drupaler.ru/forum/1060.
nonsie The Official Estonian translation group is working on the site (http://drupaler.ru) with 2007-nov-29. In this group has actively worked 13 people. Be careful ;). Gábor Hojtsy I can stop the work of this group at drupaler.ru, if it is convenient to all participants.
How to save the work of these people and move it to localize.drupal.org?
@pvasili, when were the latest changes made for Estonian language on drupaler.ru? http://l10n.theoriginalnetbaby.com has 30 registered users and its translations are posted under ET translation project on d.o. Notice there is nothing in ET issue queue about moving Estonian translation to drupaler.ru even though the translation project was created 2 years before Estonian translation appeared on drupaler.ru
@Gábor Hojtsy I don't really care at this point any more - all I am requesting is getting ET translation moved to localize.drupal.org. kaido24, martig, milosh and myself have been the most active contributors to this translation project. If we have to redo everything then that's that. At least we have documentation about general guidelines how to translate into Estonian - http://localize.theoriginalnetbaby.com/node/2
@pvasili: I think nonsie has some good points showing your setup is not where the action happens. With due respect to those, who found and contributed to your server, we should however import that data. While @nonsie might not care, those who's work would be trashed would probably care. You can directly export the translations from the server as .po files, which can then be imported on localize.drupal.org. That would not help that about 2000 suggestions which are also there given #572676: Export suggestions in .po files is unresolved so far with the expectation of cooperating existing teams.
@Gábor Hojtsy - I'm very worried about the issue of transfer of accumulated data to localize.drupal.org.
At http://drupaler.ru worked a few people (the ET group was created at their request), and I wish that this work has been preserved for all people at drupal.org
I can send you a dump tables l10n_community_string & l10n_community_translation. (I do not know a convenient way to make 4100 PO files off all modules :) )
Just FYI the translations from drupaler.ru were imported into ET language project as part of this issue - http://drupal.org/node/349170 e.g. translations on drupaler.ru in Dec, 08 were cleaned up and added.
I think it's best to start from scratch in this situation - reviewing old stuff from two sources is as time-consuming as creating a brand new translation.
@killes yes, I have (you can see my translations used at mesindus.ee for example). I'm trying to find a neutral way how to get the Estonian translation done. So far there are two half-done translations you can't use due to lack of both readiness and quality.
The fact that the drupaler.ru translations were synced to drupal.org almost a year ago only helps, if the drupaler.ru Estonian team was inactive for this period. If substantial work was done, we'd loose that again. The Ukrainian team devised an interim method to generate .po files from CSV database dumps (see http://drupal.org/node/577830), so it might be useful to contact them for help so you can migrate all this data to localize.drupal.org and continue translating here.
Gábor, here's an update what has been going on behind the scenes in the Estonian Drupal community.
A poll was posted to choose which translation should be preferred or if it should be started from the scratch - http://groups.drupal.org/node/27862. In almost two weeks there has been only been three votes - one of which is mine. It really comes down to the "give us tools and make it easy and then I'll consider contributing" approach. Estonian translation community has never been active like other communities out there...
My personal plan is to go through the remaining 1500 or so suggestions on http://localize.theoriginalnetbaby.com, commit those to ET translation project and hand it off to whoever cares enough to look past the approach I mentioned above. As it stands you and I are the only people who care about keeping the existing translation in some form.
- Estonian Drupal community is very much in grinding halt because the lack of the official Estonian translation download (in somewhat decent quality). The is no way to evangelize Drupal around here without ability people to build sites to local market in local language. We need it fast.
- I can not the follow complex story behind historical two versions of the translation. It is not that relevant for most people. All they want is: an official translation download in whatever quality (as long it is clearly said what is the completion ration of the translation release and what is the process to improve it)
- Nonsie's plan makes sense (do I follow it correctly: she brings old translations from http://localize.theoriginalnetbaby.com to http://localize.drupal.org/ ?). We can sort out the official translation caretaker amongst the community when she decides to resign.
Why is everyone ignoring the outstanding thousand of suggestions on drupaler.ru? Also, from @nonsie's comments, it seems like she is still working on approving/declining those suggestions to prepare for the migration.
Lucky neighbours, they don't have to worry about legacy problems and can actually start translating ..
We are somewhat in a same situation as the goat who stands between two haystacks and can't decide which one is better. The truth is that the best is not the moulded hay but a fresh grass beneath its legs ;)
AFAIK Nonsie is almost-ready to push the http://localize.theoriginalnetbaby.com changes over to l.d.o. The community seems to have agreed to reject drupaler.ru work according to g.d.o/estonia poll. We are ready to move on and build on nonsie work.
Please expect that there might be bumps in the service. You are among the beta-tester of this live instance. Thanks for helping out and please report issues as you find them! Your team members can now join and help import existing translations and work on more translations.
Also note that I've set this up so that it uses a controlled model (that group admins moderate translations). If you'd rather work in an open model (that everyone can directly submit translations), that is up to you and you can edit your group node to reconfigure anytime.
Comments
Comment #1
nonsieAlso - I am the current maintainer of the Estonian translation and Estonian translation server on http://l10n.theoriginalnetbaby.com/.
http://www.drupaler.ru/ listed on http://drupal.org/project/l10n_server is not the official Estonian translation server.
Comment #2
gábor hojtsyDo you know people who contribute to that server and would jump on contributing here? I'd love to get the language list cleaned out on drupaler.ru too, so we can point people to the official language list.
Comment #3
nonsieUnfortunately I'm only aware of the people contributing to the Estonian translation project.
I know that Serbian translation is managed on a separate server as well even though it is listed on drualer.ru - http://drupaler.ru/forum/1060.
Comment #4
gábor hojtsyI've contacted the maintainer of drupaler.ru to comment on this issue too.
Comment #5
pvasili commentednonsie The Official Estonian translation group is working on the site (http://drupaler.ru) with 2007-nov-29. In this group has actively worked 13 people. Be careful ;).
Gábor Hojtsy I can stop the work of this group at drupaler.ru, if it is convenient to all participants.
How to save the work of these people and move it to localize.drupal.org?
Comment #6
nonsie@pvasili, when were the latest changes made for Estonian language on drupaler.ru? http://l10n.theoriginalnetbaby.com has 30 registered users and its translations are posted under ET translation project on d.o. Notice there is nothing in ET issue queue about moving Estonian translation to drupaler.ru even though the translation project was created 2 years before Estonian translation appeared on drupaler.ru
@Gábor Hojtsy I don't really care at this point any more - all I am requesting is getting ET translation moved to localize.drupal.org. kaido24, martig, milosh and myself have been the most active contributors to this translation project. If we have to redo everything then that's that. At least we have documentation about general guidelines how to translate into Estonian - http://localize.theoriginalnetbaby.com/node/2
Comment #7
gábor hojtsy@pvasili: I think nonsie has some good points showing your setup is not where the action happens. With due respect to those, who found and contributed to your server, we should however import that data. While @nonsie might not care, those who's work would be trashed would probably care. You can directly export the translations from the server as .po files, which can then be imported on localize.drupal.org. That would not help that about 2000 suggestions which are also there given #572676: Export suggestions in .po files is unresolved so far with the expectation of cooperating existing teams.
Comment #8
pvasili commented@Gábor Hojtsy - I'm very worried about the issue of transfer of accumulated data to localize.drupal.org.
At http://drupaler.ru worked a few people (the ET group was created at their request), and I wish that this work has been preserved for all people at drupal.org
I can send you a dump tables l10n_community_string & l10n_community_translation. (I do not know a convenient way to make 4100 PO files off all modules :) )
Comment #9
nonsieJust FYI the translations from drupaler.ru were imported into ET language project as part of this issue - http://drupal.org/node/349170 e.g. translations on drupaler.ru in Dec, 08 were cleaned up and added.
Comment #10
tormiI think it's best to start from scratch in this situation - reviewing old stuff from two sources is as time-consuming as creating a brand new translation.
Comment #11
killes@www.drop.org commented@tormi: have you ever done a translation? Drupal core has now 3500 strings, that's a _lot_ of work.
If pvasili can confirm that the translations from drupaler.ru were added to the translation here at drupal.org?
Comment #12
tormi@killes yes, I have (you can see my translations used at mesindus.ee for example). I'm trying to find a neutral way how to get the Estonian translation done. So far there are two half-done translations you can't use due to lack of both readiness and quality.
Comment #13
gábor hojtsyThe fact that the drupaler.ru translations were synced to drupal.org almost a year ago only helps, if the drupaler.ru Estonian team was inactive for this period. If substantial work was done, we'd loose that again. The Ukrainian team devised an interim method to generate .po files from CSV database dumps (see http://drupal.org/node/577830), so it might be useful to contact them for help so you can migrate all this data to localize.drupal.org and continue translating here.
There is not yet an implementation to export suggestions due to how they are not compatible with our transport format. See #572676: Export suggestions in .po files. So either temporary hacks are needed like the Ukranian method, or you need to wait on #572676: Export suggestions in .po files (or help implement it).
Comment #14
nonsieGábor, here's an update what has been going on behind the scenes in the Estonian Drupal community.
A poll was posted to choose which translation should be preferred or if it should be started from the scratch - http://groups.drupal.org/node/27862. In almost two weeks there has been only been three votes - one of which is mine. It really comes down to the "give us tools and make it easy and then I'll consider contributing" approach. Estonian translation community has never been active like other communities out there...
My personal plan is to go through the remaining 1500 or so suggestions on http://localize.theoriginalnetbaby.com, commit those to ET translation project and hand it off to whoever cares enough to look past the approach I mentioned above. As it stands you and I are the only people who care about keeping the existing translation in some form.
Comment #15
kika commented- Estonian Drupal community is very much in grinding halt because the lack of the official Estonian translation download (in somewhat decent quality). The is no way to evangelize Drupal around here without ability people to build sites to local market in local language. We need it fast.
- I can not the follow complex story behind historical two versions of the translation. It is not that relevant for most people. All they want is: an official translation download in whatever quality (as long it is clearly said what is the completion ration of the translation release and what is the process to improve it)
- Nonsie's plan makes sense (do I follow it correctly: she brings old translations from http://localize.theoriginalnetbaby.com to http://localize.drupal.org/ ?). We can sort out the official translation caretaker amongst the community when she decides to resign.
- are there any other roadblocks? How can I help?
Comment #16
killes@www.drop.org commentedI propose we proceed with creation of the group and make kika the initial maintainer. They can then sort out things among themselves.
Comment #17
tormi+1
Comment #18
gábor hojtsyWhy is everyone ignoring the outstanding thousand of suggestions on drupaler.ru? Also, from @nonsie's comments, it seems like she is still working on approving/declining those suggestions to prepare for the migration.
Comment #19
tormiLucky neighbours, they don't have to worry about legacy problems and can actually start translating ..
We are somewhat in a same situation as the goat who stands between two haystacks and can't decide which one is better. The truth is that the best is not the moulded hay but a fresh grass beneath its legs ;)
Comment #20
kika commentedAFAIK Nonsie is almost-ready to push the http://localize.theoriginalnetbaby.com changes over to l.d.o. The community seems to have agreed to reject drupaler.ru work according to g.d.o/estonia poll. We are ready to move on and build on nonsie work.
Comment #21
gábor hojtsyOk, if you decide to reject the drupaler.ru translation, I cannot do anything about it. This debate already postponed decision for months.
Created team at http://localize.drupal.org/languages/et
Please expect that there might be bumps in the service. You are among the beta-tester of this live instance. Thanks for helping out and please report issues as you find them! Your team members can now join and help import existing translations and work on more translations.
Also note that I've set this up so that it uses a controlled model (that group admins moderate translations). If you'd rather work in an open model (that everyone can directly submit translations), that is up to you and you can edit your group node to reconfigure anytime.
Consequently, I've also removed the listing of the existing drupaler.ru server at http://drupal.org/project/l10n_server.
Welcome on board!
Comment #22
nonsieThanks, Gábor;)
Comment #23
tormiCool! Thanks, Nonsie and Gábor!