You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you look through the failed Travis builds, you'll find that very commonly it is the PDF build that fails. Almost always, that failure is justified, as in the failure is represented by some failed html page displaying. This is because during the PDF build phase, we process the LaTex in house, meaning we'll catch math LaTex errors, whereas during the html building phase, the LaTeX is processed by the mathjax javascript code running on the client's computer. This means that the PDF build (found where?) acts as a LaTeX validator. This guide should include common errors we've made in the past and how to fix them.
The text was updated successfully, but these errors were encountered:
IGNORE WARNINGS - there will be 100s of warnings. They are not what broke your build. Instead, just pay attention to the errors, designated with a "!". To find it, scroll to the bottom of the build - the error will start with a !.
Attempt to find the point in the corresponding html where the error ocurred. Chances are, it will be in or near a math LaTeX block. Use the copied language in the error statement to quickly find the spot in Atom with ctrl-shift-f.
If no error message is given fatal error, then look through the textbook starting from the last warning. Leftover html from our Markdown days is one likely source of errors. But that should have all been cleared out by now. Badly formatted equations are the other culprit.
If you look through the failed Travis builds, you'll find that very commonly it is the PDF build that fails. Almost always, that failure is justified, as in the failure is represented by some failed html page displaying. This is because during the PDF build phase, we process the LaTex in house, meaning we'll catch math LaTex errors, whereas during the html building phase, the LaTeX is processed by the mathjax javascript code running on the client's computer. This means that the PDF build (found where?) acts as a LaTeX validator. This guide should include common errors we've made in the past and how to fix them.
The text was updated successfully, but these errors were encountered: