Please add an actual book to the demos.

[StefanSchroeder]

So that one can clone one repo and just drop-in one's own book.

[alerque]

Will do. Quite apropos that this would be issue #1. That is the whole idea of this repo anyway..... I open sourced the tools I'm using but since I couldn't post the source for the books I've published I was going to come up with a couple Creative Commons or Public Domain texts and set them up as example books.

I found one Sherlock Holmes text but the content was pretty dirty. Any good classic texts you know about in some reasonably clean format that would be easy to convert to Markdown?

[StefanSchroeder]

Haha, Sure, project Guttenberg is your friend. https://www.gutenberg.org/
I don't believe that their books are formatted in MD, but rather in plain text.
It should be possible with some vi-wizardry to brush it up with some basic markdown.
Some fairy-tale should be a safe bet regarding propriety, e.g.

http://www.gutenberg.org/cache/epub/17860/pg17860.txt

[felipesanches]

I came here looking for the same. I wonder if the documentation for SILE and CaSILE themselves wouldn't also be good examples of book contents. And it would also work as dog-fooding.

Today @simoncozens told me I should look up the documentation, when I asked about an example of a book typeset in SILE. I see don't see "The SILE Book" referenced in this repo, though. Sounds to me like an obvious example to showcase.

• https://github.com/sile-typesetter/sile/tree/master/documentation
• https://sile-typesetter.org/manual/sile-0.10.2.pdf

[alerque]

The SILE book (manual) is typeset entirely in SILE with no tooling help from CaSILE. In this case I think that's appropriate. CaSILE has a lot to offer for publishing work where output is a mix of print, ebook, etc. and you need extra resources like covers and promotional materials. The SILE manual however is currently only distributed as a digital PDF and very specifically showcases many of the SILE specific functions as it documents each package. Hence the source material has to be SILE code (in many cases coming from the packages themselves which are self documenting). CaSILE on the other hand is really designed for prose content coming from plain text formats like Markdown and converting it to SILE for typesetting.

I'm not saying a full book project example would be a bad idea, but the SILE manual is not a good candidate. A CaSILE manual if I were to write one would be, but I have to unburry myself from the stack of "to publish"‌ books on my desk first.

[felipesanches]

Cool! Thanks for the clarification ;-D