Also,
I fell that, the documentation about localization is too vague, incomplete and scattered.
I propose a clear documentation regarding localization.
And also, centralized localization server (inside drupal.org) is must if we want to get more contributions. Now, it is pain in the ass to start a localization project and create a working release.
-Shankar
On Mon, Jul 20, 2009 at 12:53 PM, Gerhard Killesreitergerhard@killesreiter.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jakub@rtfm.cz schrieb:
In Spanish I see that problem all days, there is not a clear way to contribute, or at least people don't see it as serious, sustainable or
Agreed.
perhaps viable (is still a pain in the neck). We need to translate core, we also have to spend a lot of time maintaining translation servers. There are A LOT of translations servers, can't we just join forces to maintain a big one and let translators do their job?
Check drupal.org/project/l10n_server issue queue, there are still issues that need to be solved, mainly the performance ones, some of them waiting for a review for months!
That is unfortunate, feel free to ping me about reviews for any such issues any time.
I really want to get this deployed before DrupalCon Paris.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkpkF9YACgkQfg6TFvELooRzRgCgyGjb/ojX1oshWOoSIXuvDru7 BqEAn2H1B7q7mzv77+1XALdGqRE/txa1 =6xsB -----END PGP SIGNATURE----- _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations