2016-11-15 23:22 GMT+01:00 André Malo <n...@perlig.de>: > * Luca Toscano wrote: > > > 2016-10-23 12:55 GMT+02:00 Luca Toscano <toscano.l...@gmail.com>: > > > 2016-10-20 21:46 GMT+02:00 Mads Toftum <m...@toftum.dk>: > > >> On Thu, Oct 20, 2016 at 09:36:51PM +0200, André Malo wrote: > > >> > * 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. > > >> > > >> Sounds like a much better solution. > > > > > > I'd be +1 only if there is a clean way to mark these files as > > > "old/stale/out-of-sync", together with a clean statement/note somewhere > > > about what to do with them in the medium longer term (even in a page > > > like https://httpd.apache.org/docs-project/). > > > > Bump :) > > > > Can we move forward removing some old and outdated documentations from > > the docs? > > Sure. Is there a consensus about how? >
Only ideas.. For example, we could start from http://home.apache.org/~takashi/translation-status/test.html#2.4: there are a lot of languages that are out of sync, we should just not publish them anymore in my opinion. WDYT? Luca
