Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm sending you a note via email, but…how close to print-ready are the PDFs that are generated? My wife has been working on a novel (and 90%) of a sequel that we're getting ready to self-publish through Lulu and KDP and I'm tired from the formatting hoops.

We're using Ulysses (similar to Scrivener) and exporting to Word and importing to Pages (because the epub export was somewhat disappointing compared to the Pages epub export, and Pages layout tools are more powerful than Word's) because we need both epub and 6"x9" (US trade) print-ready PDF. She's got a cover and a back cover. She wants to have both ebook and hardcopy, and you guys don't offer hardcopy.

I don't have the time to write the software I would need to prepare this stuff myself—and I don't know that I want to learn all the standards that I'd need for it, either. If your PDFs are print-ready or I can somehow specify the size so that it can be print-ready, I'd happily pay to convert her novel—because this is just one of four books that we're going to have to do in the next few months.

(Shameless promotion for my wife: If anyone is interested in a late 70s rock and roll novel set in Canada and the UK, let me know—an email is in my profile. I'll send a note out when it's available, regardless of the process we use to produce it.)



FWIW, I recently wrote a novel in Scrivener and with very little tweaking it did a nice job converting for print and ebooks (and it allows a fair bit of tweaking). All depends on your needs, of course, but I was pleasantly surprised at the output I could get directly from Scrivener (which I really like for its organization and writing capabilities)


Did you export from Scrivener for CreateSpace formatting? I'm interested in learning how if you did.


The short answer is that they're print ready as-is. Eric Ries printed a Leanpub book of his first year's worth of blog posts (we sold them at the first Startup Lessons Learned conference). They looked pretty good.

The slightly longer answer is that we are working on some features for a more print-ready PDF. Right now our PDFs are optimized for on-screen reading. Sone small changes such as gutters and page numbers that alternate sides will make a nicer looking print book.


The slightly longer answer is that we are working on some features for a more print-ready PDF. Right now our PDFs are optimized for on-screen reading. Sone small changes such as gutters and page numbers that alternate sides will make a nicer looking print book.

So, right now, who or what handles kerning, tracking, and such to ensure that you don't get distracting "rivers" of white space, odd page/paragraph breaks, and the like when printed?


We use LaTeX to take care of this in our PDFs. It does a pretty good job. Yes, it won't be 100% as good as if you paid a typesetter to do it, but there is nothing obviously objectionable.

For example, one of our books (leanpub.com/battingat10) was written by Chick Dubber, a retired typesetter. He noticed some bad hyphenation and we tweaked a few settings to make it look good. Other than that, he had no complaints.

There are lots of book samples that you can get for free from Leanpub. Many are linked to here: http://leanpub.com/bestsellers. Take a look and see what you think.


Sweet, thanks for this.

edit: Took a look at Raganwald's combinator book sample.

It has this bit of code:

      address = Person.find(...).tap { |p| logger.log "person #{p} found" }.addre\
      ss

That's absurd.

Was this an editing choice by Reg, or is this something the software does?


This is a special case of a preformatted code block.

For preformatted code blocks, there has to be an absolute line length -- otherwise the code just flows off the right side of the page, as <pre> blocks only do line-breaks when they are actually there.

So, what we do is take all pre-formatted code blocks, wrap them if they go over a certain line length and send a warning to the author letting them know that we did this. This is a case where human intervention is required -- we need to show all of the text, but most of the time you'll want to edit where the line breaks manually.

Most of the time automation is good enough, but we try to inform authors when there's something that needs their attention.


This is a case where human intervention is required -- we need to show all of the text, but most of the time you'll want to edit where the line breaks manually.

OK, so an author would know that there were things that should be manually inspected and changed if needed.


How does that work on a device like Kindle where people can change page orientation; font size; line spacing; column sizing; from condensed to not condensed; and change from serif to sans serif?

I notice lots of rivers on Kindle.


spatten said that Leanpub output is currently "print ready as-is." My question was, when a Leanpub document is printed, what ensures that there aren't distracting bits of extra white space and other annoyances that often require a human eye and manual adjustment to avoid?

If you're seeing rivers on a Kindle I'm guessing there'd be the same problem on paper.


Software can do this... (La)TeX has been doing it for years, and rarely gets it wrong.


I have recently bought Reginald Braithwaite's Kestrels book and note that it was formatted for 8 1/2 x 11. Is this typical, or is it easy to get the page size set for 6 x 9?


I got an answer back from Scott: they support 8 1/2 x 11 and 6 x 9. This is good.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: