- Jul 24, 2023
-
-
Karl Fogel authored
-
- Jan 20, 2023
-
-
Karl Fogel authored
Before this change, refs would be stripped from documents by default (even documents, such as invoices, that don't normally have any explicit YAML head). After this change, refs are not stripped by default, but if you put "remove-refs: TRUE" in the YAML head then they will be, and you can optionally customize the regex with "ref-regex". Note also that it's "ref-regex" now instead of "ref_regex". This is because some editors (cough Emacs cough) render unescaped underscores in a jarring and distracting way in LaTeX documents, including even underscores in YAML frontmatter. A better fix would be to teach Emacs how to recognize when it's in a non-LaTeX section of a mostly-LaTeX document, but that's a bit more yak than I have time to shave today.
-
- Sep 19, 2022
-
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
- May 17, 2021
-
-
James Vasile authored
-
- Mar 19, 2021
-
-
Karl Fogel authored
Since the OTS_DOCTOOLS_DIR environment variable is required now, use that instead of Python's '__file__' variable to get values for the YAML block comment that we put at the end of each PDF. Note that the two other uses of '__file__' in this code base, in 'pipeline/pipeline.py' and 'pipeline/plugins/65_bugs.py', stay as they are: for what they're doing, '__file__' is appropriate.
-
- Jun 28, 2020
-
-
James Vasile authored
-
- May 06, 2020
-
-
James Vasile authored
-
James Vasile authored
Explain what reference system we're using in case somebody else is interested in the plugin.
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
* Detect inkscape version of 1.0 rc 1 or later and add some tex to call inkscape using new-style command line parameters. * Add a preambles loop to the base jinja template so we have an easy way to add preamble sections that doesn't require clobbering the existing preamble items * Add a dump function to pipeline.py so we can dump our output and inspect it during debugging.
-
- Apr 21, 2020
-
-
Karl Fogel authored
As promised in commit db47b65d.
-
Karl Fogel authored
Since commit 018499ec, when the bug-detection plugin is enabled (e.g. "bugs: True" in the header) then on detecting a bug in the document we stop the build, unless in draft mode ("draft: True"). There are thus three ways to fix such a build: 1) Fix whatever the bug is in the document. 2) Turn on draft mode. 3) Turn off bug-detection mode. Since our bug-detection module is not perfect, (1) is not always an option because there might not actually be a bug in the document. That's what happened in this case: the module's attempt to detect proper formatting of footnotes by looking for the leading backslash (e.g., "\footnote" instead of "footnote") cries a false positive if the document uses "\begin{footnotesize} ... \end{footnotesize}" to set the font size. I'll improve that bug-detection case in a subsequent commit. In the meantime, this commit improves the error message to inform the user about possibilities (2) and (3), which are not otherwise obvious.
-
- Mar 25, 2020
-
-
James Vasile authored
-
- Jan 09, 2020
-
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
This plugin provides general infrastructure for issuing warnings and errors upon finding certain regexes. Right now, it just looks to see that footnotes are formatted with the preceding slash. The plugin has tests.
-
- Jan 08, 2020
-
-
James Vasile authored
-
James Vasile authored
Karl called these build strings. Much better name. We had fields labelled svn and git, but no real explanation for them in the string names, so I made them more explicitly refer to the doctools and ots repos.
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
After we build a pdf, it is sometimes useful to attach some information to the built file. Here we do that as a YAML-formatted block of lines appended to the PDF and marked in PDF syntax as comments. Our PDFs now carry some machine-readable metadata.
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
If a document comes in and there's no yaml frontmatter, we don't jinjify. You might not need any yaml frontmatter metadata but still want jinja features (e.g. jinja macros). In that case, add a dummy var. The reason for doing this is that legacy docs don't have any frontmatter, and this is a convenient way to distinguish them.
-
James Vasile authored
* Make -rXXXX versions for all builds, not just drafts * Add draft plugin * In template, set draft to trigger on both True and 'True' * Move path into PIPELINE definition * Silence some echo * Use .tex instead of intermediate_ltx * Simplify some bash * Let the plugin handle draft instead of passing it as an option * Cleanup .tex files We can now do redacted and draft at the same time.
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
Refactor the jinja rendering and the redaction as a pipeline of filters that run as needed.
-