>>Run a 'make test' on the German manual. If it runs fine, and you see >>quite a lot of changes needing attention, bug Derick to build the German >>translation. If you are unhappy with this situation, try livedocs. > > Hello Gabor, > that's exactly my point. I don't need to check them for myself and I > don't translate them because I need them in German. I have livedocs > running on my local box to test it. If I couldn't read the english > originals, I wouldn't have translated them ;) > Why do we need to manually do this (especially mail Derick about it, and > then mail again multiple times if it didn't work like this time). This > has been like this since I started, always behind - my main question > was, why that isn't automated, when, say 10 commits have been made or 2 > weeks are gone?
- Doing failed builds are enough burden for the building machine. - Doing a new build needs to rebuild the whole manual, regardless of the number of pages changed (10 is a drop in the ocean if you consider the thousands of pages in the manual) - Pushing up the new files to the rsync server, all are going to have new creation dates associated with them, meaning that the rsync processes will not know right away, that files are not changed, so the whole build needs to be checked for changes, when mirrors (including php.net) get the new files, resulting in increased traffic and load on the rsync server (consider the 120 official, and countless unofficial mirrors) - Last but not least this works this way, because unfortunately those who complain about this system rarely end up improving/fixing/submitting bugs and patches against livedocs, so that we can get out of this situation. Goba
