On Thu, Sep 03, 2020 at 01:41:11PM +0200, jean-baptiste(a)holcroft.fr wrote:
> I suppose 4 weeks was too long for a string freeze. I personally though: ok, i have time to take care of this and forgot.
> You may have said a few days or a week, my reaction may have been: let's fix this now so i don't miss it.
Hello, thanks for your feedback.
Next time, I'll delay the release by one week only.
La moitié des chercheurs passe son temps à remplir des demandes que
l’autre moitié perd beaucoup de temps à lire. -- André Brahic
The Uyuni documentation is written in AsciiDoc with the Antora
toolchain. Since no translation tool supports AsciiDoc, I am
converting AsciiDoc to gettext .pot files with po4a-gettextize.
When there are changes in the AsciiDoc files, to update the .pot files
I am re-running po4a-gettextize on all the AsciiDoc files (using a
script ). Even if the original AsciiDoc has not changed,
po4a-gettextize will which regenerates the file, with a new
POT-Creation-Date. Since I have 500+ .pot files the git repository
(and 2 languages), this is a massive (1,500+ files ) commit, even
when only one single AsciiDoc file has added/change one string.
Is it possible to somehow tell po4a-gettextize to not update the
POT-Creation-Date attribute (or even better: to not create it at all,
as Sphinx does ) ?
Pau Garcia Quiles
as promised, I just released v0.61, that is mostly a hot fix for a
bug. The full changelog and tarball are available at the usual location:
Many thanks to all translators that updated their work so quickly
after my recent mail. Sorry for the ones I didn't wait for. I plan to
do a translation-only release in 4 weeks, on September 2.
If you can’t open it, you don’t own it.