We've been developing some tools to help administer, maintain and package translations. These are the ones that are running on https://translate.openatrium.com

Better than posting a patch I'm linking our public svn sandbox (they are still under development). The stuff is here: https://svn3.cvsdude.com/devseed/sandbox/drupal-6/l10n_tools/

This pack has these 3 modules:

- l10n_download: creates download packages
- l10n_server_tools: faster approval page and some clean up operations
- l10n_project: provides a projects and releases admin page, for allowing some bulk operations (these are defined by the other two modules)

Some parts need some serious testing (like the project and release bulk operations). However I'd like them to be considered for inclusion in the l10n_server and also get feedback about the features. (Also make them available for everybody to give them a try)

CommentFileSizeAuthor
#4 l10n_tools.zip22.81 KBpsicomante
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

psicomante’s picture

+1 ;) though it should integrated in the main gui

Gábor Hojtsy’s picture

Did not yet have time to look into these, but will surely do soon.

Gábor Hojtsy’s picture

At the moment, the given link gets me: "Could not open the requested SVN filesystem"

psicomante’s picture

FileSize
22.81 KB

zip file saved ;)

Gábor Hojtsy’s picture

Well, I'd assume they work on these modules, so I'd love to see the current code. Jose?

Jose Reyero’s picture

Status: Active » Postponed

Well, it seems in the meanwhile the svn repo has changed and anyway the modules are not up to date with latest l10n server developments.

I'll see about posting an updated version when I find the time.

Gábor Hojtsy’s picture

I don't think the database changed significantly. There are some batch operations in the drupal.org project integration module (which unfortunately was also named l10n_project due to how it integrates with project module data, so you might want to rename your module before updating to the latest l10n_server to avoid name conflicts).

I'll be most interested in the (mass) suggestion approval UI for localize.drupal.org at first by the way. Looked at the source code and it seemed pretty extensive (== lots of code and levels of abstraction which calls for a reasonable time devotion to actually understand and integrated). I'd love to integrate a better suggestion approval UI in l10n_server as a first step of integrating your improvements.

Pasqualle’s picture

the new link to svn sandbox:
https://devseed.svn.cvsdude.com/sandbox/drupal-6/l10n_tools/

but I guess the code is still the same..

Jose Reyero’s picture

Title: Tools modules (Consider for inclusion) » Tools modules (may have some reusable stuff)
Status: Postponed » Active

Yes, the link by Pasqualle is the right one. I've just posted updated modules there. However it seems I'm already late for the language list.

Mine was a quick update, there are some weird module dependencies so at this point I'm not asking anymore for they to be consdered for inclusion, just posting in case some stuff could be reusable, specifically:

* The l10n_server_tools module (which adds some bulk moderation pages).
* The l10n_tools module, which adds some batch capacity to the project and release list (then modules define operations to be applied to selected projects/releases).
* Some packaging logic in l10n_downloads module, which keeps tracks of releases, languages, and files to keep everything up to date and clean (the files/releases cleanup is not working yet though)

For the client side of all this, just in case something could be reused we've got this module here which is modelled after Drupal core update module, and also extends the parser for things like the language list.

http://github.com/developmentseed/Atrium/tree/f568ec4509b7485a54be05e889...

Anyway, we'll try to keep up with the packager module and latest changes, I hope I can post some more useful stuff in a few days.

Gábor Hojtsy’s picture

Yeah, the bulk moderation is something many teams came up to me to request :) So it would indeed be good to refine and include.

Gábor Hojtsy’s picture

Assigned: Unassigned » Gábor Hojtsy

I've started the work to integrate the suggestion moderations screen.

Gábor Hojtsy’s picture

Status: Active » Postponed

Worked a **lot** on this over the weekend and submitted a patch which adds in the moderation functionality and unifies filters at #570648: Add mass moderations screen for suggestions (+ user filtering). Please help review that and get that in! I'm postponing this one on that, so we can reopen for other stuff, when that is committed.

Gábor Hojtsy’s picture

Status: Postponed » Active

After the weekend, I've worked a **lot** again :) but now on test coverage for the module. Results are in CVS and in patch forms as I've stepped through the items I've been adding tests for at #560132: Write tests. Good news is that I wrote all the tests on a system with #570648: Add mass moderations screen for suggestions (+ user filtering) applied. (And it's suggestion listing screens and the new 'limit' functionality even made it easier to test the suggestion and parsing functionality). So given that I've arrived at an acceptable testing coverage for the new functionality (and found its bugs), I went ahead and committed #570648: Add mass moderations screen for suggestions (+ user filtering). So that means a huge chunk of your l10n_server_tools module is now in the base module. Plus it also resulted in a unified filtering UI (user and limit filtering options added to the existing screens too).

I'd love to see how this works on the live site, so will hold off on other big changes from here to the UI. The packaging code however will be more then interesting to work out. We've recently added a compact export option to l10n_server (fallout of #568994: Implement translation package export in l10n_packager), so that we can build .po files as small as possible. The plan is to use that compact mode, so we put as few burdens on the server as possible.

Gábor Hojtsy’s picture

Agreed these modules still have very useful bits to them, and we should keep looking at them when refactoring our code.

SebCorbin’s picture

Issue summary: View changes
Status: Active » Closed (fixed)

Closing this, had a look at the code, and I think we have most the features in the 7.x branch