[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Next GNUN release
From: |
Ineiev |
Subject: |
Re: Next GNUN release |
Date: |
Wed, 14 May 2014 13:18:25 +0000 |
Hello, Thérèse!
On 05/14/2014 07:51 AM, Thérèse Godefroy wrote:
- Why don't outdated.html and top-addendum.html use the same variables?
For historical reasons.
- Why does GNUN have to renew the out-of-date notice of translations
which already have one when the original page changes?
This seemed the most straightforward implementation.
- If the notice has to be renewed every time, why not delete each
SSI of the old notice separately, rather than the whole set. This
would take 5 commands instead of just one or 2, but there would be
more flexibility.
I don't think such flexibility would be really useful, but it would make
the program more complicated (and dependent on all historically injected
variables).
- Is there going to be a test for OUTDATED_SINCE (or another variable)
in top-addendum.html, to disable the translation disclaimer when there
is an out-of-date notice ?
Yes.
- If and when this test is implemented, are the already-outdated pages
going to be regenerated to take advantage of it?
They won't need regenerating because the change will only be
in the template.
Thank you!
- Next GNUN release, Thérèse Godefroy, 2014/05/14
- Re: Next GNUN release,
Ineiev <=
- Re: Next GNUN release, Thérèse Godefroy, 2014/05/14
- Re: Next GNUN release, Ineiev, 2014/05/15
- Re: Next GNUN release, Thérèse Godefroy, 2014/05/15
- Re: Next GNUN release, Ineiev, 2014/05/16
- Re: Next GNUN release, Thérèse Godefroy, 2014/05/16
Next GNUN release, Thérèse Godefroy, 2014/05/14