I would really like to use the same toolset for publishing POD (Print On Demand) books that I use for ebooks. Yet the pdf generation abilities of both docutils and Sphinx seem more focused on pdf "ebooks"---pdf's that you would read from a computer---not pdf's that are approriate to create physical books from. I think the solution is to add support for the LaTeX "memoir" package to Sphinx. I'll eventually get around to it, but it is not on the top of my stack. To that end I'll pay up to $200 (paypal or Amazon gift) to get that support.
For those not familiar with memoir, here's a snippet of the README:
Memoir is a flexible class for typesetting poetry, fiction, non-fiction and mathematical works as books, reports, articles or manuscripts. Documents can use 9pt, 10pt, 11pt, 12pt, 14pt, or 17pt as the normal fontsize and, if you have scalable fonts, 20pt, 25pt, 30pt, 36pt, 48pt, or 60pt sizes, or even larger. Many methods are provided to let you create your particular design. The class incorporates over 30 of the more popular packages.
Here are the details. The first person who notifies me of two github repos that meet the following points will get $100:
- A github repo containing a Sphinx project that renders out to pdf using the memoir package. The document must have an example of:
- Half Title Page
- Title Page
- Copyright Page (on verso page)
- Dedication
- Table of Contents
- Introduction
- Chapters (should start on right page)
- An index
- blank pages at the end
- Customizing page size
- The chapers should have an example of:
- Text spanning multiple pages (lorem ipsum is fine)
- Normal text
- Italicized text
- bold text
- monospace text
- Sections
- footnotes
- a code block
- an admonition
- a long admonition that is longer than a page
- an admonition with a code block inside of it
- a figure
- a table
- A github repo containing a fork of Sphinx that has memoir support. When using this fork with the above project, a suitable pdf should fall out. Numbering of chapters is correct, page numbering is correct (odd on right side), index is correct, etc.
Ideally most of the book (Table of Contents through Index) would be pure rst (or sphinx rst++). I'm ok with raw directives on the front matter.
If you are familiar with LaTeX and Sphinx, this should be pretty straightforward. It would also be a great project for someone interesting in learning those technologies.
The person who can deliver the above will make me quite happy. But, as I said, I would pay up to $200. The remaining $100 will be appropriated to the developer (or someone else) who sees that this gets pushed upstream into Sphinx proper (ie when I see a bitbucket commit with the changes on the Sphinx project). So the person who files the bug, patch and follows through with any needed tweaks to get this into mainline will get that money. I reserve the right to split up this portion among people as well.
(I apologize in advance for the github requirement, I prefer that system, so the first deliverable needs to be there. Given that Sphinx prefers bitbucket, you need to play well with them for the second deliverable.)