{"componentChunkName":"component---src-templates-post-template-js","path":"/book-review-troubles-en","result":{"data":{"markdownRemark":{"id":"0792dca4-887f-5850-939a-56aa85d0cef4","html":"
\n

This page has been machine-translated from the original page.

\n
\n

This article explains how to recover when Re:VIEW Starter suddenly stops generating PDFs even though you did not change anything.

\n

Recently, as a new challenge, I have been writing a technical doujin book to distribute at Tech Book Fest.\nFor that writing work, I use a tool called Re:VIEW Starter.

\n

Reference: Introduction to Re:VIEW Starter, a great tool for people writing technical doujin books - Qiita

\n

At one point, I suddenly ran into a problem where PDF generation stopped working, so I am leaving a record of how I resolved it.

\n

Specifically, I deleted every file with the following extensions directly under the *-pdf directory generated by Re:VIEW Starter.

\n\n

Problem that occurred

\n

All of a sudden, Re:VIEW Starter started outputting the following error and failed to generate a PDF.

\n
Package pagecolor Warning: Option nopagecolor=none requested but \\nopagecolor u\nnknown:\n(pagecolor)                By option nopagecolor the \"colour\" to be used with\\n\nopagecolor\n(pagecolor)                is set. The current value is \"none\" (maybe by defaul\nt),\n(pagecolor)                but command \\nopagecolor is undefined.\n(pagecolor)                Therefore the colour cannot be \"none\".\n(pagecolor)                Please change the option accordingly!\n(pagecolor)                As first aid nopagecolor is now set to white\n(pagecolor)                 on input line 116.\n\n\nPackage pagecolor Warning: Option pagecolor=none (maybe by default) used,\n(pagecolor)                but \\nopagecolor is unknown.\n(pagecolor)                Please use anotheroption value;\n(pagecolor)                white\n(pagecolor)                will be used now\n(pagecolor)                 on input line 127.\n\n)) (./mycolophon.sty) (./mystyle.sty) (./book.aux)\nRunaway argument?\n{\\contentsline {subsection}{\\nu\n./book.tex:193: File ended while scanning use of \\@writefile.\n<inserted text>\n                \\par\nl.193 \\begin{document}\n\nNo pages of output.\nTranscript written on book.log.\n*\n* ERROR (review-pdfmaker):\n*  failed to run command: uplatex -halt-on-error -file-line-error book.tex\n*\nmake: *** [Makefile:45: create_pdf] Error 1
\n

In most cases, something like this is caused by a problem in a *.re file.\nHowever, in this case PDF generation failed even when I used a completely valid *.re file.

\n

In the end I never identified the exact cause, but it looked like the issue was somewhere in the TeX compilation step, so I deleted all of the following files and the problem was resolved successfully.

\n\n

This happened completely out of nowhere, and because I could not figure out the cause, I ended up wasting about an hour.\nFor now, if PDF generation fails, it seems worth trying to delete previously generated files first, so I am leaving this as a memo.

","fields":{"slug":"/book-review-troubles-en","tagSlugs":["/tag/book-en/","/tag/note-en/","/tag/re-view-en/","/tag/english/"]},"frontmatter":{"date":"2021-06-09","description":"This article explains how to recover when Re:VIEW Starter suddenly stops generating PDFs even though you did not change anything.","tags":["Book (en)","Note (en)","Re:VIEW (en)","English"],"title":"How to Recover When Re:VIEW Starter Breaks Even Though You Changed Nothing","socialImage":{"publicURL":"/static/dc4d8b7f8795f3c3d3489d9957d155f2/no-image.png"}}}},"pageContext":{"slug":"/book-review-troubles-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}