Jakub Vrana wrote:
Livedocs handle this pretty well IMHO. It shows the translation and
then: "The translation of this file is outdated. Click here to read
this file in english."
Sean has of course a good point. Just because the revision indicates the
file wasn't updated in a while the file is not neccessarily outdated,
when there were only minor changes. I admit that. So livedocs isn't
saying the truth in each case either. But giving the user a link to the
original and let himself decide whether he prefers the more current
English original is a good idea anyways. But I don't think that can be
accomplished in the regular build process, can it?
Maybe the metrics could be changed from "difference in revision numbers,
file size or age" to "number of changed lines in original" to address
the issue of checking for the document's status?
SO, my solution is to add an entity that says something along the lines
of "This documentation is critically outdated; see the English
translation." And have a revcheck-like script determine which files are
POTENTIALLY outdated. Then, a user can stick ¬e.outdated; into any
files that he has personally reviewed and considers out of date.
That's not going to work. If there's a lack of translators then there
will be also lack of note-stickers.
Full ACK. That's why I prefer the automation in the build process or the
way livedocs is handling it.
Olli
