- Oct 30, 2023
-
-
Karl Fogel authored
This is identical to ${OTS_DIR}/forms/latex/report.ltx (as of r22457), except that here we drop the "MACROS" section from the end -- all it contained was the "contact()" macro, which gave James's and Karl's contact information, which is not something we want to ship here. This commit may or may not cause a problem for OTS folks building reports, depending on whether this report.ltx shadows the one in ${OTS_DIR}/forms/latex/report.ltx. If it does, we'll fix that when we find out about it. Right now, Karl and Seth Schoen just needed to get ots-doctools working for Seth on his machine, and the obstacle in front of them was that report.ltx was alleged to be missing: jinja2.exceptions.TemplateNotFound: report.ltx
-
- Feb 05, 2023
-
-
Karl Fogel authored
Suddenly it's breaking doc builds. I don't know why.
-
- Oct 11, 2022
-
-
Karl Fogel authored
Before this fix, building a document that has zero instances of "\VAR{todo('foo')}" in it would still result in a "No todos" message at the top (this has probably been true since commit 5a765ff9).
-
- Sep 19, 2022
-
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
James Vasile authored
-
- Dec 02, 2020
-
-
Karl Fogel authored
The former supersedes the latter, and has more options, so we should use it. But the proxemitae cause for this change is that I wanted to use lower-case Roman letters as item markers instead of numbers. Now, you might think it would work to just put "\usepackage{enumitem}" at the top of the doc and then use "\begin{enumerate}[label=\alph*)]", but no, that gets an error: ! Missing number, treated as zero. <to be read again> \c@* l.394 \begin{enumerate}[label=\alph*)] ! ==> Fatal error occurred, no output PDF file produced! The reason for this is that the two packages are incompatible. With 'enumerate' already loaded, if you load 'enumitem' and then try to take advantage of the feature for which you brought in 'enumitem' in the first place, you'll get the above error. This change should not break any of our older documents, since both packages work fine for plain old enumerations or lists, and until now that's all we could do -- we obviously weren't using the list-item styling feature that 'enumitem' makes possible. I also spot-checked several of OTS's more complex documents to make sure they still build.
-
- Nov 23, 2020
-
-
James Vasile authored
-
- Sep 24, 2020
-
-
Karl Fogel authored
This follows up to r16468 in the corporate repository.
-
- Jun 28, 2020
-
-
James Vasile authored
-
- Jun 08, 2020
-
-
Karl Fogel authored
-
Karl Fogel authored
In https://github.com/OpenTechStrategies/ots-doctools/pull/10, @choeppler points out (#pullrequestreview-425924575) that the "OTSDIR" environment variable should not be required to be set, since only "OTS_DOCTOOLS_DIR" is documented, and that furthermore if we are going to check paths under "OTSDIR" we should at least do it in the same order relative to "OTS_DOCTOOLS_DIR" that 'Makefile.docspecific' uses. This commit is his suggested patch from that PR review. (Note that the commits in that PR are actually already applied. There must have been a rebasing somewhere along the way, as they all have different commit IDs in master than they do in the PR.)
-
- May 06, 2020
-
-
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.
-
- Jan 08, 2020
-
-
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
-
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
Refactor the jinja rendering and the redaction as a pipeline of filters that run as needed.
-
James Vasile authored
It works, but needs some cleanup and documentation
-
James Vasile authored
-