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

T1 encoding in pdfLaTeX makes default sans-serif too wide #29

Closed
alobrv opened this issue Oct 11, 2021 · 3 comments
Closed

T1 encoding in pdfLaTeX makes default sans-serif too wide #29

alobrv opened this issue Oct 11, 2021 · 3 comments

Comments

@alobrv
Copy link
Contributor

alobrv commented Oct 11, 2021

Maybe this is out of the usage expected from this template, but if the titles are modified to use sans-serif font instead of small caps serif, T1 encoding makes the TeX default cmss font appear oddly wide and unbalanced. Titles appear normal when using the default OT1 encoding.

image
image

Even using the provided title style (small caps with serif), the default serif cmr produces different results, with OT1 encoding looking a bit better.

image
image

This issue only appear to affect the CM family, but given that it is a fairly popular font choice, perhaps it is be better to use \RequirePackage[OT1]{fontenc} or just leave it unspecified if there is no downside to it?

@Pseudomanifold
Copy link
Owner

Thanks for mentioning this! I am not up-to-date with all the encodings any more, but I was under the impression that OT1 is the older one. Is that correct? I don't want to leave the encoding unspecified because it causes problems when copying text from the document. What do you think about an FAQ item?

@alobrv
Copy link
Contributor Author

alobrv commented Oct 11, 2021

Yes, that seems like a good solution! You are right about OT1 being indeed the older encoding. Since T1 needs to be enforced to avoid those copying problems, maybe it is worth mentioning that default CM will not work properly in this scenario and other alternatives such as \usepackage{lmodern} are probably a better fit.

There is more info on this in:

@Pseudomanifold
Copy link
Owner

Thanks a lot for the additional links! I updated the FAQ accordingly and linked to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants