Hot

Here is the look of the template and the preamble has a lot of parts in it that I do not know exactly which part I should include here Any advice on how to do that? Here is a link to the poster template https://www.overleaf.com/project/69e151706bf3d752d1c5d88e

I want to reduce the line spacing within an item or items. In example 2, \setstretch{1} has a side effect that the vertical space between the first item and its preceding text (2A) is also narrowed (compare with 1A without the command). Strangely, the space between the last item and its following text remains the same (1B and 2B). In other words, \setstretch{1} command affects the space between the first item and its preceding text. Shouldn't it be independent from the line spacing command? (enumitem package manual on page 3 says that the space before the first item depends on \topsep + \parskip [+ \partopsep] which is the same as the space after the last item.) How can I make the two spaces (1A and 2A) same while using \setstretch{1} command? Or, is there any other valid solution for this? (Of course, I know a not-a-beautiful one that I can manually add a space.) Here is the example code: % !TeX encoding = UTF-8 % !TeX spellcheck = en_US % !TeX TS-program = lualatex % !TeX TXS-program:bibliography = txs:///biber \documentclass[letterpaper,10pt]{article} \usepackage{setspace} \usepackage{enumitem} \begin{document} \setstretch{2} I want to reduce the line spacing within an item or items. In example 2, {\ttfamily\textbackslash{setstretch\{1\}}} has a side effect that the vertical space between the first item and its preceding text (2A) is also narrowed (compare with 1A without the command). Strangely, the space between the last item and its following text remains the same (1B and 2B). In other words, {\ttfamily\textbackslash{setstretch\{1\}}} command affects the space between the first item and its preceding text. Shouldn't it be independent from the line spacing command? ({\ttfamily{enumitem}} package manual on page 3 says that the space before the first item depends on {\ttfamily{{\textbackslash}topsep + {\textbackslash}parskip [+ {\textbackslash}partopsep]}} which is the same as the space after the last item.) \noindent Example 1: \begin{itemize} \item This is a very long item, which has more than one line. This is a very long item, which has more than one line. \item This is a very long item, which has more than one line. This is a very long item, which has more than one line. \end{itemize} This is the end of example 1. \noindent Example 2 with {\ttfamily\textbackslash{setstretch\{1\}}} command: %\vspace*{0.5\baselineskip} %I don't like this. \begin{itemize} \setstretch{1} \item This is a very long item, which has more than one line. This is a very long item, which has more than one line. \item This is a very long item, which has more than one line. This is a very long item, which has more than one line. \end{itemize} This is the end of example 2. How can I make the two spaces same while using {\ttfamily\textbackslash{setstretch\{1\}}} command? Or, is there any other valid solution for this? (Of course, I know a not-a-beautiful one that I can manually add a space.) \end{document}

I'm using (thanks to egreg for his advise) \documentclass{article} \usepackage{enotez} \usepackage{xurl} \usepackage{hyperref} \begin{document} This is for test\endnote{“General Election: Trump vs. Biden,” RealClear Politics, accessed June 24, 2021, \url{https://www.realclearpolitics.com/epolls/2020/president/us/general_election_trump_vs_biden-6247.html#polls}.} \printendnotes \end{document} It works fine with PDFLaTeX but doesn't with XeLaTeX, can anyone advise how to achieve this with XeLaTeX? Please Either the usage of enotez or endnotes, both are fine for me

I am rendering chemical equations to PDF and SVG using LaTeX. I need the page size to exactly match the size of the equation (no extra margins). I am using the standalone class with border=0pt. My code: \documentclass[12pt, border=0pt]{standalone} \usepackage[version=4]{mhchem} \usepackage{lua-visual-debug} % to visualize boundaries \begin{document} \ce{HPO3 ->[][A] Na3P3O9, Na3PO4} \end{document} What happens: I expect the bottom page boundary to run exactly along the bottom edge of the letter "A" (which is placed below the arrow). The actual boundary is lower — exactly where an invisible kern ends (the yellow rectangle shown by lua-visual-debug). This kern is not visible without debug, but standalone takes it into account when calculating the page size. How can I force standalone to ignore this unwanted kern, or to crop the page strictly to the visible elements (in this case, to the letter "A")? In my case, these equations will be embedded into the text on a website, so even a few points of difference matter.

I'm trying to stylize the mathematical fraction in such a way that both the numerator and the denominator will automatically shrink to roughly fit the line height and preferably the digits will be expanded horizontally to occupy more horizontal space. Being away from the TeX for the last 2-3 years I've consulted an AI-assistent first and it suggested using the afrc (Alternative Fractions) and the font Adobe Caslon Pro which it said supported the afrc but that didn't work out and I gave up asking the AI. "Almost" MWE \documentclass{article} \usepackage{fontspec} \defaultfontfeatures{Ligatures={TeX,Common}} \setmainfont{Adobe Caslon Pro}[] % it's installed on my system \begin{document} gimme {\addfontfeatures{RawFeature=+afrc}1/10} of your money % afrc -> Alternative Fractions \end{document}

I am asked to produce a document where a figure caption is placed above the figure, and left-aligned (even though it is just a one-line caption). By using the subcaption package and the \captionsetup command it works fine when the figure contains only one image. However, when the figure contains several sub-figures, the sub-captions are always left-aligned, like the main caption. I would like to have the main caption left-aligned but the sub-captions (which are very short) centred below each sub-figure. The following MWE illustrates the problem. Figure 1 is the standard. Figures 2 and 3 have the main caption left-aligned as required, but also the sub-captions come out left-aligned. \documentclass{article} \usepackage[document]{ragged2e} % For left-aligned (ragged right) text \usepackage{subcaption} \usepackage{graphicx} \usepackage{lipsum} \begin{document} \lipsum[66] \begin{figure}[h] \caption{Centered caption above figure} \label{fig:f01} \centering \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{1st}\label{subfig:1st}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{2nd}\label{subfig:2nd}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{3rd}\label{subfig:3rd}\end{subfigure} \end{figure} \lipsum[66] \begin{figure}[h] \captionsetup{singlelinecheck=off,justification=raggedright} \caption{Left-aligned caption above left-aligned figure} \label{fig:f02} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{1st}\label{subfig:1stb}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{2nd}\label{subfig:2ndb}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{3rd}\label{subfig:3rdb}\end{subfigure} \end{figure} \lipsum[66] \begin{figure}[h] \captionsetup{singlelinecheck=off,justification=raggedright} \caption{Left-aligned caption above centered figure} \label{fig:f03} \centering \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{1st}\label{subfig:1stc}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{2nd}\label{subfig:2ndc}\end{subfigure} \begin{subfigure}{0.30\textwidth}\includegraphics[width=\textwidth]{example-image-duck}\caption{3rd}\label{subfig:3rdc}\end{subfigure} \end{figure} \end{document} Thank you for your suggestions. Folco

I am using VS Code with LaTeX Workshop and LTeX+ for spell checking. LTeX+ generates by default a ton of info messages like this: I would like for it to stop doing this. Here it is explained that a solution is to add "ltex.diagnosticSeverity": "hint" to the settings.json file. Nonetheless, as it is explained in the documentation, this makes any spotted spelling error not be underlined and rather only subtly marked. I would like for the errors in my code to still be underlined with a squiggly line (like with the default "ltex.diagnosticSeverity": "information" value). How could I achieve this?

