>> >> Hello everyone, >> >> A few people have tried to solve our CHM build problem but without success. >> This is a call to anyone who knows much about the topic, and is willing to >> share insight into solving this problem. >> >> Currently only en/ ja/ and tr/ CHM files build with success, whereas all the >> others end up as broken builds. The simplest way to determine if a build is >> broken (aside from opening the file) is to look at its size. Broken builds >> are currently ~15Kb or ~2000Kb whereas successful builds are closer to >> 11000Kb.
> hi, > > As I told you on IRC earlier this week, the problem is fixed and > everything is back online. But the problem I spoke about here is with the broken CHM files, which is certainly not fixed. > The script works as expected and the configuration on the server is > fixed. I will update the wiki to document how to do it as soon as > possible. I added a file size check yesterday, which will hopefully end the ability to overwrite good CHM files with broken ones (which it ended up doing a couple of days ago). At least, it should help. > Looks to me as there are some encoding issues in there. The CHM are > invalid, only incomplete or badly encoded. I will take a look at the > non English version once I'm back at real work (June 10/11th ~). Cool. Maybe someone else will fix it by then, but in the meantime I'm hopeful someone will remove all of these bogus CHM files from the rsync box, so php.net mirrors will stop hosting them. Hannes? Regards, Philip
