The page "Handbook page about the localization server is way out of date and needs to be updated.

I had half a thought about doing it myself, but I have no idea what some of it means. Some of it, such as "admin/l10n_server/l10n_localpacks", simply doesn't exist anymore.

I marked this is a version 7 issue because was required to specify some version, but it's out of date for version 6, too.

Comments

baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented
Assigned: Unassigned » baluertl
Issue summary: View changes

As it seems I'll continuously have dozen of hours freetime during the upcoming weeks, I'd be happy to compose a draft for later supervising by more experienced colleagues like Gábor Hojtsy, SebCorbin, zirvap and the others.

SebCorbin’s picture

SebCorbin commented

That would be really nice to have documentation written by someone a bit external, it would be so much clearer.

As a starting point you can use this big picture depicted at http://makina-corpus.com/blog/metier/the-state-of-localize-drupal-org-in...

  1. When a developer releases a new version of a module, a tar.gz file is automatically generated on drupal.org
  2. Localize then watch for these new releases and pulls these tar.gz files regularly
  3. It decompresses these files, and run them through the Drupal translation extractor to generate a .po template file with sources string
  4. With the translation interface, localize users put a translation in front of each source string
  5. Periodically, localize generates the complete .po files with source strings and associated translated strings
  6. These .po files are then available to download either manually or automatically (using l10n_update module)

There is also some documentation about localize at https://drupal.org/contribute/translations that may be useful to you

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

There is also http://hojtsy.hu/blog/2010-may-05/using-drupal-collaborative-software-tr... which is maybe a bit outdated but not that much :) Can be used as a starting point. Also now that the drupal.org data pulling is fully from public sources, theoretically anybody can set up an automated copy of the localize.drupal.org functionality, it would just take way too long to pull all the tens of thousands of releases. We may need a setting in the module to limit that somehow for testing. So let's talk when / before you get there in the docs.