What I want to replicate originally is something as below: Now my key point is the arrow of the following style, similar to the single arrow shape in shapes.arrows: \documentclass[tikz,border=5pt]{standalone} \usetikzlibrary{arrows.meta,positioning,shapes.arrows,decorations.markings} \begin{document} \begin{tikzpicture}[ node distance=2cm and 1cm, shrink/.style={shorten >=#1cm,shorten <=#1cm}, myarrow/.style={ shrink=.75,thick,-Stealth, postaction=decorate, decoration={ markings,mark=at position .5 with { \draw[shrink=0,-] (-10pt,-10pt) -- (10pt,10pt); } } }, mysinglearrow/.style={ shape=single arrow,minimum height=1.5cm,inner sep=3pt,draw,line width=1.2pt, } ] \node[draw] (betaII) {AAAAAAAA}; \node[draw] (betaI)[below left=of betaII]{BBBBBBBBB}; \node[draw] (normal)[below right=of betaII]{CCCCCCCCC}; \draw[myarrow] (betaII.west) -- (betaI.north); \draw[myarrow] (normal.north) -- (betaII.east); \draw[myarrow] (betaI) -- (normal); \node[mysinglearrow,rotate=45] at (-1.75,-1.5) {}; \end{tikzpicture} \end{document} However, that is not behave as a "arrow", but a shape. I dislike the syntax: \node[mysinglearrow,rotate=45] at (-1.75,-1.5) {}; Here below is the simplified version, based on the similar solution code here: % Source - https://tex.stackexchange.com/a/662285 \documentclass[tikz,margin=1cm]{standalone} \usetikzlibrary{arrows.meta} \tikzset{ doubleTriangle/.style args={#1 and #2 colored by #3 and #4}{ -Triangle, line width=#1,#3, postaction={ draw, -Triangle,#4, line width=#2, /utils/exec=\pgfmathsetlengthmacro{\doubleTriangleShortenStart}{((#1)-(#2))/2}, /utils/exec=\pgfmathsetlengthmacro{\doubleTriangleShortenEnd}{1.2*(sqrt(3))*((#1)-(#2))}, shorten <=\doubleTriangleShortenStart, shorten >=\doubleTriangleShortenEnd, }, }, } \begin{document} \begin{tikzpicture} \node[draw,below left] at (0,0) {A}; \node[draw,above right] at (5,5) {B}; \draw[doubleTriangle=1cm and 0.7cm colored by black and white] (0,0) -- (5,5); % \draw[doubleTriangle=1cm and 0.7cm colored by black and white,shorten >=.5cm,shorten <=.5cm] (0,0) -- (5,5); \end{tikzpicture} \end{document} which gives: Noted that the arrow's width is not the same. What I was after as an arrow style, is something as below: Any suggestions on how to make more elegant syntax of this arrow style?

This file compiles OK with lualatex using TeX Live 2026 on Linux: \documentclass[12pt]{article} \usepackage{amsmath} \begin{document} \begin{minipage}{\textwidth}\raggedright \textbf{Problem number} : 1\\ \textbf{Problem} : $$\begin{gathered}\begin{aligned} y^{\prime}&=2 x +1\\ y \left(0\right) &= 3\\ \end{aligned} \end{gathered}$$\\ \textbf{Date solved} : \verb|Friday, May 29, 2026 at 12:37:02 AM| \\ \end{minipage} \end{document} And gives PDF But when doing make4ht -ulm default -a debug 5.tex "mathjax,htm" it gives error (/usr/local/texlive/2026/texmf-dist/tex/generic/tex4ht/html5.4ht)) (/usr/local/texlive/2026/texmf-dist/tex/latex/l3backend/l3backend-dvips.def) (./5.aux) ! LaTeX Error: There's no line here to end. Should it not also compile clean using tex4ht? I removed the \\ after the \end{gathered}$$\\ and now tex4ht is happy and does not give error and also PDF output remained the same as before. So I will remove this \\ from my code now. But the question is this: Why does tex4ht complain about \end{gathered}$$\\, but lualatex does not? >which make4ht /usr/local/texlive/2026/bin/x86_64-linux/make4ht

When \wideoverbar is applied to a wide input, e.g., \wideoverbar{\alpha\alpha}, \wideoverbar{\alpha\alpha\alpha}, the bar is visually very snug up against the input, and this looks correct to me. However, when \wideoverbar is applied to a narrow input like \alpha, the depicted bar is raised significantly. I think \wideoverbar looks significantly better than \bar and \overbar in general, and would like to use it on narrow contents for reasons to do with both aesthetics and consistency. So, I am looking to get the behavior of wide inputs with narrow inputs. As some examples, \wideoverbar{\alpha} is spaced poorly, \wideoverbar{\alpha\alpha} is spaced well, \wideoverbar{\alpha.} is spaced well, but \wideoverbar{\alpha\!.} is spaced poorly. \wideoverbar{..} is spaced poorly, but \wideoverbar{...} is spaced well. Evidently, there is some "switch" on the vertical height of the bar which somehow depends on the width of the contents. I am using Lualatex with Unicode math + Libertinus math, in case that is relevant. For reference, here is a minimized compilable example of what I am working with: % !TEX program = lualatex \documentclass{acmart} \begin{document} $\wideoverbar{\iota}$, $\wideoverbar{\iota\iota}$, $\wideoverbar{\iota\iota\iota}$, $\wideoverbar{\iota\iota\iota\iota}$ \end{document} I find the vertical spacing on the right highly preferable. I had previously posted the question on reddit.

I have a macro that uses a minipage environment. Sometimes I need to set the height of the minipage; other times, I want it to have its natural height. I therefore open the minipage thus: \begin{minipage}[c][\minipageheight]{\minipagewidth} where \minipageheight and \minipagewidth are suitable \newcommand definitions. But I cannot find a way to set \minipageheight so that the minipage has its natural height, which requires the call to become: \begin{minipage}[c][]{\minipagewidth} In other words, how do I define \minipageheight so that it expands to an empty argument? I tried \let\minipageheight\empty, and \renewcommand{\minipageheight}{}, but neither works.

Consider the following example: \DocumentMetadata{% tagging = draft % } \documentclass{article} \begin{document} a \newpage \begin{enumerate} \item b \end{enumerate} c \end{document} If I compile this document using latexmk with no .aux file, I get the following error: ! Package tagpdf Error: there is no open structure on the stack Type <return> to continue. ... l.16 ? Notes: Line 16 appears to be the blank line between \end{enumerate} and c. With tagging = on or tagging = off it compiles fine, but tagging = draft yields an error. Using lualatex <filename> directly instead of latexkmk -lualatex <filename> it compiles fine. If there is an .aux file left over from a previous run (like if I run once using tagging=on and then switch to tagging=draft, or if I run once using lualatex and then switch to latexmk -lualatex) it compiles fine. (Using Tex Live, updated as of May 28, 2026, in Windows 11 Enterprise.) Questions: Is this expected behavior? If not, should a report be filed? If so, where? (To latexmk, or the tagging project, or both, or somewhere else?) Work-arounds in case anyone else ever encounters this issue: Evidently there are many ways to avoid it (see items 2, 3, 4 above).

I apologize in advance for submitting no MWE (I cannot think of a way to exactly reproduce the situation); yet, I think the question may have some interest and give occasion, at least, to some hints or theory explanations. I'm using memoir class. I'm in such a situation: I.e.: a very long footnote, whose marker in text happen to be in the last line of the page; but that line is the beginning of a paragraph. That paragraph spans over present pages 54 and 55, and goes on at page 56. Visually, it seems that a line of text could move from the right page to the left page (and a line of the note in the opposite direction) in order to avoid the orphan line. I unsuccesfully tried the following strategies: making \skip\footins smaller, in order to say "hey, you have space for one line of text more!"; putting \nopagebreak at the end of the present last line of text of p. 54 and \pagebreak[4] at the end of the first line of p. 55; the same within footnote text. Can anyone suggest any other approach?

How can I produce a sequence of luadraw frames using a for loop? The usual way I do it with tikz is not working. % Source - https://tex.stackexchange.com/a/755801 % Posted by nidarfp % Retrieved 2026-05-28, License - CC BY-SA 4.0 \documentclass[tikz,border=5pt]{standalone}% compile with lualatex only \usepackage[svgnames]{xcolor} \usepackage[3d]{luadraw}%https://github.com/pfradin/luadraw \usepackage{fourier-otf} %https://tex.stackexchange.com/questions/755458/how-can-you-draw-more-than-three-intersecting-planes-which-are-bounded-by-a-cube \begin{document} \foreach \i in {1,...,24} { \begin{luadraw}{name=intersecting_planes} local g = graph3d:new{ adjust2d=true,bbox=false, viewdir={30,70+\i*360/24} } g:Dboxaxes3d({grid=true,gridcolor="gray",fillcolor="lightgray", drawbox=true}) local style = function(color) return {color=color, scale=1,opacity=0.8} end g:Dscene3d( g:addPlane({Origin,vecK}, style("LightBlue")), g:addPlane({-vecI,vecI+vecK-vecJ/2}, style("Yellow")), g:addPlane({vecJ,vecJ+vecK-vecI/2}, style("Crimson")), g:addPlane({vecI-vecJ,-vecJ}, style("ForestGreen")), g:addPlane({vecK,-vecJ/3+vecK}, style("Navy")), g:addPlane({3*vecI,vecI}, style("Beige")) ) g:Show() \end{luadraw}} \end{document}

On Overleaft I want to create code listings highlited with minted. I managed to do so when using the \documentclass{article} but I'm having trouble with \documentclass{toptesi} which is however what I have to use. \documentclass{toptesi} \usepackage{minted} \begin{document} \begin{listing} \begin{minted}{docker} FROM raw # hello docker \end{minted} \end{listing} \end{document} Simply changing toptesi to article works, but I need it working with toptesi. The error I'm getting is: No verbatim file \ . \FV@Error ... {FancyVerb Error: \space \space #1 } l.8 \ begin{minted}{docker} Your command was ignored. Type <return> to continue.

I'm having trouble with the nomenclature not showing up when all content enters via an \include statement. It seems the nomenclature cannot be compiled independently, but needs some content before it. A minimal not working example is: % main.tex \documentclass{article} \usepackage{nomencl} \makenomenclature \begin{document} % content \include{content} % nomenclature \nomenclature{\(c\)}{Speed of light in a vacuum} \nomenclature{\(h\)}{Planck constant} \printnomenclature \end{document} where content.tex is file with just the word 'test': % content.tex test A minimal working example would be exchanging \include{content} with test. How can I have my nomenclature show up and neatly separate all preceding sections with \include without having to add extraneous content?

The question is similar to this classical one. I followed the following instructions with inkscape and svg2tikz: Procedure: import your bitmap image. vectorize it by Inkscape (potrace algorithm). delete bitmap image. adjust document to content. export it by inkscape2tikz extension. Then, export the svg figure with svg2tikz, it give me the following: \documentclass[tikz]{standalone} \begin{document} \def \globalscale {1.000000} \begin{tikzpicture}[y=1cm, x=1cm, yscale=-\globalscale,xscale=\globalscale, every node/.append style={scale=\globalscale}, inner sep=0pt, outer sep=0pt] \path[fill=black] (8.9, 20.3).. controls (8.8, 20.3) and (8.7, 20.2) .. (8.6, 20.2).. controls (8.6, 20.2) and (8.4, 20.2) .. (8.2, 20.2).. controls (8.1, 20.2) and (7.9, 20.1) .. (7.9, 20.1).. controls (7.8, 20.1) and (7.6, 20.0) .. (7.5, 20.0).. controls (7.4, 20.0) and (7.3, 20.0) .. (7.2, 20.0).. controls (7.2, 19.9) and (7.1, 19.9) .. (7.0, 19.9).. controls (6.8, 19.8) and (6.2, 19.5) .. (6.1, 19.5).. controls (6.1, 19.4) and (6.0, 19.4) .. (6.0, 19.4).. controls (5.9, 19.4) and (5.9, 19.3) .. (5.8, 19.3).. controls (5.8, 19.3) and (5.8, 19.3) .. (5.7, 19.2).. controls (5.7, 19.2) and (5.6, 19.2) .. (5.5, 19.1).. controls (5.4, 19.0) and (5.3, 19.0) .. (5.3, 18.9).. controls (5.1, 18.8) and (4.3, 18.1) .. (4.2, 18.0).. controls (4.2, 18.0) and (4.1, 17.9) .. (4.0, 17.8).. controls (3.9, 17.8) and (3.8, 17.6) .. (3.7, 17.6).. controls (3.6, 17.5) and (3.4, 17.3) .. (3.3, 17.2).. controls (2.7, 16.6) and (2.2, 16.1) .. (1.8, 15.5).. controls (1.7, 15.5) and (1.7, 15.4) .. (1.7, 15.3).. controls (1.6, 15.3) and (1.6, 15.2) .. (1.6, 15.2).. controls (1.5, 15.2) and (1.3, 14.6) .. (1.3, 14.4).. controls (1.3, 14.4) and (1.3, 14.3) .. (1.3, 14.2).. controls (1.2, 14.1) and (1.2, 13.9) .. (1.2, 13.7).. controls (1.2, 13.6) and (1.1, 13.3) .. (1.1, 13.2).. controls (1.1, 13.0) and (1.0, 12.7) .. (1.0, 12.3).. controls (1.0, 12.0) and (1.0, 11.7) .. (1.0, 11.6).. controls (0.9, 10.9) and (1.0, 9.6) .. (1.1, 9.3).. controls (1.1, 9.2) and (1.2, 9.1) .. (1.2, 8.9).. controls (1.2, 8.8) and (1.3, 8.7) .. (1.3, 8.6).. controls (1.3, 8.6) and (1.3, 8.5) .. (1.3, 8.4).. controls (1.4, 8.3) and (1.4, 8.3) .. (1.4, 8.2).. controls (1.4, 8.2) and (1.5, 8.1) .. (1.5, 8.0).. controls (1.5, 7.9) and (1.6, 7.8) .. (1.6, 7.8).. controls (1.6, 7.8) and (1.7, 7.7) .. (1.7, 7.7).. controls (1.7, 7.7) and (1.8, 7.4) .. (1.9, 7.3).. controls (1.9, 7.3) and (2.0, 7.2) .. (2.0, 7.1).. controls (2.1, 7.0) and (2.1, 6.9) .. (2.3, 6.8).. controls (2.4, 6.6) and (2.7, 6.2) .. (2.7, 6.2).. controls (2.8, 6.1) and (2.8, 6.1) .. (2.8, 6.1).. controls (2.8, 6.1) and (3.0, 5.8) .. (3.0, 5.7).. controls (3.1, 5.7) and (3.1, 5.6) .. (3.2, 5.5).. controls (3.3, 5.4) and (3.3, 5.4) .. (3.6, 5.0).. controls (3.7, 4.9) and (3.8, 4.7) .. (3.9, 4.6).. controls (4.0, 4.5) and (4.2, 4.4) .. (4.2, 4.3).. controls (4.4, 4.0) and (4.9, 3.5) .. (5.4, 3.1).. controls (5.5, 3.0) and (5.7, 2.9) .. (5.7, 2.8).. controls (5.9, 2.7) and (6.0, 2.6) .. (6.2, 2.5).. controls (6.2, 2.5) and (6.3, 2.4) .. (6.3, 2.4).. controls (6.3, 2.4) and (6.6, 2.2) .. (6.7, 2.2).. controls (6.7, 2.2) and (6.8, 2.1) .. (6.8, 2.1).. controls (6.8, 2.1) and (6.9, 2.1) .. (7.0, 2.0).. controls (7.1, 2.0) and (7.2, 2.0) .. (7.2, 1.9).. controls (7.3, 1.9) and (7.3, 1.9) .. (7.4, 1.9).. controls (7.4, 1.8) and (7.5, 1.8) .. (7.6, 1.8).. controls (7.6, 1.7) and (7.7, 1.7) .. (7.7, 1.7).. controls (7.7, 1.7) and (7.8, 1.7) .. (7.9, 1.6).. controls (8.0, 1.6) and (8.1, 1.6) .. (8.2, 1.5).. controls (8.3, 1.5) and (8.4, 1.5) .. (8.4, 1.5).. controls (8.4, 1.4) and (8.6, 1.4) .. (8.7, 1.4).. controls (8.9, 1.4) and (9.1, 1.3) .. (9.2, 1.3).. controls (9.3, 1.3) and (9.5, 1.2) .. (9.8, 1.2).. controls (10.0, 1.2) and (10.3, 1.2) .. (10.5, 1.1).. controls (10.8, 1.1) and (11.6, 1.1) .. (12.0, 1.1).. controls (12.2, 1.2) and (12.4, 1.2) .. (12.5, 1.2).. controls (12.6, 1.2) and (12.7, 1.3) .. (12.8, 1.3).. controls (12.8, 1.3) and (12.9, 1.4) .. (13.0, 1.4).. controls (13.1, 1.4) and (13.2, 1.4) .. (13.3, 1.5).. controls (13.3, 1.5) and (13.4, 1.5) .. (13.5, 1.5).. controls (13.6, 1.6) and (13.7, 1.6) .. (13.8, 1.6).. controls (13.8, 1.7) and (13.9, 1.7) .. (14.0, 1.8).. controls (14.4, 1.9) and (14.7, 2.1) .. (14.7, 2.1).. controls (14.7, 2.1) and (14.8, 2.2) .. (14.8, 2.2).. controls (14.9, 2.2) and (15.1, 2.4) .. (15.4, 2.6).. controls (15.6, 2.8) and (16.3, 3.6) .. (16.4, 3.7).. controls (16.5, 3.8) and (16.5, 3.9) .. (16.6, 3.9).. controls (16.7, 4.0) and (16.8, 4.1) .. (16.8, 4.2).. controls (16.8, 4.2) and (16.9, 4.3) .. (16.9, 4.3).. controls (16.9, 4.3) and (16.9, 4.3) .. (16.9, 4.3).. controls (16.9, 4.4) and (17.0, 4.5) .. (17.1, 4.6).. controls (17.1, 4.6) and (17.2, 4.8) .. (17.2, 4.8).. controls (17.3, 4.9) and (17.3, 5.0) .. (17.4, 5.1).. controls (17.5, 5.3) and (17.8, 5.9) .. (17.9, 6.0).. controls (17.9, 6.1) and (17.9, 6.2) .. (18.0, 6.3).. controls (18.0, 6.4) and (18.0, 6.4) .. (18.0, 6.5).. controls (18.0, 6.5) and (18.1, 6.6) .. (18.1, 6.8).. controls (18.2, 6.9) and (18.2, 7.0) .. (18.2, 7.1).. controls (18.2, 7.2) and (18.3, 7.3) .. (18.3, 7.3).. controls (18.3, 7.4) and (18.3, 7.5) .. (18.4, 7.6).. controls (18.4, 7.7) and (18.4, 7.9) .. (18.4, 8.0).. controls (18.6, 8.4) and (18.6, 10.2) .. (18.5, 10.9).. controls (18.4, 11.3) and (18.4, 11.5) .. (18.4, 12.2).. controls (18.3, 12.5) and (18.3, 12.9) .. (18.3, 13.1).. controls (18.3, 13.3) and (18.2, 13.6) .. (18.2, 13.7).. controls (18.2, 13.9) and (18.2, 14.1) .. (18.1, 14.2).. controls (18.1, 14.4) and (18.1, 14.5) .. (18.1, 14.6).. controls (18.0, 14.7) and (18.0, 14.8) .. (18.0, 14.9).. controls (17.9, 15.0) and (17.9, 15.1) .. (17.9, 15.2).. controls (17.9, 15.3) and (17.8, 15.4) .. (17.8, 15.5).. controls (17.8, 15.5) and (17.7, 15.6) .. (17.7, 15.6).. controls (17.7, 15.7) and (17.7, 15.8) .. (17.7, 15.8).. controls (17.6, 15.9) and (17.6, 16.0) .. (17.6, 16.0).. controls (17.6, 16.1) and (17.5, 16.2) .. (17.5, 16.2).. controls (17.5, 16.2) and (17.4, 16.3) .. (17.4, 16.4).. controls (17.4, 16.5) and (17.3, 16.6) .. (17.3, 16.6).. controls (17.3, 16.7) and (17.2, 16.7) .. (17.2, 16.8).. controls (17.2, 16.8) and (17.2, 16.9) .. (17.2, 16.9).. controls (17.1, 17.0) and (17.0, 17.1) .. (17.0, 17.2).. controls (16.9, 17.3) and (16.8, 17.4) .. (16.8, 17.4).. controls (16.8, 17.4) and (16.8, 17.5) .. (16.7, 17.6).. controls (16.6, 17.7) and (16.1, 18.2) .. (16.1, 18.2).. controls (16.0, 18.2) and (16.0, 18.3) .. (15.9, 18.3).. controls (15.9, 18.4) and (15.8, 18.4) .. (15.8, 18.4).. controls (15.7, 18.5) and (15.7, 18.5) .. (15.6, 18.5).. controls (15.6, 18.5) and (15.6, 18.6) .. (15.5, 18.6).. controls (15.5, 18.6) and (15.4, 18.7) .. (15.4, 18.7).. controls (15.4, 18.7) and (15.3, 18.8) .. (15.1, 18.8).. controls (15.0, 18.9) and (14.9, 18.9) .. (14.8, 19.0).. controls (14.6, 19.0) and (14.5, 19.1) .. (14.5, 19.1).. controls (14.5, 19.1) and (14.4, 19.1) .. (14.3, 19.2).. controls (14.3, 19.2) and (14.2, 19.2) .. (14.2, 19.2).. controls (14.1, 19.2) and (14.1, 19.3) .. (14.0, 19.3).. controls (13.9, 19.3) and (13.8, 19.4) .. (13.7, 19.4).. controls (13.6, 19.4) and (13.6, 19.4) .. (13.5, 19.5).. controls (13.5, 19.5) and (13.4, 19.5) .. (13.3, 19.5).. controls (13.3, 19.6) and (13.2, 19.6) .. (13.1, 19.6).. controls (13.1, 19.6) and (13.0, 19.7) .. (12.8, 19.7).. controls (12.7, 19.7) and (12.6, 19.8) .. (12.5, 19.8).. controls (12.1, 19.9) and (11.9, 20.0) .. (11.7, 20.0).. controls (11.6, 20.0) and (11.5, 20.1) .. (11.4, 20.1).. controls (11.3, 20.1) and (11.2, 20.2) .. (10.9, 20.2).. controls (10.7, 20.2) and (10.4, 20.2) .. (10.2, 20.3).. controls (10.0, 20.3) and (9.3, 20.3) .. (8.9, 20.3) -- cycle(10.4, 20.0).. controls (10.6, 19.9) and (10.8, 19.9) .. (10.9, 19.9).. controls (11.0, 19.9) and (11.2, 19.8) .. (11.3, 19.8).. controls (11.4, 19.8) and (11.6, 19.8) .. (11.7, 19.7).. controls (11.7, 19.7) and (11.9, 19.7) .. (12.0, 19.7).. controls (12.1, 19.7) and (12.2, 19.6) .. (12.3, 19.6).. controls (12.4, 19.5) and (12.5, 19.5) .. (12.6, 19.5).. controls (12.7, 19.5) and (12.8, 19.4) .. (12.8, 19.4).. controls (12.9, 19.4) and (13.0, 19.3) .. (13.1, 19.3).. controls (13.2, 19.3) and (13.3, 19.3) .. (13.3, 19.2).. controls (13.4, 19.2) and (13.5, 19.2) .. (13.5, 19.2).. controls (13.6, 19.1) and (13.7, 19.1) .. (13.8, 19.1).. controls (13.8, 19.1) and (13.9, 19.0) .. (14.0, 19.0).. controls (14.0, 19.0) and (14.1, 19.0) .. (14.1, 18.9).. controls (14.1, 18.9) and (14.2, 18.9) .. (14.3, 18.9).. controls (14.4, 18.8) and (14.5, 18.8) .. (14.6, 18.8).. controls (14.6, 18.7) and (14.7, 18.7) .. (14.7, 18.7).. controls (14.7, 18.7) and (15.2, 18.5) .. (15.2, 18.4).. controls (15.2, 18.4) and (15.3, 18.4) .. (15.3, 18.4).. controls (15.6, 18.3) and (16.4, 17.6) .. (16.6, 17.2).. controls (16.7, 17.0) and (16.8, 16.9) .. (16.8, 16.9).. controls (16.8, 16.9) and (17.2, 16.2) .. (17.2, 16.2).. controls (17.2, 16.1) and (17.3, 16.0) .. (17.3, 16.0).. controls (17.3, 15.9) and (17.4, 15.8) .. (17.4, 15.8).. controls (17.4, 15.7) and (17.4, 15.7) .. (17.4, 15.6).. controls (17.5, 15.6) and (17.5, 15.5) .. (17.5, 15.4).. controls (17.5, 15.4) and (17.6, 15.2) .. (17.6, 15.1).. controls (17.6, 15.0) and (17.7, 14.9) .. (17.7, 14.8).. controls (17.7, 14.8) and (17.7, 14.6) .. (17.8, 14.5).. controls (17.8, 14.4) and (17.8, 14.3) .. (17.8, 14.3).. controls (17.8, 14.2) and (17.9, 13.9) .. (17.9, 13.7).. controls (18.0, 13.6) and (18.0, 13.3) .. (18.0, 12.8).. controls (18.0, 12.5) and (18.1, 12.1) .. (18.1, 12.0).. controls (18.1, 11.9) and (18.1, 11.7) .. (18.1, 11.4).. controls (18.2, 10.8) and (18.2, 10.1) .. (18.3, 10.0).. controls (18.3, 9.9) and (18.3, 8.8) .. (18.3, 8.7).. controls (18.2, 8.7) and (18.2, 8.5) .. (18.2, 8.2).. controls (18.1, 7.8) and (18.1, 7.5) .. (17.9, 7.2).. controls (17.9, 7.1) and (17.9, 7.0) .. (17.8, 6.9).. controls (17.8, 6.8) and (17.8, 6.7) .. (17.8, 6.6).. controls (17.7, 6.6) and (17.7, 6.5) .. (17.7, 6.4).. controls (17.6, 6.2) and (17.5, 5.9) .. (17.4, 5.7).. controls (17.3, 5.6) and (17.3, 5.4) .. (17.2, 5.3).. controls (17.2, 5.3) and (17.1, 5.1) .. (17.0, 5.1).. controls (17.0, 5.0) and (16.9, 4.9) .. (16.9, 4.8).. controls (16.9, 4.8) and (16.8, 4.7) .. (16.7, 4.6).. controls (16.7, 4.5) and (16.6, 4.4) .. (16.6, 4.4).. controls (16.5, 4.1) and (15.7, 3.3) .. (15.2, 2.9).. controls (14.9, 2.6) and (14.9, 2.6) .. (14.6, 2.4).. controls (14.4, 2.2) and (14.1, 2.1) .. (14.0, 2.1).. controls (14.0, 2.1) and (13.9, 2.0) .. (13.9, 2.0).. controls (13.8, 2.0) and (13.7, 1.9) .. (13.6, 1.9).. controls (13.5, 1.9) and (13.5, 1.8) .. (13.5, 1.8).. controls (13.5, 1.8) and (13.4, 1.8) .. (13.3, 1.8).. controls (13.2, 1.7) and (13.1, 1.7) .. (13.0, 1.7).. controls (13.0, 1.6) and (12.9, 1.6) .. (12.8, 1.6).. controls (12.6, 1.6) and (12.5, 1.5) .. (12.5, 1.5).. controls (12.2, 1.4) and (10.2, 1.4) .. (10.0, 1.5).. controls (10.0, 1.5) and (9.8, 1.5) .. (9.6, 1.5).. controls (9.0, 1.6) and (8.5, 1.7) .. (8.2, 1.8).. controls (8.2, 1.8) and (8.1, 1.9) .. (8.0, 1.9).. controls (8.0, 1.9) and (7.8, 2.0) .. (7.7, 2.0).. controls (7.6, 2.1) and (7.5, 2.1) .. (7.4, 2.2).. controls (6.8, 2.4) and (6.4, 2.7) .. (5.9, 3.1).. controls (5.7, 3.2) and (5.5, 3.4) .. (5.4, 3.5).. controls (5.1, 3.7) and (5.0, 3.9) .. (4.8, 4.1).. controls (4.7, 4.2) and (4.5, 4.4) .. (4.4, 4.5).. controls (4.2, 4.7) and (4.1, 4.8) .. (4.1, 4.8).. controls (4.1, 4.8) and (4.1, 4.9) .. (4.0, 4.9).. controls (4.0, 5.0) and (3.9, 5.1) .. (3.9, 5.1).. controls (3.8, 5.2) and (3.8, 5.3) .. (3.7, 5.3).. controls (3.7, 5.4) and (3.6, 5.4) .. (3.6, 5.5).. controls (3.6, 5.5) and (3.5, 5.6) .. (3.5, 5.7).. controls (3.3, 5.8) and (3.2, 5.9) .. (3.2, 6.0).. controls (3.1, 6.1) and (3.1, 6.1) .. (3.1, 6.2).. controls (3.0, 6.3) and (3.0, 6.3) .. (2.9, 6.4).. controls (2.9, 6.5) and (2.8, 6.5) .. (2.8, 6.6).. controls (2.8, 6.6) and (2.7, 6.7) .. (2.7, 6.7).. controls (2.7, 6.8) and (2.6, 6.8) .. (2.6, 6.9).. controls (2.5, 6.9) and (2.5, 7.0) .. (2.4, 7.1).. controls (2.4, 7.1) and (2.3, 7.2) .. (2.3, 7.3).. controls (2.3, 7.3) and (2.2, 7.4) .. (2.2, 7.4).. controls (2.2, 7.5) and (2.1, 7.5) .. (2.1, 7.5).. controls (2.1, 7.5) and (2.1, 7.6) .. (2.0, 7.7).. controls (2.0, 7.7) and (1.9, 7.9) .. (1.9, 7.9).. controls (1.8, 8.0) and (1.7, 8.2) .. (1.7, 8.2).. controls (1.7, 8.3) and (1.7, 8.4) .. (1.6, 8.5).. controls (1.6, 8.5) and (1.6, 8.7) .. (1.5, 8.8).. controls (1.5, 8.9) and (1.5, 9.0) .. (1.5, 9.1).. controls (1.4, 9.1) and (1.4, 9.3) .. (1.4, 9.4).. controls (1.4, 9.6) and (1.3, 9.8) .. (1.3, 9.9).. controls (1.2, 10.2) and (1.2, 11.6) .. (1.3, 12.2).. controls (1.3, 12.3) and (1.4, 12.6) .. (1.4, 12.8).. controls (1.4, 13.3) and (1.4, 13.5) .. (1.5, 13.7).. controls (1.5, 13.8) and (1.5, 14.0) .. (1.6, 14.1).. controls (1.6, 14.3) and (1.6, 14.4) .. (1.6, 14.5).. controls (1.7, 14.5) and (1.7, 14.6) .. (1.7, 14.7).. controls (1.8, 14.9) and (2.0, 15.3) .. (2.1, 15.5).. controls (2.2, 15.6) and (2.7, 16.2) .. (2.8, 16.3).. controls (2.8, 16.3) and (2.9, 16.4) .. (3.0, 16.5).. controls (3.2, 16.7) and (3.5, 17.0) .. (3.9, 17.3).. controls (4.0, 17.4) and (4.1, 17.5) .. (4.1, 17.5).. controls (4.2, 17.6) and (5.0, 18.3) .. (5.2, 18.5).. controls (5.2, 18.5) and (5.3, 18.6) .. (5.4, 18.6).. controls (5.6, 18.8) and (5.9, 19.0) .. (6.0, 19.0).. controls (6.0, 19.0) and (6.0, 19.1) .. (6.1, 19.1).. controls (6.1, 19.1) and (6.2, 19.2) .. (6.2, 19.2).. controls (6.2, 19.2) and (6.3, 19.2) .. (6.3, 19.2).. controls (6.4, 19.3) and (6.5, 19.3) .. (6.5, 19.3).. controls (6.6, 19.3) and (6.6, 19.4) .. (6.7, 19.4).. controls (6.7, 19.4) and (6.8, 19.5) .. (6.9, 19.5).. controls (6.9, 19.5) and (7.0, 19.5) .. (7.1, 19.6).. controls (7.2, 19.6) and (7.3, 19.6) .. (7.3, 19.7).. controls (7.4, 19.7) and (7.5, 19.7) .. (7.6, 19.7).. controls (7.7, 19.8) and (7.8, 19.8) .. (7.9, 19.8).. controls (8.0, 19.8) and (8.1, 19.9) .. (8.2, 19.9).. controls (8.5, 20.0) and (9.7, 20.0) .. (10.4, 20.0) -- cycle; \end{tikzpicture} \end{document} which give me a filled area, but not a path. I would prefer a path with the same line width in my actual case. Here below is the original blurry image: Says that I want a closed and smooth path, any suggestion on the process above? Edited: I try with Gemini-3.5-Flash with the following prompt: Identify the path and return to me a smooth TikZ Bezier closed curve. Which give the code: \documentclass[tikz,border=10pt]{standalone} \begin{document} \begin{tikzpicture} \draw [ line width=1.5pt, color=black!80, line cap=round, line join=round ] (0.2, 2.2) .. controls (1.0, 2.2) and (1.5, 1.9) .. (1.8, 1.3) .. controls (2.1, 0.7) and (2.2, -0.2) .. (1.9, -0.9) .. controls (1.6, -1.6) and (0.9, -2.1) .. (0.0, -2.1) .. controls (-0.9, -2.1) and (-1.6, -1.7) .. (-2.0, -0.9) .. controls (-2.4, -0.1) and (-2.4, 0.8) .. (-1.8, 1.5) .. controls (-1.2, 2.2) and (-0.6, 2.2) .. (0.2, 2.2) -- cycle; \end{tikzpicture} \end{document} But the details is NOT what the original image is, and the output code is unstable(due to LLM's randomness limitation): The LLM solution is probably not what I was after here.

I am using the "related entries" feature of Biblatex to cross-reference and show relationships among the publications in my Biblatex + Biber bibliography. The bibliography uses the default numeric citation style (e.g., "[1]"). For some reason, the citations generated by my related:... macros have extraneous space between the opening square bracket and the first digit of the citation key. Consider the following minimal example: \documentclass{article} \usepackage{biblatex} \begin{filecontents}{test.bib} @article{eger2025transforming, author = {John Eger}, title = {Transforming Science}, journal = {Journal of Foo}, year = 2025, volume = 1, related = {eger2026transforming}, relatedtype = {later}, } @article{eger2026transforming, author = {John Eger}, title = {Transforming Science}, journal = {Journal of Bar}, year = 2026, volume = 1, } \end{filecontents} \NewBibliographyString{later} \DefineBibliographyStrings{english}{later = {Later published as }} \newbibmacro*{related:later}[1]{% \entrydata{#1}{\autocite{\thefield{clonesourcekey}}}} \addbibresource{test.bib} \begin{document} \nocite{eger2025transforming,eger2026transforming} \printbibliography \end{document} The first entry in the bibliography is rendered as [1] John Eger. “Transforming Science”. In: Journal of Foo 1 (2025). Later published as [ 2]. rather than as [1] John Eger. “Transforming Science”. In: Journal of Foo 1 (2025). Later published as [2]. I can't see anything in my related:later macro that would be causing this extra space. Is this a bug in Biblatex or some problem with my code?

I have a file for course notes that uses subfiles for each section of the notes, and phantomsection \addcontentsline to group several sections into a "Unit". My main file is mathNotes.tex, with multiple subfiles: testFile1p1.tex, testFile2p1.tex, etc. (the actual project is significantly larger). In the following MWE, the phantomsection's \addcontentsline's are before each subfile for the corresponding unit, but the phantomsection \addcontentsline appears in the TOC after the subfiles: mathNotes.tex \documentclass{article} \usepackage{subfiles,hyperref} \begin{document} \tableofcontents \pagebreak \phantomsection \addcontentsline{toc}{section}{Unit 1} \subfileinclude{subfiles/testFile1p1.tex} \phantomsection \addcontentsline{toc}{section}{Unit 2} \subfileinclude{subfiles/testFile2p1.tex} \end{document} testFile1p1.tex: \documentclass[../mathNotes]{subfiles} \begin{document} \section{Section in unit 1} stuff and things \end{document} testFile2p1.tex: \documentclass[../mathNotes]{subfiles} \begin{document} \section{Section in unit 2} things and stuff \end{document} Here is how the document appears in Evince: What syntax should I use to correct this? I know I could put each phantomsection \addcontentsline at the beginning of the first file for that unit, but I want the phantomsection's \addcontentsline in the main file since it makes organizing the units more straightforward. Also, I'm certain I had this working at one point, but despite my best efforts, I can't find what I changed in my git history.

I have a collection of exercise files that I later assemble into worksheets/tests. A simplified example looks like this: \begin{subexercises} \subexercise Hello \subexercise World \subexercise ! \subexercise ? \end{subexercises} \subexercise is a custom wrapper around \item that also handles additional formatting (margin notes, points, etc.). I would now like to selectively include only certain subexercises without editing the source files each time. For example, with something like \renewcommand{\subexselect}{1,4} I would want the output to contain only a) Hello b) ? So the numbering should remain continuous even though some subexercises are skipped. I also would like to keep the \item-like syntax \subexercise Hello instead of changing all files to something argument-based like \subexercise{Hello} because I already have many existing exercise files and like the syntax better (and partly also because I'm interested in how to achieve this and maybe learning something new that way). What I tried 1. Using conditionals inside \subexercise I experimented with \if...\fi constructs and tried to place balancing \iftrue / \fi pairs into begin/end hooks of the environment. I could not get this to work reliably. 2. Using pgfparser to gobble unwanted items I then tried parsing tokens until the next \subexercise and discarding them when the current item should not be printed. This almost works, except for the final item because there is no following \subexercise token to stop the parser. I also tried using \end{subexercises} as an alternative stop condition, but I could not figure out how to do this properly since it is not a single token. It works with an additional stop-marker at the end of the environment but having to manually insert this marker at the end of the environment is bad. Here is a minimal example of that attempt (when not including 4 in the list I get an emergency stop): \documentclass{article} \usepackage{enumitem} \usepackage{pgfparser} \newlist{subexercises}{enumerate}{1} \setlist[subexercises]{label=\alph*)} \newcommand{\subexselect}{} \newcounter{subexcount} \setcounter{subexcount}{0} \newcommand{\subexercise}[1][]{% \stepcounter{subexcount}% \ifnum\pdfmatch{\thesubexcount}{\subexselect}=1% \item \else \pgfparserparse{subex}% \fi } \pgfparserdef{subex}{all}\subexercise{\pgfparserswitch{final}\pgfparserreinsert} \pgfparserset{subex/silent=true} %\newcommand{subexend}{} %\pgfparserdef{subex}{all}subexend{\pgfparserswitch{final}} %\pgfparserdeffinal{subex}{} \begin{document} \renewcommand{\subexselect}{1,4} \begin{subexercises} \subexercise Hello \subexercise World \subexercise ! \subexercise ? %subexend \end{subexercises} \end{document} Question How can this kind of selective inclusion be implemented while preserving the \item-like syntax, i.e. not replacing subexercise by a macro that takes the body of the \item as argument?

I'm wanting to validate that my PDF satisfies WCAG accessibility. PDFix lists several WCAG profiles that it will use, but I would rather use veraPDF (which shares the same backend as PDFix). Is it possible to do so? How do the profiles relate to each other?

I am converting a dissertation written in LaTeX to docx format using pandoc. By fine-tuning my pandoc command and my reference document, I have made it so that pandoc can produce an almost perfect docx output, with one exception: I am getting extra outside parentheses around the citations generated by \cite{key} commands. Initial long citations are appearing as: "(Author, Title (Place: Publisher, Date), [page #])"; when they should be: "Author, Title (Place: Publisher, Date), [page #]". And subsequent short citations are appearing as: "(Author, Short Title, [page #])"; when they should be: "Author, Short Title, [page #]". My pandoc command is: pandoc -s dissertation.tex --filter pandoc-crossref --citeproc --bibliography=dissertation.bib --csl=chicago-notes-bibliography-subsequent-ibid-classic.csl --reference-doc=dissertation-reference.docx -o dissertation.docx My MWE of the LaTeX is: \documentclass[12pt, oneside]{book} \setcounter{secnumdepth}{5} \setcounter{tocdepth}{5} \usepackage{geometry} \geometry{letterpaper} \usepackage{graphicx} \usepackage{amssymb} \usepackage[english]{babel} \usepackage{csquotes} \usepackage{setspace} \singlespacing \usepackage{titlesec} \usepackage{microtype} \usepackage[backend=biber, style=verbose-ibid, language=english]{biblatex} \addbibresource{dissertation.bib} \renewcommand{\thesection}{\arabic{section}} \renewcommand*{\thesubparagraph}{\alph{subparagraph}.} \newcommand{\fn}{\footnote} \title{Title} \author{Author} \begin{document} \setlength{\emergencystretch}{1em} \include{Introduction} \include{Chapter_1} \include{Chapter_2} \printbibliography \end{document} All of my \cite{key} commands (so far as I can tell) are located in footnotes, which are created by my custom command: \fn{}. What I have done: (1) I have attempted to figure out where in the CSL file there would be an option to remove the prefix and suffix parentheses that I don't want. I cannot find an applicable option. (2) I have attempted to create lua and python scripts that would strip out the parentheses after --citeproc runs (the lua option didn't work because, so far as I understand, lua files are always accessed before citeproc). When I compile to PDF, everything works as expected. Is there anything I could be doing, particularly on the LaTeX end of things, to prevent this? Thank you for reading and your help!

How can I autocomplete a command in TeXmaker with placeholders, e.g. writing \frac and pressing a key results in \frac{}{} and the cursor cues into the first curly bracket? And how can I jump between placeholders? Tab doesn’t work and I don’t know why, although I’ve seen that the Tab key should do that?

I have a template and a style, which combined should output a PDF. The content comes from Markdown, and the conversion is made with Pandoc. The idea is to create a recipe book. There are environments for dedication, acknowledgements, and preface, and color boxes for ingredients and preparation (with a customized list for preparation steps). Since the book will be created in three different languages, the titles of each section should be customizable (either via the yaml header in the Markdown file, or any similar method which doesn't include changing the LaTeX files). Right now it doesn't output the titles of Dedication, Acknowledgements, Preface – just the contents. It also puts all those on the same page, although I have \cleardoublepage in the begin-code of each environment. I'm quite sure I'm doing something wrong around the environment and colorbox definitions, but my LaTeX knowledge is rusty (to say the least), and none of the small changes I made helped to solve this. Can anybody detect my error and help me to actually print the titles of the environments? What about the fonts? If I try to use Merriweather and Montserrat, I always get an error. (I have them installed on the PC.) Does my Markdown make any sense? Is there a better way of doing the whole thing? My template.tex: \documentclass[a4paper,12pt,twoside,openright,final]{book} \usepackage[catalan]{babel} % or serbian, german, etc. \usepackage[utf8]{inputenc} \usepackage{geometry} \geometry{left=2.5cm, right=2.5cm, top=3cm, bottom=3cm} \usepackage{recipestyles} \newcommand{\authorname}{$author$} \newcommand{\booktitle}{$title$} \begin{document} \begin{titlepage} \centering \pagecolor{dpyellow} \color{dpred} \vspace*{3cm} {\titlesfont \Huge \textbf{\booktitle} \par} \vspace{1.5cm} {\titlesfont \Large \authorname \par} \vfill \end{titlepage} \frontmatter \renewcommand{\thepage}{\Roman{page}} \pagestyle{roman} \pagecolor{dpyellow} \color{black} $if(dedication_title)$ \renewcommand{\dedicationtitle}{$dedication_title$} $endif$ $if(acknowledgements_title)$ \renewcommand{\acknowledgementstitle}{$acknowledgements_title$} $endif$ $if(preface_title)$ \renewcommand{\prefacetitle}{$preface_title$} $endif$ $if(ingredients_title)$ \renewcommand{\ingredientstitle}{$ingredients_title$} $endif$ $if(tips_title)$ \renewcommand{\tipstitle}{$tips_title$} $endif$ $if(dedication)$ \begin{envdedication} $dedication$ \end{envdedication} $endif$ $if(acknowledgements)$ \begin{envacknowledgements} $acknowledgements$ \end{envacknowledgements} $endif$ \tableofcontents \mainmatter \pagestyle{fancy} $if(preface)$ \begin{envpreface} $preface$ \end{envpreface} $endif$ $body$ \end{document} My recipestyles.sty: \NeedsTeXFormat{LaTeX2e} \ProvidesPackage{recipestyles}[2026/05/27] \RequirePackage{xcolor} \RequirePackage[T1]{fontenc} \RequirePackage{fontspec} \RequirePackage{fancyhdr} \RequirePackage{titlesec} \RequirePackage{pagecolor} \RequirePackage[most]{tcolorbox} \RequirePackage{enumitem} % colors \definecolor{dpyellow}{HTML}{FFF8DC} \definecolor{dpred}{HTML}{C8102E} % fonts (ligatures deactivated) \setmainfont[Ligatures={NoRequired,NoCommon,NoContextual}]{Georgia} % Merriweather \newfontfamily\titlesfont[Ligatures={NoRequired,NoCommon,NoContextual}]{Arial} % Montserrat % page styles % roman \fancypagestyle{roman}{ \fancyhf{} \fancyfoot[C]{\thepage} } % fancy \pagestyle{fancy} \fancyhf{} \fancyhead[LE,RO]{\titlesfont\color{dpred}\thepage} \fancyhead[RE]{\small\titlesfont\color{gray}\authorname} \fancyhead[LO]{\small\titlesfont\color{gray}\booktitle} \renewcommand{\headrulewidth}{0.4pt} % title styles % title of parts \titleformat{\part}[display] {\centering\Huge\bfseries\titlesfont\color{dpred}}{}{0pt}{\Huge} % title of chapters \titleformat{\chapter}[display] {\Huge\bfseries\titlesfont\color{dpred}}{}{0pt}{\Huge} \titlespacing*{\chapter}{0pt}{-20pt}{20pt} % title of sections \titleformat{\section} {\LARGE\bfseries\titlesfont\color{dpred}}{}{0em}{} \titlespacing*{\section}{0pt}{15pt}{10pt} % environments and boxes % variables for env/box titles \newcommand{\dedicationtitle}{Dedicació} \newcommand{\acknowledgementstitle}{Agraïments} \newcommand{\prefacetitle}{Pròleg} \newcommand{\ingredientstitle}{Ingredients} \newcommand{\tipstitle}{Consells} \newenvironment{envdedication}[1][\dedicationtitle]{% \cleardoublepage \vspace*{5cm} \begin{flushright} \itshape{\titlesfont\large\bfseries #1}\par\vspace{0.5cm}% }{\end{flushright}} \newenvironment{envacknowledgements}[1][\acknowledgementstitle]{% \cleardoublepage \vspace*{2cm} {\titlesfont\Huge\bfseries\color{dpred} #1}\par\vspace{1cm} }{} \newenvironment{envpreface}[1][\prefacetitle]{% \cleardoublepage \vspace*{2cm} {\titlesfont\Huge\bfseries\color{dpred} #1}\par\vspace{1cm} }{} % ingredients (yellow box with red border) \newtcolorbox{ingredientsbox}{colback=dpyellow, colframe=dpred, boxrule=1mm, sharp corners, title=\titlesfont\bfseries \ingredientstitle, coltitle=dpyellow, colbacktitle=dpred, fonttitle=\bfseries} % preparation steps \newlist{steps}{enumerate}{1} \setlist[steps]{label=\protect\tcbox[colback=dpred, colframe=dpred, coltext=dpyellow, sharp corners, size=small, on line, fontupper=\bfseries\titlesfont, top=1mm, bottom=1mm, left=1.5mm, right=1.5mm]{\arabic*}, leftmargin=1.5cm, labelsep=0.3cm, itemsep=0.5cm, parsep=0mm} \newenvironment{preparation}{\begin{steps}}{\end{steps}} % tips (red box) \newtcolorbox{tipsbox}{colback=white, colframe=dpred!70!black, boxrule=0.5mm, arc=2mm, title=\titlesfont\bfseries💡 \tipstitle, coltitle=dpred!70!black, colbacktitle=dpyellow, attach boxed title to top left={yshift=-2mm, xshift=2mm}, boxed title style={sharp corners, boxrule=0.5mm, colframe=dpred!70!black}} \providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}} \endinput My current test Markdown file: --- title: "Receptari" author: "D. P." date: "2026-05-27" dedication_title: "A la meva gent" --- ::: dedication Gràcies per tant amor! ::: ::: acknowledgements Moltes gràcies a tota la gent que va tenir la paciència i la confiança, tant en mi com en aquest llibre. ::: ::: preface Les paraules d'alguna persona important 👥 ::: # I: Fonaments ## Pa amb tomàquet ::: ingredientsbox - 4 llesques de pa de pagès - 2 tomàquets madurs ::: ### Preparació ::: preparation 1. **Talleu el pa** en llesques. 2. **Torreu les llesques** lleugerament. ::: ::: tipsbox Aprofiteu el tomàquet madur, aquell que ja és una mica suau quan es prem i que probablement ja no faríeu servir per fer una amanida. ::: Pandoc command: pandoc receptari.md --template=template.tex --top-level-division=part --pdf-engine=xelatex -o receptari.pdf

I would like to have the first row (red ellipse) a little bit bigger, maybe not the same size as the second row, but right now it looks just too small. \documentclass{article} \usepackage[T1]{fontenc} \usepackage{lmodern} \usepackage[ngerman]{babel} \usepackage[landscape, margin=0.5cm]{geometry} \usepackage[ngerman]{babel} \usepackage{tabularray, tblr-extras} \usepackage{xcolor} \UseTblrLibrary{amsmath,varwidth} \UseTblrLibrary{babel} \pagenumbering{gobble} %\usepackage{showframe} \begin{document} \centering \begin{longtblr} { colspec={Q[l,m] Q[l,m] X[l,m] X[3,c] l l X[l,m]},vlines, cell{1}{4-Z}={r=2}{l,m}, measure=vbox, } \hline 06W & Nachlauf & {$\text{t[Bit]} = \frac{\mathtt{0x10000}-\text{Val}}{\text{CF}}$} & { $ \begin{aligned} (\text{CF}=3)\Rightarrow\quad \begin{cases} 2, & 65533 < \text{Val} \le 65536 \\ \mathtt{0x10000}-\text{Val}, & 65281 < \text{Val} \le 65533 \\ 255, & 65281 \geq \text{Val} \end{cases} \\[1em] (\text{CF}=7)\Rightarrow\quad \begin{cases} 2, & 65503 < \text{Val} \le 65536 \\ \dfrac{\mathtt{0x10000}-\text{Val}}{16}, & 61456 < \text{Val} \le 65503 \\ 255, & 61456 \geq \text{Val} \end{cases} \end{aligned} $ } & 015 & Nachlauf\_Bits & RTS Nachlauf nach Daten (in Bits: Max 255, Min 2)\{1;R;2..255\} \\ \hline[dotted] 03B7.4& {Clockfaktor (CF)} & $ \begin{aligned} 3 & =\text{1-fach} \\ 7 & =\text{16-fach} \end{aligned} $ & & & & \\ \hline \end{longtblr} \end{document}

If I have a complicated font declared with many series and shapes under babel applying to one language, then a font for another language is specified that only has much more limited series and shapes, many warnings are produced like this: LaTeX Font Warning: Font shape `TU/Aboensis(0)/m/it' undefined (Font) using `TU/Aboensis(0)/m/n' instead on input line... It's possible to get rid of these by manually declaring the font to fallback, e.g., ItalicFont = {Aboensis} But this becomes tedious if you are working with many families and series and shapes. I guess it's also possible to use the silence package, but I wouldn't want to supress all these warnings, only ones related to the particular font in question. What are my options to declare things neatly and avoid the warnings? Here's a MWE that produces warnings: %! TeX Program = lualatex \documentclass{article} \usepackage{babel} \babelprovide[import,main]{australian} \babelprovide[import]{german} \babelfont{rm} [ FontFace={l}{n}{Font=Noto Serif Light}, FontFace={l}{it}{Font=Noto Serif Light Italic} ] {Noto Serif} \babelfont[german]{rm}{Aboensis} \begin{document} {\itshape English \foreignlanguage{german}{Deutsch}} {\fontseries{l} English \foreignlanguage{german}{Deutsch}} {\fontseries{l} English \foreignlanguage{german}{Deutsch}} {\fontseries{l}\itshape English \foreignlanguage{german}{Deutsch}} \end{document} The warnings can be removed using: \babelfont[german]{rm}[ ItalicFont = Aboensis, FontFace={l}{n}{Font=Aboensis}, FontFace={l}{it}{Font=Aboensis}, ]{Aboensis} But If I have to deal with lots of series and shapes as well as sf and tt families, it becomes verbose. I want something simpler and more compact.

I'm trying to create a scripture index using bibleref, but I'm currently facing a problem with the index generation: nothing appears in the index. Here's my MWE: \documentclass{article} \usepackage{bibleref} \usepackage[xindy]{indextools} \makeindex[name=bible] \renewcommand{\biblerefindex}{\index[bible]} \begin{document} \ibibleverse{Ex}(20:17) \printindex[bible] \end{document} And the output of the xindy compilation : \begin{theindex} \item Ancien Testament \subitem \BRbooktitlestyle {Ex} \subsubitem \BRchapterstyle {20}\BRchvsep \BRversestyle {17}, \textrm{1} \end{theindex}

I need to draw some balls at the entrance (and if possible at the bottom) of the Galton board like the following picture: Code: \documentclass[tikz]{standalone} \begin{document} \begin{tikzpicture} \def\distance{0.3cm} \def\layer{10} \def\radius{2pt} % draw the nails \foreach \i in {0,...,\layer} { \foreach \j in {0,...,\numexpr\i+1\relax} { \draw ({-\distance*\i/2 + \distance*\j}, {-sqrt(3)*\distance*\i/2}) circle[radius=\radius]; } } % draw the slant board on both sides \draw ({-\layer*\distance/2-sqrt(3)*\radius}, {-sqrt(3)*\distance*\layer/2-\radius}) -- (0,2*\radius) -- +(-4pt,4pt); \draw ({-\layer*\distance/2+\distance*(\layer+1)+sqrt(3)*\radius}, {-sqrt(3)*\distance*\layer/2-\radius}) -- (\distance,2*\radius) -- +(4pt,4pt); % draw the separator plates \foreach \i in {0,...,\numexpr\layer+1\relax} { \draw ({-\layer*\distance/2 + \i*\distance}, {-sqrt(3)*\layer*\distance/2 - \radius}) -- ++ (0,-0.5cm); } % draw the bottom line \draw ({-\layer*\distance/2},{-sqrt(3)*\layer*\distance/2 - \radius - 0.5cm}) -- ++ ({(\layer+1)*\distance},0); % number the separated areas \foreach \i in {0,...,\numexpr\layer\relax} { \node at ({-\layer*\distance/2 + \distance*(\i+0.5)},{-sqrt(3)*\layer*\distance/2 - \radius - 0.7cm}) {\footnotesize\i}; } \end{tikzpicture} \end{document}

I am trying to draw a 3D graph that looks like the attached picture. However, I cannot make the axes behave in the same way. In the picture, some intervals of the axes appear on top of the surface, while on other intervals the surface appears above the axes. I would also like the axis labels to stay outside the arrow tips. What I have tried so far is shown below, together with the attached picture. I would like a solution that works for arbitrary functions, not only for this particular example. \documentclass[tikz,border=5pt]{standalone} \usepackage{pgfplots} \pgfplotsset{compat=1.18} \begin{document} \begin{tikzpicture} \begin{axis}[ view={45}{20}, axis lines=center, %axis on top, axis line style={-latex}, xlabel={$x$}, ylabel={$y$}, zlabel={$z$}, ticks=none, xmin=-5, xmax=5, ymin=-5, ymax=5, zmin=-4, zmax=4, width=7cm, height=7cm, colormap/jet, declare function={ f(\x,\y)=10*\y/((\x^2 + 1)*(\y^2 + 2*\y + 4)); }, ] \addplot3[ surf, opacity=0.6, faceted color=black!80, samples=60, samples y=60, domain=-4:4, y domain=-4:4, line width=0.01pt, ] (({x},{y},{f(x,y)}); \end{axis} \end{tikzpicture} \end{document}

I have a monster LaTeX project that I'm making accessible with tagging: \DocumentMetadata{ tagging=on, lang=en-US, pdfstandard=UA-2, tagging-setup={ math/alt/use, math/setup=mathml-SE } } This takes a non-instantaneous amount of time to compile. To speed things up while I'm editing with TeXShop, I will often turn off tagging and/or includeonly a single chapter. Once I'm done with my edits, I'll turn tagging back on and compile from the command line so that I can increase the required memory limits. My problem is that I will sometimes forget and try to compile the entire tagged document from within TeXShop. Because the compilation won't complete, my aux files get corrupted. This takes a few more compilations to fix, and is annoying. Is there a way that I can abort the compilation (1) before opening any of the aux files (2) if tagging is active, (3) I'm compiling the entire document, and (4) I haven't increased the memory limits?