On Jun 20, 2012, at 8:49 AM, Hannes Magnusson wrote: > On Wed, Jun 20, 2012 at 4:29 PM, Ferenc Kovacs <tyr...@gmail.com> wrote: >> >> >> On Wed, Jun 20, 2012 at 4:38 PM, Philip Olson <phi...@roshambo.org> wrote: >>> >>> Hello Hannes, >>> >>> I think we should disable this email (i.e., broken translation >>> notifications) >>> from being sent to phpdoc@, and only send 'en' here. >>> >>> Regards, >>> Philip >> >> >> Supposing that you read http://news.php.net/php.doc/969383877 back then I'm >> guessing that you think that the translations are failing more frequently by >> the translators fault than by the changes/issues in the english >> documentation. >> If that's true and having some translation failing is a frequent situation >> instead of a rare exception, I would agree removing these notifications from >> the general doc mailing list. >> It would be still nice if somebody could keep an eye on the failing builds >> and if a translation is not fixed in 2-4 weeks (I'm a "little" bit generous >> here) it should be removed from the active languages until it is fixed. >> What do you think? >> > > > We used to have a rule: You break translation, you fix it. > That and if noone is paying attention to the translation then we will > be sending email to the list for ever and ever, without anyone caring > - creating an annoying situation for anyone who wants to join the > translation and wasting precious resources building it endlessly.
I don't think notifying the documentation discussion list with build failure emails for all languages is working, and instead it makes me want to either leave this list or ignore it. I suspect it has this affect on others too. Most of the time, a translation is broken because of changes to en/. This happens over 90% of the time. However, this is a flaw in our XML<->XML system and I doubt English authors should be expected to edit every translation as often the quick fix is inserting English into the translation. I've done that and feel slightly guilty while doing so. The real fix is translating the new text. Of course, sometimes it's a markup change that breaks a translation… Or maybe we'll move to PO+gettext… ;) I've disabled this email for now. I did it blindly and with the bad habit of editing scripts on the server instead of in the VCS. It'll probably be overwritten. Also, how is this managed on euk2 now? The recent migration has moved away from /etc/crontab so please let me know. I'll then edit the proper files in the VCS in the future. :) If the above change feels wrong then please speak up, but I think the reasons make sense. I usually visit the following each week or so, and try to fix the translations. It's not a perfect system but it works most of the time: http://docs.php.net/download-docs.php?sizes=1 Today it shows that one translation (kr) is outdated by a day. I tried fixing it but finding errors (especially when --disable-segfault-error is required) is not always easy, and it feels especially difficult today. :( Regards, Philip
