* Rich Bowen wrote:
> * We have translations that are grossly out of date. We should drop > them. It remains only to define what "tool old" means? If a translation > hasn't been touched since 2.4.0, I would recommend dropping it. > Discussion? Guilty... However, I think, it would be waste to throw them away. I'm proposing a "do not transform (and remove html) until current" solution instead. I can also take a look at the build system to make that happen. > * It also occurs to me that we should make specific recommendations of > which docs should be translated first. For example, I think that the > "Getting Started" doc, and the "HowTo" docs, would be good places to > start, while the module docs, being more about technical detail and > having a less conversational style, would come later. Hmm. People have itches to scratch. If at all, it should be a very weak recommendation. > * All of this hinges on actually getting translators. It *seems* that > this used to be easier, but lately we have really stunk at attracting > new translators. I think that this might be because our review process > is so rigorous, and it's hard to find reviewers. Maybe, maybe not. I think, the project itself lost traction in terms of contributions (from non-developers). It's not that cool anymore (or the hot shit, take your pick). nd -- "Das Verhalten von Gates hatte mir bewiesen, dass ich auf ihn und seine beiden Gefährten nicht zu zählen brauchte" -- Karl May, "Winnetou III" Im Westen was neues: <http://pub.perlig.de/books.html#apache2> --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org For additional commands, e-mail: docs-h...@httpd.apache.org
