Re: Critical files in translation
| From: | Friedhelm Betz | Date: | Wed, 05 Oct 2005 16:49:29 +0000 |
| Subject: | Re: Critical files in translation | ||
| References: | 1 2 3 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969370465@lists.php.net to get a copy of this message | ||
Jakub Vrana wrote:
Sean Coates wrote:Thats nice, but does not solve any problems in the near future.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."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. ;)
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 ;-) FriedhelmSO, 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.