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

Compiling Errors [Overleaf] #3

Open
zrobertson466920 opened this issue Apr 3, 2023 · 6 comments
Open

Compiling Errors [Overleaf] #3

zrobertson466920 opened this issue Apr 3, 2023 · 6 comments

Comments

@zrobertson466920
Copy link

The poster displays when compiled on Overleaf using pdfLatex (2022). However, there appear to be undefined control sequence errors in main.tex from the compiler.


\beamer@thmffamily@footline ->\Raleway

l.67 \begin{document}

The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., \hobx'), type I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


\beamer@thmffamily@heading ->\Lato

l.327 \end{frame}

The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., \hobx'), type I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

@mirandali707
Copy link

Months late, but in case anyone else faces this issue I was able to get no compile errors by changing the compiler to XeLatex (in the Overleaf doc, Menu > Settings > Compiler) and uncommenting lines 11, 18, and 19 in beamerthemegemini.sty (\RequirePackage{fontspec}, \newfontfamily\Raleway[Ligatures=TeX]{Raleway}, \newfontfamily\Lato[Ligatures=TeX]{Lato}). It also seems to look nice if you uncomment lines 21-28 also :) cheers

@RylanSchaeffer
Copy link
Owner

I tried creating a new Overleaf project. I uploaded the files to a blank project, hit compile and everything seemed to work:

image

This is with pdflatex:

image

@zrobertson466920 @mirandali707 do you two still have the same problem? If so, can you tell me how to recreate it?

I'd like to fix it if possible.

@lgelauff
Copy link

lgelauff commented May 24, 2024

I am running into errors as well. I forked the repo, and downloaded it from there to Overleaf. I get 9 errors/warnings:

  • 2 undefined control sequence errors for \begin{document}
  • 4 undefined control sequence errors for \end{frame}
  • Warning: Font shape OMX/cmex/m/n' in size <35.83> not available` in main.tex
  • Warning: Font shape OMX/cmex/m/n' in size <17.915> not available` in main.tex
  • Warning: Size substitutions with differences in main.tex

Changing my settings to yours did not change anything.

Changing to XeLaTeX doesn't change anything, but when I then also uncomment the lines mentioned by @mirandali707 , it works. Uncommenting lines 11 and 18 gets rid of 5 of the errors, line 19 gets rid of the final one.

Switching to pdflatex results in Fatal Package fontspec Error: The fontspec package requires either XeTeX

@RylanSchaeffer
Copy link
Owner

RylanSchaeffer commented May 24, 2024

@lgelauff I just downloaded the repo as a .zip and uploaded it to Overleaf and it compiles:

image

I see the 9 errors but Overleaf doesn't seem to care. I'm not an expert with Latex, so I'm not sure if it matters. Do you think it does? If so, should I make the above fixes?

@RylanSchaeffer
Copy link
Owner

If I make the above suggested fixes, it appears that pdflatex no longer works :(

@lgelauff
Copy link

The pdf indeed does compile for me with these errors, but I generally try to fix them. Up to you if you want to spend more time on fixing this - thanks for at least making the template available!
An easy improvement could be to add a comment about the errors, so that people don't blame their own code for it.

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

4 participants