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."
Thats nice, but does not solve any problems in the near future.
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.
Thats a valid concern, but we loose nothing, we just can gain something.
This gives at least the possibility to act if some of the translators
want to do. If they want to do something, we give them the possibility.
Thats better than nothing ;-)
Friedhelm