WIP: Use sidecar files for identifying outdated translations #974
No hay revisores
Etiquetas
Sin etiquetas
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
Sin Milestone
No asignados
3 participantes
Notificaciones
Fecha de vencimiento
Sin fecha de vencimiento.
Dependencias
No se han establecido dependencias.
Referencia: FSFE/fsfe-website#974
Cargando…
Referencia en una nueva incidencia
No se ha proporcionado una descripción.
Eliminar rama "(eliminado):fix#64_2 "
Eliminar una rama es permanente. Aunque la rama eliminada puede continuar existiendo durante un corto tiempo antes de que sea eliminada, en la mayoría de los casos NO PUEDE deshacerse. ¿Continuar?
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
Se cerró la solicitud de incorporación