Good Day Didn`t found it in docs (may be bad looking 8( ) When I commited translations into per module translations directory for all possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no access)) - are there any automation script for integrating those translations into module releases?Or this process only human based and I have to post issues to all translated modules for getting access to modules CVS or pinging module developers for including translations into feature releases?
Please, help to understand, cause I do very big work and want to do it fast and without errors
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andriy Podanenko schrieb:
Hi Andriy!
Didn`t found it in docs (may be bad looking 8( )
When I commited translations into per module translations directory for all possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no access)) - are there any automation script for integrating those translations into module releases?Or this process only human based and I have to post issues to all translated modules for getting access to modules CVS or pinging module developers for including translations into feature releases?
You translations will only be integrated into future releases. You need to commit the translation to the branch the module author is working on, say DRUPAL-6--1, and the next time the author will create a tag on that branch and make a release on that tag, your translations will be included.
Cheers,
Gerhard
Thanks a lot. Got it
2009/5/21 Gerhard Killesreiter gerhard@killesreiter.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andriy Podanenko schrieb:
Hi Andriy!
Didn`t found it in docs (may be bad looking 8( )
When I commited translations into per module translations directory for
all
possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no access)) - are there any automation script for integrating those translations into module releases?Or this process only human based and I have to post issues to all translated modules for getting access to
modules
CVS or pinging module developers for including translations into feature releases?
You translations will only be integrated into future releases. You need to commit the translation to the branch the module author is working on, say DRUPAL-6--1, and the next time the author will create a tag on that branch and make a release on that tag, your translations will be included.
Cheers,
Gerhard-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoVOsAACgkQfg6TFvELooSPuACfUIuvm39np4TvvVgly6K2mnsF QjAAniD3MsogKtICGWZ2l6jpDQ9K8rvc =laII -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Dear All,
Does anyone know how much of work involved in localization of Drupal? How many strings/words are there for translation?
thanks, Batpurev
On Thu, May 21, 2009 at 7:31 PM, Andriy Podanenko podarokua@gmail.com wrote:
Thanks a lot. Got it
2009/5/21 Gerhard Killesreiter gerhard@killesreiter.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andriy Podanenko schrieb:
Hi Andriy!
Didn`t found it in docs (may be bad looking 8( )
When I commited translations into per module translations directory for all possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no access)) - are there any automation script for integrating those translations into module releases?Or this process only human based and I have to post issues to all translated modules for getting access to modules CVS or pinging module developers for including translations into feature releases?
You translations will only be integrated into future releases. You need to commit the translation to the branch the module author is working on, say DRUPAL-6--1, and the next time the author will create a tag on that branch and make a release on that tag, your translations will be included.
Cheers,
Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoVOsAACgkQfg6TFvELooSPuACfUIuvm39np4TvvVgly6K2mnsF QjAAniD3MsogKtICGWZ2l6jpDQ9K8rvc =laII -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Andriy Podanenko podarok@ own blog: http://my.ukrweb.info/blog homepage: http://podanenko.com twitter: http://twitter.com/podarok LinkedIn: http://www.linkedin.com/in/podarok WM Z335493205060
translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
4000-20000 stringsdepending of modules
2009/5/22 B.Batpurev batpurev@gmail.com
Dear All,
Does anyone know how much of work involved in localization of Drupal? How many strings/words are there for translation?
thanks, Batpurev
On Thu, May 21, 2009 at 7:31 PM, Andriy Podanenko podarokua@gmail.com wrote:
Thanks a lot. Got it
2009/5/21 Gerhard Killesreiter gerhard@killesreiter.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andriy Podanenko schrieb:
Hi Andriy!
Didn`t found it in docs (may be bad looking 8( )
When I commited translations into per module translations directory
for
all possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no access)) - are there any automation script for integrating those translations into module releases?Or this process only human based and
I
have to post issues to all translated modules for getting access to modules CVS or pinging module developers for including translations into
feature
releases?
You translations will only be integrated into future releases. You need to commit the translation to the branch the module author is working on, say DRUPAL-6--1, and the next time the author will create a tag on that branch and make a release on that tag, your translations will be included.
Cheers,
Gerhard-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoVOsAACgkQfg6TFvELooSPuACfUIuvm39np4TvvVgly6K2mnsF QjAAniD3MsogKtICGWZ2l6jpDQ9K8rvc =laII -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-- Andriy Podanenko podarok@ own blog: http://my.ukrweb.info/blog homepage: http://podanenko.com twitter: http://twitter.com/podarok LinkedIn: http://www.linkedin.com/in/podarok WM Z335493205060
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
-
Andriy Podanenko -
B.Batpurev -
Gerhard Killesreiter