simos / gnome-i18n-manage-vcs Goto Github PK

We would iterate selected modules and create localised XML source files for language.
Then, generate HTML (using xsltproc), PDF (using db2latex) for each module.

We currently can identify if a PO file from dir_po/ is newer than a startdate.
We should be able to commit those PO files.

Issues that remain:

1. Do we commit to master only? How do we identify whether to commit to branch?
2. Is master the main branch for all modules? We depend on RSS feed from l10n.gnome.org for this; currently we assume master is 'master'.

Leonardo: «Hi there, I have a feature request. Take this situation: after cloning the GNOME 2.26 repositories, I had GTK+ with branch master. But today the correct branch would be gtk-2-16. So, when I ran "gnome-i18n-manage-vcs vcsmanage --update-vcs", it should switch to the gtk-2-16 branch automatically (but it didn't).»

We iterate selected modules and produce an HTML document which lists

1. original (English) figure
2. localised figure (if available)
   next to each other.

See
http://simos.info/pub/figures_scan-perl.txt
for relevant Perl script.

See http://simos.info/pub/gnome-2-26-figures.html for relevant generated HTML file.