[BUG] Isel template doesn't compile
Closed this issue · 5 comments
Which version of the template are you using? 6.10.12
Checkout the repo, defined the school as ISEL (\ntsetup{school=ips/isel}
), run make and this is the output:
Redoing nameref's sectioning
Redoing nameref's label
Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref) removing `\<def>-command' on input line 203.
Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref) removing `\<def>-command' on input line 203.
Package todonotes Warning: The length marginparwidth is less than 2cm and will
most likely cause issues with the appearance of inserted todonotes. The issue c
an be solved by adding a line like \setlength {\marginparwidth }{2cm} prior to
loading the todonotes package. on input line 203.
(/usr/local/texlive/2019/texmf-dist/tex/latex/psnfss/t1phv.fd)
! Package pdftex.def Error: File `\@school@logo@memory .pdf' not found: using d
raft setting.
See the pdftex.def package documentation for explanation.
Type H <return> for immediate help.
...
l.211 \ntprint{covers}
% The cover page
Do you use a cloud-based service? Which one? No
Do you use a local service? Yes, mactex, Mac OS 11.6.7
What went wrong?
Doesn't compile
Expected behavior
A clear and concise description of what you expected to happen.
Instructions to Reproduce the Error
Steps to reproduce the behavior:
- Start from a "fresh" distribution of the template
- Add packages "X" and "Y"
- …
- In the main text, add the text "ABC" or the command "XYZ"
- See error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
ISEL is IPL and not IPS. 😃
\ntsetup{school=ipl/isel}
Sorry for the typo, even when I put \ntsetup{school=ipl/isel}
I get the same error
Ah! That's weird. Because I get that error with "ips/isel", but everything works all with with "ipl/isel".
Please double check… if the errors persists, please let me know which LaTeX distribution (and version) you are using. Thanks.
Definitely cannot reproduce the bug. It works on my machine! 😁
@jsaramago
I was testing with the develop branch and not the master.
Updated the master to match develop. Please check again.
Please let me know if it worked or still fails. Thanks.