Repository navigation
The Temporary page! #169
Replies: 12 comments 13 replies
|
If you know that you never compile more than once, you could split the pdf after compilation to remove the last page |
|
This is a kernel feature not an |
|
If you know the absolute number of pages that will be created you can add If the number is wrong you will get a warning and will have to rerun: |
you have to understand that this is not simply an unnecessary burden. LaTeX generates that page for a reason: there are some things that need to be done at the very end of the run and put into the last page when it comes down do pdfmanagement and if the last page has been shipped out without knowing that it is the last page that doesn't happen, so without it (or if you cut this extra page off externally --- depending on the tool you use or why the page was generated) your document may not be any longer correct. So it is an emergency measure and two runs are really required. As Ulrike said, if you know how many pages there should be you can inform LaTeX about it and then the second run can be avoided, but otherwise it is like with cross refs: you need two runs because LaTeX doesn't know the the correct values first time around and thus inserts ?? instead of the correct values. |
|
I did a Google search and it seems like there is a way of selecting the range of PDF pages to be placed in the output by something like |
|
if you use ltx-talk because you want a tagged pdf then you shouldn't use pagesel. See latex3/tagging-project#542. And if you know that your document has 5 five pages, then |
|
I thought you are using ltx-talk because you want accessible presentations, you arn't likely to get them if you use something like pagesel which is not compatible with tagging, see https://latex3.github.io/tagging-project/tagging-status/#pagesel |
|
Would it be possible to prescan the file with Lua and guess the numbers of pages (quickly) for the first run? A bit of a can of worms, obviously, but for simple documents it would be a minor quality of life improvement.
(Very low on the priority list I’d imagine)
|
|
possible is close to everything Will given a turing complete program :-), but realistically it requires the a full processing of the document to get it right most of the time given the diversity of document sources. I think it would be futile to expect much and frankly in most cases it would be useless because document are usually processed more than once during development and afterthe first run LaTex typically knows how many pages to expect. And if documents are auto-generated then I don't see why you can't run them several times automatically as well without much burden. |
|
My situation is a bit different as I have a set of many MD files (in the number of hundreds, as I am a teacher and these are my lecture slides) I am almost always working on several files at the same time until the very last moment. It is difficult for me to track which file has been run for how many times, as I uses a Makefile to compile them. |
|
but then your makefile should do precisely that: run the document as often as necessary ... not really difficult to automate. Again, if you get this page and don't rerun your document is simply just incorrect in places (and you are lucky if it doesn't show or breaks accessibility). |
|
You could compile with latexmk, which will automatically determine if an additionally run is necessary. Or you could parse the log file in your makefile to determine if additional runs are necessary. The you are sure that you are getting a correct document. |
|
Maybe I'll just set in the makefile to compile the TEX file twice always, which isn't too difficult to do. |
|
Why waste time with unnecessary runs? There are tools which can tell you how many runs are necessary. |
|
And sometimes twice isn't sufficient. So always-twice will sometimes break the PDF and sometimes compile unnecessarily. Of course, depending on the content, you may know twice is always sufficient for these documents. But tagging often requires 3 runs with LuaLaTeX for me. |
|
Really, need to compile it three times? As for latexmk, I guess the only reason I didn't use it was because it does not look into the TEX file to check for a !TEX program line to pick the correct LATEX engine, and of course I was using beamer and it wasn't a problem then. But now I guess it is time to start using it. |
|
(depending on which other tools you use, even 3 run might not be enough) If you want to control the engine from within the file, use the coll automatisation tool arara. The you can specify the tools and engines from within your file. |
|
For example if your file looks like you can compile it with |
LaTeX can need arbitrary many runs (down to never getting to a stable state, though that is rare). But three is quite possible, for example, in an article with a TOC and xrefs to pages: first time no TOC no xrefs resolved, second time TOC is there but xrefs now resolved incorrectly because TOC moved the text, third time all correct. If you use things like varioref text length can change depending on placement requiring more cycles. (The LaTeX Companion 3rd edition requires 7 compilations to settle) And as an example of a simple document that never settles: consider a document with roman page numbers and crossref to pages. The width of the page numbers is not an increasing sequence, e.g viii is wider than ix. So it is possible to construct a document with a page ref to page 8 (viii) which if inserted moves the label to page 9 (ix); thus LaTeX responds with "rerun to get ....". Next run it replaces the xref with ix after which the label moves back to page 8 (viii) and the cycle restarts. |
|
For whatever reason 'arara' is not a recognizable command on my computer. But it is okay, I will use latexmk as it is more popular and readily to get more help online if I need to. |
|
arara is available both via texlive and miktex -- and you could use it in combination with latexmk to specify the engine within the file. |
|
Following is what I saw when I did a tlmgr update --all on MACOSX For whatever reason the arara is skipped and maybe that's way it is not available. |
|
Try with |
|
Interesting! Got it. Thanks. |
|
You're welcome! |
Uh oh!
There was an error while loading. Please reload this page.
Hey, I don't know if I am the first one who asks this question, but I wanted to see if there is a way to turn off the generation of the "Temporary page!" (LATEX was unable to guess the total number of pages correctly...). I guess I can understand its usefulness, but in my case the TEX file is auto-generated, and only serve to be compiled once to get the desired PDF file; thus having to always compile it twice to get rid of the temporary page becomes quite a burden to me. Thanks.
All reactions