WIP: Use sidecar files for identifying outdated translations #974
Sans évaluateur
Labels
Sans labels
bug
build
cgi Scripting
design
disruptive
documentation
duplicate
easy
feature-request
help wanted
javascript
priority/low
question
system-hackers
tagging
text
translations
wait/bugfix
wait/inprogress
wait/misc
wait/proofread
wontfix
xsl
Sans jalon
Sans assignation
3 participants
Notifications
Échéance
Aucune échéance n'a été définie.
Dépendances
Aucune dépendance définie.
Référence : FSFE/fsfe-website#974
Chargement…
Référencer dans un nouveau ticket
Sans contenu.
Supprimer la branche "(supprimé) : fix#64_2"
La suppression d’une branche est permanente. Bien qu’une branche supprimée puisse temporairement subsister, elle NE PEUT PAS être facilement restaurée. Continuer ?
Alternative ansatz to fix #64.
Interesting!
A script checking for outdated translations already exists, perhaps you can use or expand it instead of creating a script with the same focus? check-translation-status.sh
A command to output all languages which are outdated against their english original: check-translation-status.sh -f <any_file> -o out
The idea is interesting, but I see two downsides:
However, I have some idea how to improve this concept which I will describe in issue #64.
Good point! Fixed in
9d24d36061
I didn't notice that script. On my machine, doing
takes approx. 12 minutes (with lots of "date: ungültiges Datum „@“" messages).
Generating the sidecar files takes approx. 5 minutes on my box (which is roughly the extra time a full build takes with #974.) Once the sidecar files are generated, you can do
and get all outdated files no (almost) no time.
Closing per discussion in #837
Demande d’ajout fermée