generator-latex-template 2026.9.23 → 2026.10.8

package/README.md

@@ -132,7 +132,8 @@ In the long run, the contents of the `paper.tex` (and similar) files in reposito
 - Cancel workflows:
   - `gh run list -L 100 --json databaseId -s queued -R latextemplates/generator-latex-template | jq -r '.[] | .databaseId' | awk '{gsub(/\\r\\n/,RS)} 1' | while read -r run_id; do gh run cancel "$run_id" -R latextemplates/generator-latex-template || true; done`
   - `gh run list -L 100 --json databaseId -s in_progress -R latextemplates/generator-latex-template | jq -r '.[] | .databaseId' | awk '{gsub(/\\r\\n/,RS)} 1' | while read -r run_id; do gh run cancel "$run_id" -R latextemplates/generator-latex-template || true; done`
-- Update submodule of "derived" templates (LNCS, ...): `scripts/spread-updates.sh`
+- Update submodule of "derived" templates (LNCS, ...): `scripts/spread-updates.sh`. It also links the generator's `refine-ltg` PR in the description of each template's "Update LTG" PR.
+- Keep the `refine-ltg` PR description current: it links every issue the cycle fixes (the same `[repo#N]` links as the CHANGELOG).
 - Sort `dot.aspell.en.pws`: `cat dot.aspell.en.pws | (sed -u 1q; sort) | sponge dot.aspell.en.pws` <!-- hint by https://stackoverflow.com/a/56151840/873282 -->
 
 ### Testing
