System settings:
- Quarto v1.3.49
- nmfs-opensci/titlepage v3.3.8
- macOS 11.7.2
- Texlive 2022
Description
A simple test file like
---
title: "Some Very Long Title Which Spans Multiple Lines "
format:
titlepage-pdf:
titlepage-theme:
title-fontstyle: Huge
---
test
will result in the following latex syntax for the title:
{{\Huge{\nohyphens{Some Very Long Title Which Spans Multiple
Lines}}}\par
}%
There are a couple of problems with this syntax. The most important one is that the paragraph is ended at the wrong position. If you insert \par only after you switched back from the custom font size, then the text will be set with a wrong baselineskip (the one from the normal font around it and not with your title font). Try the following two lines to see the difference:
{{\Huge{\nohyphens{Some Very Long Title Which Spans Multiple
Lines}}}\par
}%
{{\Huge{\nohyphens{Some Very Long Title Which Spans Multiple
Lines}}\par}
}%

Another potential problem: Depending on what comes after the title, you might get an additional space from the unprotected line ending after \par}
Not a problem as such, just unnecessary:
- the outermost
{...} is unnecessary
- font size commands like
\Huge etc are switches and don't take an argument. Instead of writing \Huge{...} it should normally be \Huge ...
System settings:
Description
A simple test file like
will result in the following latex syntax for the title:
There are a couple of problems with this syntax. The most important one is that the paragraph is ended at the wrong position. If you insert
\paronly after you switched back from the custom font size, then the text will be set with a wrong baselineskip (the one from the normal font around it and not with your title font). Try the following two lines to see the difference:Another potential problem: Depending on what comes after the title, you might get an additional space from the unprotected line ending after
\par}Not a problem as such, just unnecessary:
{...}is unnecessary\Hugeetc are switches and don't take an argument. Instead of writing\Huge{...}it should normally be\Huge ...