Jakub Vrana wrote:
Sean Coates wrote:
I just had a short discussion with Sean about "critical" files in
translations of the manual and he suggested I'd bother all of you with
the issue. ;)
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."
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.
Jakub Vrana
How about adding a link to such a feature just like we have with notes.
Then if there're enough people who complained about the documentation of
that page not being in-sync, a note is sent to the translator's
mailinglist, and if they don't respond, it would automatically be marked
as such. If you also add a link in that mail for contributors to click,
which automatically removes the entire "outdated" queue for that file...
that should make sure it isn't abused too much.
But that's just an idea..
- tul