who would be first to inhibit localize.drupal.org?
Hey, Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently - knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project. The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too. A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include: - all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways If your team would like to be among the first to migrate, let me know. Gábor
Thank you Gabor! I can finally "kick off" my l10n.drupal-contrib.org and migrate to the official one :) Blessings! On Sat, Aug 15, 2009 at 12:26 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Fernando P. García, http://www.develcuy.com Developer - Analista de Sistemas +51 1 9 8991 7871, Calle Santa Catalina Ancha #377, Cusco -Perú ** Antes de imprimir este mensaje piensa en tu compromiso con el medio ambiente, protegerlo depende de tí.
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Also state if you'd like to have suggestions kept (that still requires migration software to be written and the attributions will be lost even in that case). Gábor 2009/8/15 Fernando P. García <fernando@develcuy.com>:
Thank you Gabor!
I can finally "kick off" my l10n.drupal-contrib.org and migrate to the official one :)
Blessings!
On Sat, Aug 15, 2009 at 12:26 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Fernando P. García, http://www.develcuy.com Developer - Analista de Sistemas +51 1 9 8991 7871, Calle Santa Catalina Ancha #377, Cusco -Perú
** Antes de imprimir este mensaje piensa en tu compromiso con el medio ambiente, protegerlo depende de tí.
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
On Sat, 2009-08-15 at 19:26 +0200, Gábor Hojtsy wrote:
If your team would like to be among the first to migrate, let me know.
I used to do the bulk of the work on the Arabic project, and since I have slowed down, people were put off by CVS and other complications. A move may encourage newcomers, and I will certainly have a go at it. -- Amr Gharbeia http://gharbeia.net
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Also state if you'd like to have suggestions kept (that still requires migration software to be written and the attributions will be lost even in that case). Gábor On Sat, Aug 15, 2009 at 10:17 PM, Amr Gharbeia<amr@gharbeia.net> wrote:
On Sat, 2009-08-15 at 19:26 +0200, Gábor Hojtsy wrote:
If your team would like to be among the first to migrate, let me know.
I used to do the bulk of the work on the Arabic project, and since I have slowed down, people were put off by CVS and other complications. A move may encourage newcomers, and I will certainly have a go at it.
-- Amr Gharbeia http://gharbeia.net
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
15 aug 2009 kl. 19.26 skrev Gábor Hojtsy:
If your team would like to be among the first to migrate, let me know.
Gábor
Sweet! The Swedish translation team has a l10n server at l10n.drupalsverige.se, and I'm sure we all love the idea of moving everything over to the official server. Do we just export the projects as .po files? How about suggested translations, are those possible to migrate too? We have a team of admins helping out on our server. Will it be possible on the new server to give just a number of people the ability to accept translations in Swedish, or do all users on the server have the same permissions? Thanks! /Hannes - zoo33
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). See more below. On Sun, Aug 16, 2009 at 7:31 PM, Hannes Lilljequist<hannes@perrito.se> wrote:
The Swedish translation team has a l10n server at l10n.drupalsverige.se, and I'm sure we all love the idea of moving everything over to the official server. Do we just export the projects as .po files? How about suggested translations, are those possible to migrate too?
Well, you need to decide. Keeping suggestions still requires migration software to be written and the attributions will be lost even in that case. Please include this in your issue.
We have a team of admins helping out on our server. Will it be possible on the new server to give just a number of people the ability to accept translations in Swedish, or do all users on the server have the same permissions?
Localize.drupal.org runs the l10n_groups and og modules, so you can appoint an arbitrary number of group managers (>= 1 that is), and also pick your way of operation for the group. Either an open group where everyone can submit translations and suggestions or a moderated group where suggestions are submitted and approved or declined. Gábor
Awesome, can't wait for it! On Wed, Aug 19, 2009 at 3:19 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). See more below.
On Sun, Aug 16, 2009 at 7:31 PM, Hannes Lilljequist<hannes@perrito.se> wrote:
The Swedish translation team has a l10n server at l10n.drupalsverige.se, and I'm sure we all love the idea of moving everything over to the official server. Do we just export the projects as .po files? How about suggested translations, are those possible to migrate too?
Well, you need to decide. Keeping suggestions still requires migration software to be written and the attributions will be lost even in that case. Please include this in your issue.
We have a team of admins helping out on our server. Will it be possible on the new server to give just a number of people the ability to accept translations in Swedish, or do all users on the server have the same permissions?
Localize.drupal.org runs the l10n_groups and og modules, so you can appoint an arbitrary number of group managers (>= 1 that is), and also pick your way of operation for the group. Either an open group where everyone can submit translations and suggestions or a moderated group where suggestions are submitted and approved or declined.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Fernando P. García, http://www.develcuy.com Developer - Analista de Sistemas +51 1 9 8991 7871, Calle Santa Catalina Ancha #377, Cusco -Perú ** Antes de imprimir este mensaje piensa en tu compromiso con el medio ambiente, protegerlo depende de tí.
Hi! 2009/8/15 Gábor Hojtsy <gabor@hojtsy.hu>:
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team.
The Norwegian team is interested. We have ~9500 translated strings, in two languages. (There are two variants of Norwegian, Norwegian Bokmal (nb) and New Norwegian (nn).) We're not extremely active right now (only 3 different translators last month, only 6 last months). That may increase soon, as a large group of libraries are switching to Drupal, and recently asked us about how they could contribute to the translations. Our current server: http://lokalisering.drupalnorge.no/ (still on 5.x) I asked the other translators about early migration to the central server on our forum, and of the six translators who have contributed the last half year, five have answered either "yes" or "YES!!!" (http://drupalnorge.no/innlegg/forum/innlegg-1068). (The sixth hasn't answered yet.) Hilde / zirvap
Hi, Hilde Austlid wrote:
Hi!
2009/8/15 Gábor Hojtsy <gabor@hojtsy.hu>:
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team.
The Norwegian team is interested. We have ~9500 translated strings, in two languages. (There are two variants of Norwegian, Norwegian Bokmal (nb) and New Norwegian (nn).) We're not extremely active right now (only 3 different translators last month, only 6 last months). That may increase soon, as a large group of libraries are switching to Drupal, and recently asked us about how they could contribute to the translations.
Our current server: http://lokalisering.drupalnorge.no/ (still on 5.x) I asked the other translators about early migration to the central server on our forum, and of the six translators who have contributed the last half year, five have answered either "yes" or "YES!!!" (http://drupalnorge.no/innlegg/forum/innlegg-1068). (The sixth hasn't answered yet.)
Hilde / zirvap _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hindi team would also like to be part of this currently we have l10n server @ http://drupalhindi.com Regards Abhishek Nagar http://abhishek.nagar.me
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Also state if you'd like to have suggestions kept (that still requires migration software to be written and the attributions will be lost even in that case). Gábor On Wed, Aug 19, 2009 at 6:10 PM, Abhishek Nagar<nagar.ksp@gmail.com> wrote:
Hi,
Hilde Austlid wrote:
Hi!
2009/8/15 Gábor Hojtsy <gabor@hojtsy.hu>:
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team.
The Norwegian team is interested. We have ~9500 translated strings, in two languages. (There are two variants of Norwegian, Norwegian Bokmal (nb) and New Norwegian (nn).) We're not extremely active right now (only 3 different translators last month, only 6 last months). That may increase soon, as a large group of libraries are switching to Drupal, and recently asked us about how they could contribute to the translations.
Our current server: http://lokalisering.drupalnorge.no/ (still on 5.x) I asked the other translators about early migration to the central server on our forum, and of the six translators who have contributed the last half year, five have answered either "yes" or "YES!!!" (http://drupalnorge.no/innlegg/forum/innlegg-1068). (The sixth hasn't answered yet.)
Hilde / zirvap _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hindi team would also like to be part of this currently we have l10n server @ http://drupalhindi.com
Regards Abhishek Nagar http://abhishek.nagar.me _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Also state if you'd like to have suggestions kept (that still requires migration software to be written and the attributions will be lost even in that case). Gábor On Sun, Aug 16, 2009 at 8:51 PM, Hilde Austlid<zirvap@gmail.com> wrote:
Hi!
2009/8/15 Gábor Hojtsy <gabor@hojtsy.hu>:
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team.
The Norwegian team is interested. We have ~9500 translated strings, in two languages. (There are two variants of Norwegian, Norwegian Bokmal (nb) and New Norwegian (nn).) We're not extremely active right now (only 3 different translators last month, only 6 last months). That may increase soon, as a large group of libraries are switching to Drupal, and recently asked us about how they could contribute to the translations.
Our current server: http://lokalisering.drupalnorge.no/ (still on 5.x) I asked the other translators about early migration to the central server on our forum, and of the six translators who have contributed the last half year, five have answered either "yes" or "YES!!!" (http://drupalnorge.no/innlegg/forum/innlegg-1068). (The sixth hasn't answered yet.)
Hilde / zirvap _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
If your team would like to be among the first to migrate, let me know.
Gábor
Dear Gabor, The timing of the release of new localization server is really coinciding with our plan to undertake localization of Drupal to Mongolian language. As a start we have already translated and submitted general.pot file. And other files are being translated. We would like to be one of the first to try out new localization server. Can you please consider our interest and include Mongolian translation. thanks in advance, Batpurev CEO, InfoCon LLC. www.infocon.mn
Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Also state if you'd like to have suggestions kept (that still requires migration software to be written and the attributions will be lost even in that case). Gábor On Mon, Aug 17, 2009 at 8:13 AM, B.Batpurev<batpurev@gmail.com> wrote:
If your team would like to be among the first to migrate, let me know.
Gábor
Dear Gabor,
The timing of the release of new localization server is really coinciding with our plan to undertake localization of Drupal to Mongolian language. As a start we have already translated and submitted general.pot file. And other files are being translated. We would like to be one of the first to try out new localization server. Can you please consider our interest and include Mongolian translation.
thanks in advance, Batpurev
CEO, InfoCon LLC. www.infocon.mn _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gábor Hojtsy schrieb:
If your team would like to be among the first to migrate, let me know.
Ok, the following teams volunteered: - - Arabic - - French (off-list) - - Mongolian - - Norwegian (x2) - - Spanish I think that's a great start. The next question is: How much do you value your translation history and existing translation suggestions (if you've been using l10n_server before)? Currently, we cannot preserve this. We can only import existing the existing PO files. So please indicate if this is ok with you. There is another caveat: we are using a new SSO solution for l.d.o. If you are logged into drupal.org and visit that site, a local account is automatically created for you. That account will use the same username and email address as drupal.org does. Unfortunately, this currently also means that you cannot change either of them after the local account was created without breaking the SSO connection. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqJS5UACgkQfg6TFvELooRD/wCeJN6+i/cLACU2DgB4xfKR/sJt z6YAn1kXY1Aq5/8/ltFscKzAtQvcoSJ5 =vRbK -----END PGP SIGNATURE-----
Hey, The brazilian team volunteered also :D Haven't you got my message? Cheers, Fabiano Sant'Ana On Mon, Aug 17, 2009 at 9:22 AM, Gerhard Killesreiter < gerhard@killesreiter.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gábor Hojtsy schrieb:
If your team would like to be among the first to migrate, let me know.
Ok, the following teams volunteered:
- - Arabic - - French (off-list) - - Mongolian - - Norwegian (x2) - - Spanish
I think that's a great start.
The next question is: How much do you value your translation history and existing translation suggestions (if you've been using l10n_server before)?
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
There is another caveat: we are using a new SSO solution for l.d.o. If you are logged into drupal.org and visit that site, a local account is automatically created for you. That account will use the same username and email address as drupal.org does. Unfortunately, this currently also means that you cannot change either of them after the local account was created without breaking the SSO connection.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqJS5UACgkQfg6TFvELooRD/wCeJN6+i/cLACU2DgB4xfKR/sJt z6YAn1kXY1Aq5/8/ltFscKzAtQvcoSJ5 =vRbK -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fabiano Sant'Ana schrieb:
Hey, The brazilian team volunteered also :D Haven't you got my message?
No, there's also nothing in the archive.
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
So, please fill out the questionaire. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqJUL8ACgkQfg6TFvELooS6ogCgsZGmJCRnIQwsBys3oov+dPei gT0AoLAxNgvIsc6upL6yOzcntQUAZWu7 =s15t -----END PGP SIGNATURE-----
Sorry I sent the message only to Gabor.Sending it to the list. fabiano On Mon, Aug 17, 2009 at 9:44 AM, Gerhard Killesreiter < gerhard@killesreiter.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Fabiano Sant'Ana schrieb:
Hey, The brazilian team volunteered also :D Haven't you got my message?
No, there's also nothing in the archive.
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
So, please fill out the questionaire.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqJUL8ACgkQfg6TFvELooS6ogCgsZGmJCRnIQwsBys3oov+dPei gT0AoLAxNgvIsc6upL6yOzcntQUAZWu7 =s15t -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hi Killes,no problem about losing our suggestions history, we still have the contributors name committed to the CVS. Cheers, Fabiano Sant'Ana On Mon, Aug 17, 2009 at 9:44 AM, Gerhard Killesreiter < gerhard@killesreiter.de> wrote:
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
So, please fill out the questionaire.
Cheers, Gerhard
Hi! Yay, we're in! * dances a happy dance * 2009/8/17 Gerhard Killesreiter <gerhard@killesreiter.de>:
The next question is: How much do you value your translation history and existing translation suggestions (if you've been using l10n_server before)?
Sacrificing the history is OK. We'll need a few days to go through the current suggestions and approve or delete them.
There is another caveat: we are using a new SSO solution for l.d.o. If you are logged into drupal.org and visit that site, a local account is automatically created for you. That account will use the same username and email address as drupal.org does. Unfortunately, this currently also means that you cannot change either of them after the local account was created without breaking the SSO connection.
That sounds like something we can live with. There are several (well, at least some) contrib module translations in CVS which were never imported to our local server. Will these also be imported to the new server? There will also be cases where there is an old translation in CVS, and a newer version on our localization server. The core translations are definitively more outdated in CVS than on the server. So when there's a conflict between the files on CVS and the files from our server, the server files should win. Hilde (zirvap)
Dear Gerhard, Thanks for inlcuding our team (Mongolian). We do not have previous history of translation except recent submission of general.po file.
From your message that can be imported no problem.
In this discussion thread, I read filling out a questionnaire but can not find any attachment? Can someone direct me to that questionnaire please. thanks, Batpurev On Mon, Aug 17, 2009 at 8:22 PM, Gerhard Killesreiter<gerhard@killesreiter.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gábor Hojtsy schrieb:
If your team would like to be among the first to migrate, let me know.
Ok, the following teams volunteered:
- - Arabic - - French (off-list) - - Mongolian - - Norwegian (x2) - - Spanish
I think that's a great start.
The next question is: How much do you value your translation history and existing translation suggestions (if you've been using l10n_server before)?
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
There is another caveat: we are using a new SSO solution for l.d.o. If you are logged into drupal.org and visit that site, a local account is automatically created for you. That account will use the same username and email address as drupal.org does. Unfortunately, this currently also means that you cannot change either of them after the local account was created without breaking the SSO connection.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqJS5UACgkQfg6TFvELooRD/wCeJN6+i/cLACU2DgB4xfKR/sJt z6YAn1kXY1Aq5/8/ltFscKzAtQvcoSJ5 =vRbK -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
@Batpurev There is a link in the FAQ of localize.drupal.org @Gábor I will really need some way to migrate suggested strings, we have a lot of valuable suggested strings pending for approval. So, just "some working way" will be enough. Blessings! On Mon, Aug 17, 2009 at 10:24 PM, B.Batpurev <batpurev@gmail.com> wrote:
Dear Gerhard,
Thanks for inlcuding our team (Mongolian). We do not have previous history of translation except recent submission of general.po file. From your message that can be imported no problem.
In this discussion thread, I read filling out a questionnaire but can not find any attachment? Can someone direct me to that questionnaire please.
thanks, Batpurev
On Mon, Aug 17, 2009 at 8:22 PM, Gerhard Killesreiter<gerhard@killesreiter.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gábor Hojtsy schrieb:
If your team would like to be among the first to migrate, let me know.
Ok, the following teams volunteered:
- - Arabic - - French (off-list) - - Mongolian - - Norwegian (x2) - - Spanish
I think that's a great start.
The next question is: How much do you value your translation history and existing translation suggestions (if you've been using l10n_server before)?
Currently, we cannot preserve this. We can only import existing the existing PO files.
So please indicate if this is ok with you.
There is another caveat: we are using a new SSO solution for l.d.o. If you are logged into drupal.org and visit that site, a local account is automatically created for you. That account will use the same username and email address as drupal.org does. Unfortunately, this currently also means that you cannot change either of them after the local account was created without breaking the SSO connection.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqJS5UACgkQfg6TFvELooRD/wCeJN6+i/cLACU2DgB4xfKR/sJt z6YAn1kXY1Aq5/8/ltFscKzAtQvcoSJ5 =vRbK -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Fernando P. García, http://www.develcuy.com Developer - Analista de Sistemas +51 1 9 8991 7871, Calle Santa Catalina Ancha #377, Cusco -Perú ** Antes de imprimir este mensaje piensa en tu compromiso con el medio ambiente, protegerlo depende de tí.
I would like Telugu (te) to be on localize.drupal.org. We didn't have a translation server set up. However, we have done some localization at etelugu.org. I (and couple of my friends) are happy to contribute via localize.drupal.org . I created an issue for creating a Translation Team for Telugu here: http://drupal.org/node/553020 Thanks, Veeven. -- Read Telugu blogs @ koodali.org
Hi Gabor, An l.d.o.is good news! The Dutch team also likes to join if there is still place among the 'first'. We have no (active) translation server. Regards, Erik Stielstra On 15 aug 2009, at 19:26, Gábor Hojtsy wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hi Erik, Perfect. Please open an issue on http://drupal.org/node/add/project-issue/webmasters categorized for localize.drupal.org. State your username on drupal.org (and log in on localize.drupal.org, so your account is created there too). Thanks, Gábor On Fri, Aug 21, 2009 at 3:44 PM, Erik Stielstra<info@erikstielstra.nl> wrote:
Hi Gabor,
An l.d.o.is good news! The Dutch team also likes to join if there is still place among the 'first'. We have no (active) translation server.
Regards, Erik Stielstra
On 15 aug 2009, at 19:26, Gábor Hojtsy wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Ok the Dutch team also joined the server. These were the first steps, lets continue... I like to get a small group working on Dutch translation at l.d.o. We can work on existing translations, but will existing translations automatically be imported from CVS? And would it conflict if we would move some translations over already? When a project translation is completed is the (current) workflow to export it and commit it into CVS? Is my understanding correctly that translations will, in due time, be removed from CVS? Regards, Erik Stielstra On 15 aug 2009, at 19:26, Gábor Hojtsy wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
On Mon, Aug 24, 2009 at 1:05 PM, Erik Stielstra<info@erikstielstra.nl> wrote:
Ok the Dutch team also joined the server. These were the first steps, lets continue...
I like to get a small group working on Dutch translation at l.d.o. We can work on existing translations, but will existing translations automatically be imported from CVS?
No automated import from CVS will take place. We cannot tell whether teams have more up to date translations on a translation server or in CVS, or wherever else. This is up to individual teams to figure out.
And would it conflict if we would move some translations over already?
It should not cause any conflict. Now that you have the team set up, you can move translations from CVS and/or your translation server.
When a project translation is completed is the (current) workflow to export it and commit it into CVS?
Yes, this is the current workflow.
Is my understanding correctly that translations will, in due time, be removed from CVS?
More precisely, I'd say that .po and .pot files will not be allowed to be committed to CVS. The old files will be kept for posterity (and will be kept in the unchanged older packages as well of course). New Drupal.org generated project packages will not include translations, but translations will be packaged separately on localize.drupal.org. Whether this will be on trigger from the translation teams or automated time-to-time is not yet figured out. We'll have a Drupal 6 & 7 module to automatically download and update translations on Drupal installations from these packages to make users' life simpler. This is the plan. Gábor
Hello, I've also joined http://localize.drupal.org with user: claudiu.cristea for Romanian translation team and I've sent an issue ticket ( http://drupal.org/node/557974). We have not a previous translation server... Thank you, Claudiu C. On Sat, Aug 15, 2009 at 8:26 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Dear Gabor, We have applied for CVS account and we are interested to try out the new localization server for Mongolian translation but none seems to open a CVS account for us can you please help us. thanks, batpurev On Mon, Aug 24, 2009 at 10:02 PM, Claudiu Cristea<clau.cristea@gmail.com> wrote:
Hello,
I've also joined http://localize.drupal.org with user: claudiu.cristea for Romanian translation team and I've sent an issue ticket (http://drupal.org/node/557974). We have not a previous translation server...
Thank you, Claudiu C.
On Sat, Aug 15, 2009 at 8:26 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
batpurev, You don't need a CVS account for the new localization server. I don't know the expected time schedule for the new 'module to automatically download and update translations', but with a little luck you can do without a CVS account at all. To try the localization server follow the instruction given by Gabor in previous mails on this list. Erik Stielstra On 25 aug 2009, at 06:56, B.Batpurev wrote:
Dear Gabor,
We have applied for CVS account and we are interested to try out the new localization server for Mongolian translation but none seems to open a CVS account for us can you please help us.
thanks, batpurev
On Mon, Aug 24, 2009 at 10:02 PM, Claudiu Cristea<clau.cristea@gmail.com
wrote: Hello,
I've also joined http://localize.drupal.org with user: claudiu.cristea for Romanian translation team and I've sent an issue ticket (http://drupal.org/node/557974). We have not a previous translation server...
Thank you, Claudiu C.
On Sat, Aug 15, 2009 at 8:26 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hi, translators and translation supporters. Is there something we can do to help get Latvian translation on localize.drupal.org? Issue here: http://drupal.org/node/576728 Thanks for all your great work. Mik (mike-green) On 2009.15.8, at 20:26, Gábor Hojtsy wrote:
Hey,
Localize.drupal.org (or localise.drupal.org) is becoming real! :) A central setup of the localization server project (which is already used by some of the translation teams) is alive on localize.drupal.org. It was running in a catch-up / testing mode this past weeks to parse up recent Drupal project releases. It currently
- knows about 4886 projects - parsed up 5274 (0 in queue and parsing new releases as they are available on d.o) - 37943 files scanned - which results in 145646 strings to translate
That is a huge amount of strings to translate but the UI allows you to focus on distinct projects even on distinct releases. Only projects with stable releases are parsed, but these 5274 projects include at least one stable release from the end of each branch of each project.
The localize.drupal.org site works in a single-sign-on system with drupal.org, in which it is also pioneering new functionality on drupal.org. That was also tested in recent weeks, and we worked out solutions to some bugs, but there might be others lingering still. Good news it that you don't need to register on the site to use it, but will get redirected to drupal.org for login and get logged in on localize.drupal.org too.
A wider announcement is expected later, but before getting a flood on us, it would be good to try and migrate a team or two to this platform and see how it works. We can either migrate teams from the drupal.org CVS based commit workflow or from another localization server. There should be no duplication in teams however, so unless there is dedication from the team to move to localize.drupal.org, we will not migrate a team. Advantages to be here include:
- all releases of projects parsed, backups solved, so no need to manage all that within your team - central packaging and distribution will be implemented from here (not yet implemented), so sites will get translations from here easily - single sign-on with drupal.org - if you are still using the CVS workflow, this is far superior in many ways
If your team would like to be among the first to migrate, let me know.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
participants (13)
-
Abhishek Nagar -
Amr Gharbeia -
B.Batpurev -
Claudiu Cristea -
Erik Stielstra -
Fabiano Sant'Ana -
Fernando P. García -
Gerhard Killesreiter -
Gábor Hojtsy -
Hannes Lilljequist -
Hilde Austlid -
Miķelis Zaļais -
Veeven (వీవెన్)