-
Notifications
You must be signed in to change notification settings - Fork 222
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
Styling of \section and \subsection is incorrect in epleval-derived classes due to bad titlesec options #841
Comments
Fixes Gp2mv3#841 Styling unified to that of sans-serif fonts for all section titles. Label (in a shadow box) aligned such that the lower bound of the white box is aligned with the baseline of the section title.
Newly found bug: actually, in |
Bon ben va falloir choisir ce qu'on fait alors (je switch en français pour être un peu plus "ouvert").
Aussi, pour le moment la majeure partie de ces incohérences vient de l'utilisation de (Pour ma part je suis en faveur du 2 ; le 4 est possible mais franchement les titres sont dégueux car la taille du label avec cette Pour le contexte : j'essaie de fix #632 et #844 et donc j'ai remarqué cette mocheté. |
Autre argument en faveur de la dépréciation de |
Ex: the LEPL1803 2016 June exam contains a small unnumbered (starred) section before the questions, where there are some instructions and recaps.
In
eplbase.cls
, we define, usingsectsty
, the sections, subsections... to have a sans-serif font.In
epleval.cls
, in order to have the stylish icon for the question number, we usetitlesec
to change the styling. Buttitlesec
erases the modifications done withsectsty
, so the font is back to a serif font, while the subsections are still with a sans-serif font.This is ridiculously ugly. I can't believe it's by design.
(As I'm working in #840 to insert some special code into
\section
, I've come across this inconsistency.)Either we repair the
titleformat
command to have a sans-serif font again. Or we change the styling of all (sub)sections inepleval.cls
to go back to a serif font. Or we give up with the styling question number (which would be my personal preference as it allows a much "cleaner" code for what I'm trying to achieve in #840 ).Opinions?
(Related to #127 )
The text was updated successfully, but these errors were encountered: