-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Can't use footnotes with columns #2166
Comments
How did you try this two-column layout? I've always failed at them :) |
Simply used |
Oh, from the frametricks package? It's probably incompatible with the frame layout expected by resilient (if not with any other frameset actually...), as it defines its own frame(s) based on the current typesetter frame (so it doesn't know anything about footnote or margins frames, and who's gonna eat space, and how these should then adapt. Another example of a quick hack that only works if the initial frameset is... naive. |
(I was about to say my usual thing: "This whole frametricks thing is a joke", hesitated, and oh well. It is a joke. But I've used that utterance so many times that I'm not sure I'll want to repeat it again 🤣 ) |
So how to have a two column page without
Does resilient have any support for multiple columns pages? I didn't find anything related in its documentation... I really need to use a two column for this one! |
Not yet. There was an experiment in February 2023 with results shown on our Gitter (which you could join by the way): But although it seems nice "on a picture", it breaks severely in many cases, so I put it on hold until I could return to my new typesetter/pagebuilder attempt (which helps here, but then breaks on footnotes...). But I am afraid this isn't a discussion for SILE (core). |
Interesting, how can I join there? |
Third bullet in the Wiki https://github.com/sile-typesetter/sile/wiki/Contributing#regarding-questions ;) |
Only the first frame has its height changed, and even so the text is overwritten.
I'm using SILE 0.15.5 with resilient (no modifications in the default styles.yml).
The text was updated successfully, but these errors were encountered: