> 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. ;)
Yeah, audience is too small on #phpdoc. > I'd be glad to hear your opinion on this. So, I think that falling back to English when a document is "critically outdated" is a good idea. HOWEVER, I'm opposed to a script trying to determine that a revision is too old. For example: if I fix 100 typos in an English file, that doesn't mean that (e.g.) the German version of the same file is out of date (in fact, it probably isn't, because it's likely that the translator wouldn't have introduced the same typos during the translation. 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. But I also welcome opinions. (-: S
