When I was finishing up production on my two latest titles (Pride and Prejudice and The Good Soldier), I decided to include a separate colophon (a page describing the production of the book in your hand). And that’s when I saw an error that has been reproduced in every book up to now.
You see, when I published my first title, Wuthering Heights, I was concerned about the page count (it’s a hefty book!), so instead of including a full page colophon, I had added some typeface information on the copyright page. I must have been in full panic (or sleep deprived) trying to pull everything together, because I named the wrong font: every Gladstone Press titles uses Aldus Nova typeface, not Aldus Next (which doesn’t exist) for the reading text. This would have been easily fixable if I HADN’T CONTINUED TO CUT AND PASTE THAT INFO INTO EACH SUBSEQUENT BOOK’S COPYRIGHT PAGE.
So, my apologies. It doesn’t seem like a huge error compared to, say, leaving out a full page of text or forgetting to print the book’s title on the spine (both errors I’ve encountered working with much larger presses), but for me, it’s a big deal.
Gladstone Press is run almost entirely by myself, with some help from friends in the industry who can double-check my spelling and syntax on cover copy, or, in the case of a book which has been entirely mangled over the years, help me with proofreading and comparing editions. I try to keep errors to a bare minimum through their expertise, but I never had anyone fact check my little statement on typefaces. Argh.
On that note: if you own any of my books and would like me to send you a bookplate containing the correct (and full) colophon (including printer and paper quality info), please reach out to me via email at firstname.lastname@example.org. Let me know what title(s) you own, and perhaps also when or where you purchased. With that info I can put together a colophon that matches your book. It’s the least I can do.
As a friend of mine blithely put it, the errors make the book more—not less—collectible. But I’m still going to cringe about this error, at least for a few months . . .