Corrupted file at Lightning Source

 Last night, I checked into the customer area on the Lightning Source website to check the status of my uploaded files for The Horsepower Whisperer and The Wormton Lamb. The proof was ready for The Wormton Lamb but today I had a message from my customer rep to tell me that the text file for The Horsepower Whisperer was corrupted on pages 5 and 6. These pages are the ones that feature the maps at the beginning of my books. They consist of layered drawings and if any part of the pdf was likely to become corrupt this was it. However, all my files at home look okay so I can only assume that the CD that went to Lightning Source in the states was damaged in some way.


I would've uploaded a new file for The Horsepower Whisperer and ordered a proof for The Wormton Lamb tonight but the Lightning Source website is being maintained at the moment.

I regenerated a text file pdf for The Horsepower Whisperer just to make sure there were no problems but notice something odd in the process. Each text block must be divisible by four. It's something to do with Lightning Source's printing processes. Checking my new pdf for The Horsepower Whisperer in Adobe Reader for my text block file came to 423 pages whereas before it was 424

To cut a long story short, I noticed that the Open Office Writer file featured a jump in page numbers close to the end of the block. It seemed to be related to a changing header format. Deleting any page breaks removed the jump in page numbers but also caused the header format to flow from the text right to the end of the document where I really wanted completely blank pages without any header or footer.

In the end, I got around this problem by adding a new page to the Open Office Writer file. When I exported this, the resulting pdf had the correct page count.

I have an open mind about what causes this. The Open Office Writer software that I am now using is a later version than the ones I used to generate my original textblock files. I believe this is causing formatting changes and I'm optimistic that if I was generating a textblock from scratch again, then none of these problems would arise. It does show, though, that generating the pdf for uploading onto Lightning Source's system is the trickiest interface of all between what I'm doing and what the printer needs.

Tomorrow, when the Lightning Source site is available again after maintenance, I'll have another go at uploading my text block. This didn't work before because I was uploading a revised text block as well as the new cover file. With just the text block to upload, there shouldn't be any problems with file size.

Needless to say, both for cover files that Becky produced have been accepted without any problems.