Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
in the packaging script for the new release system (http://drupal.org/node/88056) we don't currently handle translation status at all. see especially http://drupal.org/node/88056#comment-144641.
we need to get this working again fairly soon. what killes and i had previously discussed was:
- store that info in the DB, not a flat file
- add a simple little project_translation_stats.module that displays the info from the DB into a human-readable table at some fixed menu location
of course, we also have to modify the packaging script (modules/project/release/package-release-nodes.php on DRUPAL-4-7--2 branch) to compute the status and store the data...
i can certainly help with the packaging script side. anyone care to work on project_translation_stats.module? ;)
Comments
Comment #1
dwwfor the record, here's the page i'm talking about that the project_translation_status.module would have to generate:
http://drupal.org/node/13236
Comment #2
Gábor HojtsyWhat is the code used to generate the stats page now? That should be used as a start I guess.
Comment #3
dwwi don't know, i don't have php filter rights on d.o...
Comment #4
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedthe Drupal page node only includes a textfile which is generated by the packaging script using gettext tools. I think I'd like to keep it that way since a module woudl have to run a lot of code through shell commands.
Comment #5
dwwto clarify, the original design was:
is there anything wrong with that approach? i don't think so...
-derek
Comment #6
Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commentedI am ok with this approach. We only need to find out how to proceed with existing tarballs.
Comment #7
Gábor HojtsyMy SoC project moves this functionality to the localization server, so this gets fixed elsewhere. Closing.