Mikescher/www.mikescher.com
1
0
Fork 0
Code Actions

fix typo
All checks were successful
Build Docker and Deploy / Build Docker (push) Successful in 1m12s
Details
Build Docker and Deploy / Deploy to Server (push) Successful in 19s
Details

Browse Source
This commit is contained in:
Mike Schwörer 2024-01-11 23:30:08 +01:00
parent 1010d99fd2
commit e81621ef9c
Signed by: Mikescher
GPG Key ID: D3C7172E0A70F8CF
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
www/statics/blog/proj_lawful_ebook.html
View File

@ -30,7 +30,7 @@
<li>the <code>*-moreinfo</code> variant also includes the alignment text of each post/character after the character-name.</li> <li>the <code>*-moreinfo</code> variant also includes the alignment text of each post/character after the character-name.</li>
<li>the <code>*-avatars</code> variant show the character avatar beside each post. This forces us to include all 600-ish avatars in the epub file, which increases filesize and loading time</li> <li>the <code>*-avatars</code> variant show the character avatar beside each post. This forces us to include all 600-ish avatars in the epub file, which increases filesize and loading time</li>
<li>the <code>*-avatars-moreinfo</code> also includes the alignment text and author name (additionally to the avatar). Here the avatar/character-name/alignment-text/author-name are also no longer inlined, but get their own paragraph at the start of every post.</li> <li>the <code>*-avatars-moreinfo</code> also includes the alignment text and author name (additionally to the avatar). Here the avatar/character-name/alignment-text/author-name are also no longer inlined, but get their own paragraph at the start of every post.</li>
<li>the <code>*-biggerhtml</code> variant looks the same as <code>*-inline</code>, but internally every chapter is a single big file (instead of multiple split files), this makes the initial loading of the epub slower, but codevents a forced page-break after every 128th post.</li> <li>the <code>*-biggerhtml</code> variant looks the same as <code>*-inline</code>, but internally every chapter is a single big file (instead of multiple split files), this makes the initial loading of the epub slower, but prevents a forced page-break after every 128th post.</li>
</ul> </ul>
As said above, it should be possible to create epub's with other combination of options (see <code>Program.cs</code> and <code>Options.cs</code>) As said above, it should be possible to create epub's with other combination of options (see <code>Program.cs</code> and <code>Options.cs</code>)