@@ -231,7 +232,7 @@ ejslint.cmd c:\git-repositories\latextemplates\generator-latex-template\generato
    Use [release-it](https://www.npmjs.com/package/release-it) (do not create a release on GitHub) and [github-release-from-changelog](https://www.npmjs.com/package/github-release-from-changelog).
 
    - `npx release-it`
-   - `npx github-release-from-changelog`
+   - `GITHUB_TOKEN=$(gh auth token) npx github-release-from-changelog` (Git Bash; it needs a GitHub token, which the logged-in `gh` CLI provides)
 5. On `main`, run `scripts/end-new-cycle.sh`, then **squash-merge** each template's "Update LTG" PR once it is green.
 
 ## License
@@ -241,6 +242,7 @@ See [benbalter/talks#15](https://github.com/benbalter/talks/issues/15#issuecomme
 
 - `generators/app/templates/splncs04nat.bst` is taken from [tpavlic/splncs04nat](https://github.com/tpavlic/splncs04nat) and is MIT-licensed.
 - `generators/app/templates/logos/`: This directory contains logos, which have special licenses.
+- `generators/app/templates/figures/ulm-minster.jpg` is [Landappbw 79389 1820 Ulmer Münster Ulm.jpg](https://commons.wikimedia.org/w/index.php?curid=131463041) by wkrauth, dedicated to the public domain under [CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/).
 
 [hyperref]: https://ctan.org/pkg/hyperref
 [listings]: https://ctan.org/pkg/listings

package/generators/app/CLAUDE.md

@@ -0,0 +1,113 @@
+<!-- Loaded automatically when Claude works on files under generators/app/. Moved from the repository root CLAUDE.md. -->
+
+## Adding a package or example (wire every place, or a variant silently drops it)
+
+The generated document is assembled from micro-templates; a new LaTeX package or
+example section has to be wired in **lockstep** across several files. Miss one and
+the feature vanishes for some switch combination without any error.
+
+1. **Content** — add/extend `generators/app/templates/<name>.example.<lang>.tex`
+   (the demo body) and/or `<name>.preamble.<lang>.tex` (the `\usepackage`). Example
+   bodies use the `<%- bexample %> … <%- eexample %>` convention (=
+   `\begin{ltgexample}…\end{ltgexample}`), which **runs the body in place and echoes
+   its own source lines** — it is *not* the old `latexdemo`/`\PrintDemo`. Most examples
+   are a single shared `.en` file included from both mains. Give each feature its **own**
+   `<feature>.preamble.<lang>.tex` (one concern per file — e.g. `tikz.preamble`,
+   `longtable.preamble`, `uml.plantuml.preamble`), **not** a catch-all "examples" preamble.
+   **Config vs. demo:** a package a feature needs to *work* belongs in that feature's
+   config preamble and is loaded wherever the feature is on; a package that only *renders
+   a demo* is the example's own concern. So `\mathbb` (a real feature) is provided by
+   `math.preamble.en.tex` — `\@ifundefined{mathbb}{\usepackage{amssymb}}{}`, guarded
+   because `amssymb` clashes with `mathdesign`/`newtxmath`/`unicode-math` — and the math
+   *example* is then gated to where `math.preamble` is included (`isThesis ||
+   feature.abbreviations`), so LNCS etc. don't reference an undefined `\mathbb`.
+2. **Wire the includes into `main.en.tex` AND `main.de.tex`.** Example includes go in
+   the `LaTeX Hints` chapter (the whole chapter is already guarded by
+   `<% if (examples) %>`); package loads go in the preamble area. Guard each with the
+   right condition (`isThesis`, a switch value, …) — and gate an example to where the
+   config that makes it compile is present.
+3. **`Texlivefile`** — add the TeX Live package name, guarded (usually
+   `githubpublish || <condition>`; `githubpublish` deliberately bundles everything).
+4. **Shell-escape is derived, never hardcoded.** It is the boolean
+   `requiresShellEscape` in `index.js` (`listings == "minted" || uml == "plantuml"`).
+   Extend that expression if the new package needs `\write18`; the `latexmkrc` and the
+   `main.*.tex` editor hints read the flag.
+5. **New user switch?** Decide **prompt vs. plain flag** first:
+   - A **prompt** in `options.js` (scope with `when()`, give a `default`) is interactive
+     and nice for discovery — but **every** template's `update-files.yml` that satisfies
+     its `when()` must pass the flag (like `--todo`), or the non-interactive `yo` run in CI
+     blocks on the prompt and fails. So a thesis-only prompt (e.g. `uml`) means
+     `scientific-thesis-template` *and* `uni-stuttgart-dissertation-template` need
+     `--uml=…` added to their (template-managed) `update-files.yml`.
+   - A **plain CLI flag** read from `this.options` in `index.js` with a default (e.g.
+     `longtable`) never prompts, so it never breaks CI and needs no `update-files.yml`
+     change — at the cost of interactive discovery.
+   Either way default it in `index.js` (prompt: `if (!this.props.x) this.props.x = "none";`
+   / flag: read `this.options.x` with a fallback), and if it's a prompt add the axis to
+   `__tests__/matrix.js` **and** the list in `.github/generate-workflows.py` (kept in
+   sync). Model on the `todo` / `uml` (prompt) and `longtable` (flag) options.
+6. **Not in TeX Live** (e.g. `tikz-uml`) — guard usage with
+   `\IfFileExists{<pkg>.sty}{…}{…}` so a plain `npx`/submodule-less generation still
+   compiles (it just skips the demo). Provide the package via a git submodule +
+   `TEXINPUTS` (in `latexmkrc`) and a recursive checkout in the generated `check.yml`,
+   and document the setup in `README.en.md`. External-tool packages (PlantUML needs
+   Java) also need the tool installed in `check.yml` and `--shell-escape`.
+
+**Verify (LaTeX-free first, then compile):** `npx ejs-lint <file>` on every changed
+EJS template; run **`npm test`**, not `node --test` directly — `npm test`'s `pretest`
+runs `eslint .` (incl. `prettier`), which `node --test` skips, so a prettier-only nit
+in `index.js`/`options.js` passes locally but fails CI (run `npx eslint --fix .` to
+match the formatter). `npm test` is the pairwise suite; `npm run test:all` is the full
+matrix. Then generate locally with the **exact** `update-files.yml` flags (a missing
+required option such as `acmformat` or `todo` drops you into an interactive prompt,
+which reads as a hang) and grep the output. Sanity-compile new `.tex` in a *minimal
+standalone* document (the full thesis pulls in packages a local TeX Live may lack);
+`perl -c` the generated `latexmkrc`; validate the generated `check.yml` as YAML. The
+`check-make.yml` build also runs `make format` (latexindent) + `git diff --exit-code`,
+so generated output must already be latexindent-clean — column-aligned tables in
+particular (see `lookForAlignDelims` in `localSettings.yaml`).
+
+### EJS whitespace: `-%>` eats the trailing newline
+
+Almost every control tag ends with `-%>` (the EJS "newline slurp"): `<% if (…) { -%>`,
+`<% } -%>`, `<% switch/case/break … -%>`, and `<%- include('…', this); -%>`. That slurp
+is deliberate — it keeps the control flow (and the include statements themselves) from
+emitting stray blank lines into the generated `.tex`. A plain `<% } %>` (no dash) leaves
+its newline and can inject an unwanted blank line, so the convention is the dashed form;
+only use plain `%>` when you actually want that newline.
+
+The consequence (and a real footgun): **the blank-line layout of the output is not the
+layout of the source.** Because `-%>` eats one trailing newline, two adjacent
+`-%>`-terminated blocks/includes render with **no** blank line between them. To get a
+blank line between blocks you need one of:
+- the first block's file to **end with a trailing blank line** (how most
+  `*.preamble.*.tex` separate themselves — e.g. `font.preamble` ends with a blank line
+  then `<% } -%>`), **or**
+- an **explicit blank line in the source** between the two `-%>` tags (the `-%>` eats one
+  newline, the remaining one + the content's own trailing newline = a blank line).
+
+This is exactly the `nowidow` bug: it followed `microtype.preamble`, which does *not* end
+with a trailing blank, and the include `-%>` ate the source newline — so the block butted
+against microtype until an explicit blank line was added between the two includes. When a
+generated block is missing/extra a blank line, this slurp interaction is the first thing
+to check.
+
+### Compile gotchas the single-variant local test misses
+
+`npm test` only checks that the generator *generates*; the **multi-variant template
+builds** (each `update-ltg` PR compiles every `main*.tex` for both languages and several
+formats) catch things a single local `yo` + compile does not. Two that have bitten:
+
+- **Two-column layouts can't use `longtable`** ("longtable not in 1-column mode"). IEEE and
+  the ACM `sigconf`/`sigplan`/`acmtog` formats are two-column, so any `longtable` (or other
+  one-column-only) example must be gated on `!twocolumn` (a derived prop in `index.js`:
+  `documentclass == "ieee" || (acmart && acmformat ∈ {acmtog,sigconf,sigplan})`). Single-column
+  figures (`figure`, not `figure*`) are fine in two columns.
+- **A template repo ships ONE shared `abbreviations.tex`** — the `update-files.yml` "Prepare
+  files" step keeps only one variant's copy (e.g. the `en`+minted one), and **every** main
+  file (English *and* German) does `\input{abbreviations}`. So a glossary entry used by any
+  language's example must be defined in **both** `abbreviations.en.tex` and
+  `abbreviations.de.tex` (the unused one just never appears in that document's list). Making
+  `\gls` entries language-exclusive breaks the other language's variant with
+  "Glossary entry `…' has not been defined". The same single-shared-file logic applies to
+  other `this.fs.copy`'d siblings (`commands.tex`, …).

package/generators/app/index.js

@@ -348,6 +348,14 @@ export default class extends Generator {
       );
     }
 
+    // Photo for the JPEG example in floats.example.*.tex (CC0, see README)
+    if (this.props.examples) {
+      this.fs.copy(
+        this.templatePath("figures/ulm-minster.jpg"),
+        this.destinationPath("figures/ulm-minster.jpg"),
+      );
+    }
+
     if (this.props.language === "de" && !this.props.githubpublish) {
       this.fs.copyTpl(
         this.templatePath("README.de.md"),

package/generators/app/templates/README.en.md

@@ -372,6 +372,24 @@ In case you think, a package needs to be altered or added, feel free to open an
 - Edit [paper.tex](paper.tex).
 - `latexmk paper`.
 
+## Using the template for a THU term paper
+
+Technische Hochschule Ulm (THU) bases its term paper template on the IEEE conference template.
+To follow the THU requirements (as of the THU template v1.0 of 2023-09-23 by Markus Goldstein):
+
+- Enable page numbers: uncomment `\pagestyle{plain}` after `\maketitle`.
+- Use the THU affiliation in the author block:
+
+  ```latex
+  \author{\IEEEauthorblockN{Given Name Surname}
+  \IEEEauthorblockA{\textit{Department of Computer Science} \\
+  \textit{Ulm University of Applied Sciences (THU)}\\
+  Ulm, Germany \\
+  youremail@thu.de}}
+  ```
+
+Everything else (A4 paper, numeric citations with `natbib` and `IEEEtranN`, `\citet`, links without colored boxes) is already set up.
+
 ## Attention regarding `compsocconf`
 
 Some conferences distribute a `IEEEtran.cls` V1.7a dated 2007 and a parameter `compsocconf`.
@@ -652,6 +670,13 @@ The author of the class offers a large FAQ at <http://www.michaelshell.org/tex/i
 Please read on there.
 The other possibility is to execute `texdoc ieeetran` and read in the documentation.
 For example, there is an explanation of how to typeset the affiliation information with four or more authors properly.
+
+### Q: How are the two columns of the last page balanced?
+
+The [flushend](https://ctan.org/pkg/flushend) package balances them automatically; no command in the text is needed.
+An `\AtEndDocument` hook in the preamble (right after `\usepackage{flushend}`) activates flushend for the last page and, when the text ends in the first column, ends that column, so that flushend distributes the text over both columns.
+If you do not want balanced columns, remove `\usepackage{flushend}` together with that hook.
+If flushend produces odd spacing on the last page (IEEEtran's author warns about that for references), balance by hand instead: remove flushend and enable `\IEEEtriggeratref{N}` in front of `\bibliographystyle`, which starts a new column before reference `N`.
 <% break; case "ustutt": -%>
 
 ### Q: How to rename `thesis-example.tex`?

package/generators/app/templates/Texlivefile

@@ -235,6 +235,9 @@ nowidow
 ntheorem
 <% } -%>
 paralist
+<% if (githubpublish || twocolumn) { -%>
+pdfcol<%# required by the tcolorbox library "breakable" (example boxes in two-column documents) %>
+<% } -%>
 pdfcomment
 pdfescape
 <% if (githubpublish || isThesis) { -%>
@@ -253,8 +256,8 @@ placeins
 <% if (githubpublish || (uml == "plantuml")) { -%>
 plantuml<%# plantuml.sty for the PlantUML UML example; the diagram also needs an external PlantUML install %>
 <% } -%>
-<% if ((documentclass == 'acmart') || (documentclass == 'ieee')) { -%>
-preprint<%# this includes balance%>
+<% if (documentclass == 'acmart') { -%>
+preprint<%# this includes balance, used by the acmart option "balance"%>
 <% } -%>
 <% if (githubpublish || isThesis) { -%>
 psnfss<%# provides pifont%>
@@ -290,7 +293,7 @@ soulpos
 spelling
 <% } -%>
 stringenc
-sttools<%# this includes stfloats; at least required by acmart, ieee, lncs, ustutt, scientific-thesis %>
+sttools<%# this includes stfloats (at least required by acmart, ieee, lncs, ustutt, scientific-thesis) and flushend (ieee: balances the columns on the last page) %>
 subfig
 svn-prov<%# at least required by acmart, ustutt, scientific-thesis%>
 <% if (githubpublish || isThesis) { -%>

package/generators/app/templates/cleveref.example.en.tex

@@ -17,7 +17,7 @@ Cleveref demonstration: Cref at beginning of sentence, cref in all other cases.
     Heading1 & Heading2 \\
     \midrule
     One      & Two      \\
-    Thee     & Four     \\
+    Three    & Four     \\
     \bottomrule
   \end{tabular}
   \caption{Example table for cref demo}

package/generators/app/templates/diagbox.example.en.tex

@@ -1,14 +1,15 @@
+<%# Keep the first cell of the table short: latexindent pads the first cell of every row to its width, and the echoed code has to fit a narrow column (IEEE, ACM). -%>
 <%- bexample %>
-% Source: https://tex.stackexchange.com/a/468994/9075
+% Adapted from https://tex.stackexchange.com/a/468994/9075
 \begin{<% if (documentclass == 'ieee') { %>figure<% } else { %>table<% } %>}
   \caption{Table with diagonal line}
   \label{tab:diag}
   \begin{center}
     \begin{tabular}{|l|c|c|}
       \hline
-      \diagbox[width=10em]{Diag \\Column Head I}{Diag Column\\Head II} & Second & Third \\
+      \diagbox{Row}{Column} & A & B \\
       \hline
-                                                                       & foo    & bar   \\
+      1                     & x & y \\
       \hline
     \end{tabular}
   \end{center}

package/generators/app/templates/dot.aspell.conf

@@ -1,5 +1,6 @@
 add-tex-command "minted options" ppppppppppppppppppppppp
 add-tex-command @ifundefined pppppp
+add-tex-command AtEndDocument p
 add-tex-command Cref p
 add-tex-command DeclareFontFamily ppp
 add-tex-command DeclareFontShape pppppp

package/generators/app/templates/dot.aspell.en.pws

@@ -1,4 +1,4 @@
-personal_ws-1.1 en 132 utf-8
+personal_ws-1.1 en 138 utf-8
 ACM
 Atlantic
 BPEL
@@ -26,13 +26,17 @@ OMG
 ORCID
 OldStyle
 Organization
+PNG
 Practitioner
 RDBMS
 RGB
+ScienceOS
 TODOs
 Textfarbe
 Treaty
 UML
+Ulm
+Wikimedia
 Worten
 Zcref
 abbreviationdot
@@ -47,6 +51,7 @@ basewidth
 basicstyle
 bei
 belowskip
+breakatwhitespace
 breaklines
 category
 cls
@@ -125,6 +130,7 @@ tion
 tt
 werden
 wird
+wkrauth
 wurde
 xleftmargin
 zcref

package/generators/app/templates/dot.textlintrc.json

@@ -4,7 +4,7 @@
   },
   "filters": {
     "allowlist": {
-      "allow": ["/\\bonly\\b/i"]
+      "allow": ["/\\bonly\\b/i", "/\\bFinally,/"]
     }
   },
   "rules": {

package/generators/app/templates/floats.example.de.tex

@@ -10,6 +10,17 @@
   \label{fig:label}
 \end{figure}
 <%- eexample %>
+
+Fotos im JPEG- oder PNG-Format werden genauso eingebunden, wie <%- cref %>{fig:jpg} zeigt.
+
+<%- bexample %>
+\begin{figure}
+  \centering
+  \includegraphics[width=.5\linewidth]{figures/ulm-minster.jpg}
+  \caption{Ulmer Münster. Foto: wkrauth, CC0, via Wikimedia Commons.}
+  \label{fig:jpg}
+\end{figure}
+<%- eexample %>
 <%- include('floatflt.example.en.tex', this); -%>
 <% if (documentclass == 'ieee') { -%>
 

package/generators/app/templates/floats.example.en.tex

@@ -13,6 +13,17 @@
   \label{fig:label}
 \end{figure}
 <%- eexample %>
+
+Photos in JPEG or PNG format are included the same way, as shown in <%- cref %>{fig:jpg}.
+
+<%- bexample %>
+\begin{figure}
+  \centering
+  \includegraphics[width=.5\linewidth]{figures/ulm-minster.jpg}
+  \caption{Ulm Minster. Photo: wkrauth, CC0, via Wikimedia Commons.}
+  \label{fig:jpg}
+\end{figure}
+<%- eexample %>
 <%- include('floatflt.example.en.tex', this); -%>
 <% if (documentclass == 'ieee') { -%>
 

package/generators/app/templates/hyphenation.example.en.tex

@@ -7,16 +7,15 @@ Here are some hints:
 
 <%- bexample %>
 In case you write <%- bquote %>application-specific<%- equote %>, then the word will only be hyphenated at the dash.
-You can also write \verb1applica\allowbreak{}tion-specific1 (result: applica\allowbreak{}tion-specific), but this is much more effort.
+You can also insert \verb1\allowbreak{}1 into the word, as in applica\allowbreak{}tion-specific, but this is much more effort.
 
 <% if (tweakouterquote == "outerquote")  { -%>
 In the net, you will read about that one can use a normal quote sign followed by an equal sign (\verb1"=1) to specify that hyphenation is allowed at other places in the word.
 Since we use the quote sign for automatic quotation, this is not possible anymore.
-Please use the command \verb1\hydash1 for the same purpose.
-Example: \verb1application\hydash specific1 (result: application\hydash specific).
+Please use the command \verb1\hydash1 for the same purpose, as in application\hydash specific.
 <% } else { -%>
 You can now write words containing hyphens which are hyphenated at other places in the word.
-For instance, \verb1application"=specific1 gets application"=specific.
+For that, write \verb1"=1 instead of \verb1-1, as in application"=specific.
 This is enabled by an additional configuration of the babel package.
 <% } -%>
 <%- eexample %>

package/generators/app/templates/latexmkrc

@@ -7,14 +7,34 @@ $pdflatex = '<%= reallatexcompiler %> <% if (requiresShellEscape) { %>--shell-es
 $ENV{'TEXINPUTS'} = './tikz-uml//:' . ($ENV{'TEXINPUTS'} // '');
 <% } -%>
 
-#Use SumatraPDF instead of the default PDF viewer
-$pdf_previewer = 'start "C:\Program Files\SumatraPDF\SumatraPDF.exe"';
+#------------------------------------------------------------------------------#
+# compilation
 
-#SumatraPDF updates automatically
+# automatically call lualatex/pdflatex (instead of latex)
+$pdf_mode = 1;
+
+# replaces main.pdf by jobname.pdf
+# Note: -pvc may then not find the PDF.
+#$jobname = 'thesis';
+
+#------------------------------------------------------------------------------#
+# preview
+# You may put these settings in ~/.latexmkrc instead.
+
+# >0 <-> equivalent to -pv
 $preview_mode = 0;
+# >0 <-> equivalent to -pvc
+#$preview_continuous_mode = 1;
 
-#automatically call lualatex/pdflatex (instead of latex)
-$pdf_mode = 1;
+if ($^O eq 'MSWin32') {
+  # Use SumatraPDF instead of the default PDF viewer; it reloads the PDF automatically
+  $pdf_previewer = 'start "C:\Program Files\SumatraPDF\SumatraPDF.exe"';
+}
+# 'evince' is 'Document Viewer' (GNOME's default)
+#$pdf_previewer = 'evince';
+
+#------------------------------------------------------------------------------#
+# bibliography and glossaries
 
 # enable deletion of *.bbl when calling "latexmk -c"
 $bibtex_use = 2;
@@ -33,6 +53,9 @@ sub run_makeglossaries {
   };
 }
 
-#remove more files than in the default configuration
+#------------------------------------------------------------------------------#
+# cleanup
+
+# remove more files than in the default configuration
 @generated_exts = qw(acn acr alg aux code fls glg glo glo-abr gls glsdefs idx ind ist lof lol lot out run.xml synctex thm toc tpt upa upb wrt);
 $clean_ext .= ' %R.ist %R.xdy';

package/generators/app/templates/listings.example.de.tex

@@ -15,8 +15,8 @@
 \end{lstlisting}
 <%- eexample %>
 
-Der zusätzliche Paramter \verb+float+ führt dazu, dass das Listing auch floated.
-<%- Cref %>{lst:flXML} zeigt das gleitendede Listing.
+Der zusätzliche Parameter \verb+float+ führt dazu, dass das Listing auch floated.
+<%- Cref %>{lst:flXML} zeigt das gleitende Listing.
 
 <%- bexample %>
 \begin{lstlisting}[
@@ -62,3 +62,7 @@ public class Hello {
 }
 \end{lstlisting}
 <%- eexample %>
+<% if (isThesis) { -%>
+
+<%- include('listings.long.example.en.tex', this); -%>
+<% } -%>

package/generators/app/templates/listings.example.en.tex

@@ -62,3 +62,7 @@ public class Hello {
 }
 \end{lstlisting}
 <%- eexample %>
+<% if (isThesis) { -%>
+
+<%- include('listings.long.example.en.tex', this); -%>
+<% } -%>

package/generators/app/templates/listings.long.example.en.tex

@@ -0,0 +1,75 @@
+Listings longer than the remaining space continue on the next page if they are \emph{not} floating.
+A floating listing is always placed on a single page.
+<%- Cref %>{lst:long} spans multiple pages.
+
+\begin{lstlisting}[
+  language=Java,
+  caption={Long Java listing spanning multiple pages},
+  label={lst:long}]
+public class Squares {
+
+    /** Returns the square of 1. */
+    public int square1() {
+        return 1 * 1;
+    }
+
+    /** Returns the square of 2. */
+    public int square2() {
+        return 2 * 2;
+    }
+
+    /** Returns the square of 3. */
+    public int square3() {
+        return 3 * 3;
+    }
+
+    /** Returns the square of 4. */
+    public int square4() {
+        return 4 * 4;
+    }
+
+    /** Returns the square of 5. */
+    public int square5() {
+        return 5 * 5;
+    }
+
+    /** Returns the square of 6. */
+    public int square6() {
+        return 6 * 6;
+    }
+
+    /** Returns the square of 7. */
+    public int square7() {
+        return 7 * 7;
+    }
+
+    /** Returns the square of 8. */
+    public int square8() {
+        return 8 * 8;
+    }
+
+    /** Returns the square of 9. */
+    public int square9() {
+        return 9 * 9;
+    }
+
+    /** Returns the square of 10. */
+    public int square10() {
+        return 10 * 10;
+    }
+
+    /** Returns the square of 11. */
+    public int square11() {
+        return 11 * 11;
+    }
+
+    /** Returns the square of 12. */
+    public int square12() {
+        return 12 * 12;
+    }
+
+    public static void main(String[] args) {
+        System.out.println(new Squares().square12());
+    }
+}
+\end{lstlisting}

package/generators/app/templates/longtable.example.en.tex

@@ -1,7 +1,7 @@
 <%= heading2 %>{Tables spanning multiple pages}
 
 The \href{https://ctan.org/pkg/longtable}{longtable} package typesets tables that automatically break across page boundaries.
-The header (\verb+\endhead+) and footer (\verb+\endfoot+) rows are repeated on every page; once enough rows are added, the table spans several pages on its own.
+The header (\verb+\endhead+) and footer (\verb+\endfoot+) rows are repeated on every page; once enough rows are added, the table spans more than one page on its own.
 
 <%- bexample %>
 \begin{longtable}{|l|l|l|}