Oliver Albers wrote:
Critical files are files with too old revisions. So this status can be
used as an indication for the translated file being outdated, though
it's no proof. But IMO the indication a file _might_ be outdated is
enough to consider it outdated. My idea was to skip each file with a
critical status and build the original English version of it instead of
the translated one, as it is done with files missing in a translation.
At least if that is feasible to implement in the build process.
AFAIK, since documentation describes PHP, critical changes in the
documentation are related to critical changes in the PHP itself. For
example, changing the way some function or class works, e.g. changing
the returning value of array_search() on failure after version 4.2.0
from NULL to FALSE. It is just one word, but it's an important change -
so relying on the volume of changes is not good enough approach. In this
particular case there's a note describing the change, so wouldn't it be
enough just to have some tag saying this?
I mean to have something like:
<!-- Critical-Change-Revision: x.xx -->
and if the EN-Revision pseudo-tag in translated file is less than this
version, to show the original english file, or a pale blue dot warning,
or whatever...:)
--
Kouber Saparev
http://kouber.saparev.com
