Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup book class, set sane defaults, expand arsinal of tools #597

Draft
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

alerque
Copy link
Member

@alerque alerque commented Apr 29, 2019

The book class is missing a few basic things I would expect (like \part and \title (or \titlepage?) handling. It also has a few things backwards (like gutter margin on the right in what is otherwise an LTR default layout).

This is a work in progress to fix those things.

@alerque alerque changed the title [classes] Place gutter margin on left for LTR layout Cleanup book class, set sane defaults, expand arsinal of tools Apr 29, 2019
@sile-typesetter sile-typesetter deleted a comment May 22, 2019
BREAKING CHANGE: Any books that used this layout by default and manually
fixed this by either skipping a page or reversing the left/right masters
will need to undo those hacks to get their proper layout back.
@sile-typesetter sile-typesetter deleted a comment May 31, 2019
BREAKING CHANGE: The :pre and :post function names didn't make any sense
because they were not actually before or after the chapter (or whatever
level) headings but just around the numbers. This makes it a lot more
clear in say a book or project library what is actually being done.

This is a step towards making the heading levels easier to style.
@alerque
Copy link
Member Author

alerque commented Mar 17, 2023

No idea if that merge resolution makes any sense, this branch was only 2748 commits behind master! I couldn't even reason about what it was doing any more the code was so old. Some bits still seem to make sense, some probably are obsolete and should be backed out.

@alerque
Copy link
Member Author

alerque commented Mar 17, 2023

Nope merge is borked. I'll probably just look through the commits again and cherry pick instead of trying to fix the whole branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Status: In progress
1 participant