Week

What is the command to use in mtpro2 the heavy bold \mathsf{F}? Actually I not remembering this. I have tried with \boldsymbol, \boldmath but nothing. \documentclass{article} \usepackage{amsmath} \usepackage{mtpro2} \begin{document} $\mathsf{F}\mathbold{\mathsf{F}} \mbf{\mathsf{F}}$ \end{document} I can't use bm package because there is mtpro2. I have seen the pag. 6/7 of the documentation: https://tug.ctan.org/fonts/mtp2lite/texmf/doc/fonts/mtpro2/mtpro2.pdf.

\documentclass{beamer} \usepackage{tikz} \setbeamertemplate{navigation symbols}{} \begin{document} \begin{frame} \begin{itemize} \item why \item itemize \item move \item upwards \item in the second frame? \end{itemize} \end{frame} \begin{frame} \begin{itemize} \item why \item itemize \item move \item upwards \item in the second frame? \end{itemize} \begin{tikzpicture}[remember picture,overlay] \fill (current page.center) circle[radius=.5cm]; \end{tikzpicture} \end{frame} \end{document} tikzpictures with overlay should have no bounding box. Why in the second frame the same itemize of the first frame move upward?

I am trying to place two TikZ figures side-by-side , but I am running into layout issues. In my document structure, I cannot use \resizebox or scale the figures, because there are too many elements that would conflict with my existing layout and typography constraints. For the same reason, I also want to avoid changing the x and y unit scales inside the TikZ pictures. My goal is to keep both figures at their natural size and still arrange them horizontally on the same line, respecting the page geometry. However, despite trying different approaches, the result is not satisfactory: the figures either overlap, break the margins, or force unwanted scaling. Is there a reliable way to force two TikZ pictures to stay side-by-side without resizing them and while respecting the page layout constraints? \documentclass{article} \usepackage[top=2.5cm,bottom=2.2cm, left=3.2cm,right=1.5cm,headsep=10pt,a4paper]{geometry} \usepackage{graphicx} \usepackage{subcaption} \usepackage{tikz} \usetikzlibrary{arrows.meta} \tikzset{ rhtip/.tip={ Triangle[ fill=white, line width=0.8pt, length=8pt, width=8pt ] } } \begin{document} \begin{figure}[htbp] \centering \begin{subfigure}{0.48\textwidth} \centering \begin{tikzpicture}[x=0.6cm,y=0.6cm, font=\large] \draw[->] (0,0)--(6,0) node[right]{$x$}; \draw[->] (0,0)--(0,4) node[above]{$y$}; \node[below left] at (0,0){$O$}; \node[draw,circle] at (-1,3){$\Sigma$}; \begin{scope}[shift={(1.1,1.1)}] \draw[->] (0,0)--(6,0) node[right]{$x'$}; \draw[->] (0,0)--(0,4) node[above]{$y'$}; \node[below right] at (0,0){$O'$}; \node[draw,circle] at (1.5,3){$\Sigma'$}; \end{scope} \draw[-rhtip, line width=2pt, red!80!black] (6.2,3)--(7.5,3); \node[below] at (6.85,2.8){$\mathbf{v}$}; \end{tikzpicture} \caption{$\Sigma'$ in moto rispetto a $\Sigma$} \end{subfigure} \begin{subfigure}{0.48\textwidth} \centering \begin{tikzpicture}[x=0.6cm,y=0.6cm, font=\large] \draw[->] (0,0)--(6,0) node[right]{$x$}; \draw[->] (0,0)--(0,4) node[above]{$y$}; \node[below left] at (0,0){$O$}; \node[draw,circle] at (-1,3){$\Sigma$}; \begin{scope}[shift={(1.1,1.1)}] \draw[->] (0,0)--(6,0) node[right]{$x'$}; \draw[->] (0,0)--(0,4) node[above]{$y'$}; \node[below right] at (0,0){$O'$}; \node[draw,circle] at (1.5,3){$\Sigma'$}; \end{scope} \draw[-rhtip, line width=2pt, orange!80!black] (7.5,3)--(6.2,3); \node[above] at (6.85,3.1){$-\mathbf{v}$}; \end{tikzpicture} \caption{Velocità relativa opposta} \end{subfigure} \caption{Due sistemi di riferimento inerziali in moto relativo rettilineo uniforme.} \end{figure} \end{document}

I'm trying to customize item labels within an enumerate list on the fly, using the item options. However, I don't fully understand how it works. The code below produces unexpected results, and different patterns emerge for the first layer of the list and the second layer of the list. I'm trying to do this without using the enumitem package, if possible. I know how to manually edit the items, but want the counter to be more automated in the inner list. Here is a minimum working example: \documentclass{article} \begin{document} \begin{enumerate} \item[\theenumi.] Why is this 0, instead of 1? \begin{enumerate} \item[\theenumii.] Why is this blank? \item[\theenumii.] Why is this blank? \item[\theenumii.] Why is this blank? \end{enumerate} \item And this adds one to the counter \item And this adds one to the counter \end{enumerate} \begin{enumerate} \setcounter{enumi}{1} \item[\theenumi.] Now this is 1, as expected. \begin{enumerate} \setcounter{enumii}{1} \item[\theenumii.] And this is a, as expected. \item[\theenumii.] Why doesn't this add one to the counter? \item[\theenumii.] Why doesn't this add one to the counter? \end{enumerate} \item And why does this still add one to the counter? \item And why does this still add one to the counter? \end{enumerate} \end{document} Here's the output:

This question might be off-topic, but the reason I ask it here is that I want to eventually create a module for a LaTeX package to enable the use of conic gradients via PDF Type 6 shadings which are also known as Coons Patch Mash Tiling. Also, please do not read this as "fix my issue for me" question. Rather, I appreciate any pointers to where I could be wrong. I understand that this topic is highly specialised, so I don't expect anybody to actually fix it completely or even partially. Now, as far as I understand, such shadings are essentially encoded as object stream in a PDF with the following object structure as basis (of course the object number and the contents of the stream and its length are different in a real document): 1 0 obj << /ShadingType 6 /ColorSpace /DeviceRGB /BitsPerCoordinate 16 /BitsPerComponent 8 /BitsPerFlag 2 /Decode [ 0 100 0 100 0 1 0 1 0 1 ] /Length 0 >> stream 00... endstream The stream defines the patches. Each path can be thought of a (distorted) rectangle of which the four sides are described as cubic Bézier curves. Therefore, each of the four edges of the patch has four control points, which means that there are twelve such points needed to describe a patch. Also, each corner of the patch is assigned a color. Now, in a mesh, the patches are attached to each other so that they share a common edge. To identify the shared edge, a flag is added to each patch which describes which edge is shared. A 0 flag identifies the initial patch, a 1 flag means that the right edge of the previous patch is used as the left edge of the current patch. There are more flags, but we only need these two for this case. If edges are shared, the relevant control points and colors are omitted in the description of the patch in the stream. So, if we take the sizes as described by /BitsPerCoordinate, \BitsPerComponent and /BitsPerFlag (let us assume 16, 8, and 2 respectively, also let us assume RGB), we get the following binary representation of the a patch with flag 0: Flag: 2 bits Points: 12 points, 16 bits for the x coordinate, 16 bits for the y coordinate Colors: 4 colors, 8 bits for the red part, 8 bits for the green part, 8 bits for the blue part For a patch with flag 1, we get: Flag: 2 bits Points: 8 points, 16 bits for the x coordinate, 16 bits for the y coordinate Colors: 2 colors, 8 bits for the red part, 8 bits for the green part, 8 bits for the blue part Maybe I got something wrong here already, which might explain why things don't work. Anyways, my question is why the following does not result in the desired output. My idea for a conic shading was to create patches that look like slices of a pie. Like this: I first tried without the rounded edge and just set the control points to be equal to the relevant corner, hoping that this would result in a triangle-shaped rectangle. So my patches would adhere to the following logic: Patch 1: Flag = 0 Points: (50, 50) (50, 50) (100, 50) (100, 50) (100, 50) (50, 100) (50, 100) (50, 100) (50, 50) (50, 50) (50, 50) (50, 50) Colors: (255,0,0) (191,0,64) (191,0,64) (255,0,0) Patch 2: Flag = 1 Points: (50, 100) (0, 50) (0, 50) (0, 50) (50, 50) (50, 50) (50, 50) (50, 50) Colors: (128,0,128) (128,0,128) Patch 3: Flag = 1 Points: (0, 50) (50, 0) (50, 0) (50, 0) (50, 50) (50, 50) (50, 50) (50, 50) Colors: (64,0,191) (64,0,191) Patch 4: Flag = 1 Points (50, 0) (100, 50) (100, 50) (100, 50) (50, 50) (50, 50) (50, 50) (50, 50) Colors: (0,0,255) (0,0,255) But, the output is totally not what it should look like although I think that the stream is correct. Acrobat also complains about something being wrong. It looks like this: 21 0 obj << /ShadingType 6 /ColorSpace /DeviceRGB /BitsPerCoordinate 16 /BitsPerComponent 8 /BitsPerFlag 2 /Decode [ 0 100 0 100 0 1 0 1 0 1 ] /Length 350 >> stream 20002000200020003FFFE0003FFFE0003FFFE00020003FFFE0003FFFE0003FFFE00020002000200020002000200020003FC0002FC0102FC0103FC00018000FFFF00008000000080000000800080008000800080008000800080008000800080800080400020002000000020000000200000002000200020002000200020002000200010002FD0002FD80000000FFFF8000FFFF8000FFFF8000800080008000800080008000800080000000FF0000FF endstream endobj So, my question is: What am I missing? Where is the probably simple but basic problem? The following is an MWE intended for testing. It contains a few helper funcitons and the relevant functions from the package where the code eventually is supposed to be included. It should work with PDFLaTeX and LuaLaTeX: \DocumentMetadata{uncompress} \documentclass[]{article} \usepackage{l3draw} \ExplSyntaxOn % a few helper functions \cs_new:Npn \__hawkdraw_tuple_use_i:w ( #1 , #2 ) {#1} \cs_new:Npn \hawkdraw_tuple_use_i:n #1 { \fp_to_dim:n { \exp_last_unbraced:Ne \__hawkdraw_tuple_use_i:w { \fp_eval:n {#1} } } } \cs_new:Npn \__hawkdraw_tuple_use_ii:w ( #1 , #2 ) {#2} \cs_new:Npn \hawkdraw_tuple_use_ii:n #1 { \fp_to_dim:n { \exp_last_unbraced:Ne \__hawkdraw_tuple_use_ii:w { \fp_eval:n {#1} } } } \cs_new_protected:Npn \hawkdraw_support_pdfliteral:n #1 { \sys_if_engine_luatex:TF { \tex_pdfextension:D literal {#1} } { \tex_pdfliteral:D {#1} } } \cs_new_protected:Npn \hawkdraw_support_pdfxform:nnN #1#2#3 { \tex_immediate:D \tex_pdfxform:D \tl_if_empty:nF {#1} { attr {#1} } resources {#2} #3 } \cs_new_protected:Npn \hawkdraw_support_pdflastxform: { \tex_pdflastxform:D } \cs_new_protected:Npn \hawkdraw_support_pdfrefxform:N #1 { \tex_pdfrefxform:D \int_use:N #1 \scan_stop: } \cs_generate_variant:Nn \hawkdraw_support_pdfrefxform:N { c } % === % relevant code from the package \box_new:N \l__hawkdraw_shading_object_box \cs_new_protected:Npn \hawkdraw_shading_set:nnn #1#2#3 { \hbox_set_to_wd:Nnn \l__hawkdraw_shading_object_box { 100bp } { \vbox_to_ht:nn { 100bp } { \skip_vertical:n { 0pt plus 1fil } \hawkdraw_support_pdfliteral:n { /Sh ~ sh } } \skip_horizontal:n { 0pt plus 1fil } } \pdf_object_new:n { hawkdraw_shading_ #1 } \tl_if_empty:nTF {#3} { \pdf_object_write:nne { hawkdraw_shading_ #1 } { dict } { #2 } } { \pdf_object_write:nne { hawkdraw_shading_ #1 } { stream } { {#2} {#3} } } \hawkdraw_support_pdfxform:nnN { } { /Shading ~ << ~ /Sh ~ \pdf_object_ref:n { hawkdraw_shading_ #1 } ~ >> } \l__hawkdraw_shading_object_box \int_const:cn { c__hawkdraw_shading_ #1 _int } { \hawkdraw_support_pdflastxform: } } \cs_new_protected:Npn \hawkdraw_shading_use:n #1 { \hawkdraw_support_pdfrefxform:c { c__hawkdraw_shading_ #1 _int } } % === \cs_new:Npn \hawkdraw_convert_bin_to_hex:n #1 { \__hawkdraw_convert_bin_to_hex_aux:w #1 \q_stop } \cs_generate_variant:Nn \hawkdraw_convert_bin_to_hex:n { e } \cs_new:Npn \__hawkdraw_convert_bin_to_hex_aux:w #1 \q_stop { \int_compare:nNnF { \tl_count:n {#1} } < { 4 } { \__hawkdraw_convert_bin_to_hex_aux:NNNNw #1 \q_stop } } \cs_new:Npn \__hawkdraw_convert_bin_to_hex_aux:NNNNw #1#2#3#4#5 \q_stop { \int_format:nn { \int_from_bin:n {#1#2#3#4} } { 1X } \__hawkdraw_convert_bin_to_hex_aux:w #5 \q_stop } % === \cs_generate_variant:Nn \color_export:nnN { e } \cs_generate_variant:Nn \str_set_convert:Nnnn { Ne } \seq_new:N \l__hawkdraw_shading_conic_colors_seq \seq_new:N \l__hawkdraw_shading_conic_colors_bin_seq \cs_new_protected:Npn \hawkdraw_shading_conic_stream:N #1 { \tl_set:Ne #1 { \hawkdraw_convert_bin_to_hex:e { \seq_map_indexed_function:NN \l__hawkdraw_shading_conic_colors_bin_seq \__hawkdraw_shading_conic_stream_aux:nn } } } \cs_new:Npn \__hawkdraw_shading_conic_stream_aux:nn #1#2 { % skip first entry representing color at first edge \int_compare:nNnF {#1} = { 1 } { % flag (2 bit) \int_format:nn { \int_compare:nNnTF {#1} = { 2 } { 0 } { 1 } } { 0>2b } % four patches for each of the n colors % patch is pie segment going from 0 to 360 / ( n * 4 ) % points of first patch (12 points, 2 x 16 bits each \int_compare:nNnT {#1} = { 2 } { \prg_replicate:nn { 2 } { \__hawkdraw_shading_conic_stream_point_polar:nn { 0 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 2 ) } } \prg_replicate:nn { 2 } { \__hawkdraw_shading_conic_stream_point_polar:nn { 1 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 2 ) } } } \__hawkdraw_shading_conic_stream_point_polar:nn { 1 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 2 ) } \prg_replicate:nn { 3 } { \__hawkdraw_shading_conic_stream_point_polar:nn { 1 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 1 ) } } \prg_replicate:nn { 3 } { \__hawkdraw_shading_conic_stream_point_polar:nn { 0 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 1 ) } } \__hawkdraw_shading_conic_stream_point_polar:nn { 0 } { 360 / ( \seq_count:N \l__hawkdraw_shading_conic_colors_bin_seq - 1 ) * ( #1 - 2 ) } % colors (4 colors, 3 x 8 bits each) \int_compare:nNnT {#1} = { 2 } { \seq_item:Nn \l__hawkdraw_shading_conic_colors_bin_seq { #1 - 1 } } #2 #2 \int_compare:nNnT {#1} = { 2 } { \seq_item:Nn \l__hawkdraw_shading_conic_colors_bin_seq { #1 - 1 } } } } \cs_new:Npn \__hawkdraw_shading_conic_stream_point_polar:nn #1#2 { % get from point polar % normalize to 65535 \int_format:nn { \fp_to_int:n { \hawkdraw_tuple_use_i:n { ( 50bp , 50bp ) + ( \draw_point_polar:nn { #1 * 50bp } {#2} ) } / 100bp * 65535 } } { 0>16b } \int_format:nn { \fp_to_int:n { \hawkdraw_tuple_use_ii:n { ( 50bp , 50bp ) + ( \draw_point_polar:nn { #1 * 50bp } {#2} ) } / 100bp * 65535 } } { 0>16b } } \cs_new_protected:Npn \__hawkdraw_shading_color_set_bin_value:n #1 { \seq_put_right:Ne \l__hawkdraw_shading_conic_colors_bin_seq { \int_format:nn { \int_from_hex:n {#1} } { 0>24b } } } \cs_generate_variant:Nn \__hawkdraw_shading_color_set_bin_value:n { V } % start , % start!25!mid , start!50!mid , start!75!mid , mid , % mid!25!end , mid!50!end , mid!75!end , end \cs_new_protected:Npn \hawkdraw_shading_color_set_bin_values:n #1 { \seq_clear:N \l__hawkdraw_shading_conic_colors_bin_seq \seq_set_from_clist:Nn \l__hawkdraw_shading_conic_colors_seq {#1} \seq_map_indexed_inline:Nn \l__hawkdraw_shading_conic_colors_seq { \int_compare:nNnTF {##1} = { 1 } { \color_export:enN { \seq_item:Nn \l__hawkdraw_shading_conic_colors_seq { 1 } } { HTML } \l__hawkdraw_shading_color_value_tmp_tl \__hawkdraw_shading_color_set_bin_value:V \l__hawkdraw_shading_color_value_tmp_tl } { \color_export:enN { \seq_item:Nn \l__hawkdraw_shading_conic_colors_seq { ##1 - 1 } ! 75 ! ##2 } { HTML } \l__hawkdraw_shading_color_value_tmp_tl \__hawkdraw_shading_color_set_bin_value:V \l__hawkdraw_shading_color_value_tmp_tl \color_export:enN { \seq_item:Nn \l__hawkdraw_shading_conic_colors_seq { ##1 - 1 } ! 50 ! ##2 } { HTML } \l__hawkdraw_shading_color_value_tmp_tl \__hawkdraw_shading_color_set_bin_value:V \l__hawkdraw_shading_color_value_tmp_tl \color_export:enN { \seq_item:Nn \l__hawkdraw_shading_conic_colors_seq { ##1 - 1 } ! 25 ! ##2 } { HTML } \l__hawkdraw_shading_color_value_tmp_tl \__hawkdraw_shading_color_set_bin_value:V \l__hawkdraw_shading_color_value_tmp_tl \color_export:enN { ##2 } { HTML } \l__hawkdraw_shading_color_value_tmp_tl \__hawkdraw_shading_color_set_bin_value:V \l__hawkdraw_shading_color_value_tmp_tl } } } \cs_new_protected:Npn \hawkdraw_shading_conic:n #1 { \int_if_exist:cF { c__hawkdraw_shading_ conic . #1 _int } { \hawkdraw_shading_color_set_bin_values:n {#1} \hawkdraw_shading_conic_stream:N \l_tmpa_tl \hawkdraw_shading_set:nnn { conic . #1 } { /ShadingType ~ 6 ~ /ColorSpace ~ /DeviceRGB ~ /BitsPerCoordinate ~ 16 ~ /BitsPerComponent ~ 8 ~ /BitsPerFlag ~ 2 ~ /Decode ~ [ ~ 0 ~ 100 ~ % x 0 ~ 100 ~ % y 0 ~ 1 ~ % R 0 ~ 1 ~ % G 0 ~ 1 ~ % B ] ~ } { \tl_use:N \l_tmpa_tl } } } \ExplSyntaxOff \begin{document} \ExplSyntaxOn \hawkdraw_shading_conic:n { red , blue } \hbox_set:Nn \l_tmpa_box { \hawkdraw_shading_use:n { conic.red,blue } } \box_use:N \l_tmpa_box \ExplSyntaxOff \end{document}

What package I have to use if I want to get French text in superscript? I want to write "57ème croche sur 92" with the term "ème" in superscript.

I use countwords to count the number of words in some LaTeX documents. The package counts words into a standard LaTeX counter. I then use totcount to display this wordcount at the beginning of the document. The number is generally in the thousands. Totcount provides a single macro \total{<counter>} for printing the eventual value of a counter, but it doesn't do any intelligent formatting, like dividing thousands with a comma/space (and fair enough -- very few situations call for counters in the thousands!). I would like to print the eventual value of the counter at the beginning of the document in a nicely formatted way. How can I do this? Based on other discussions of formatting counters, I have tried using numprint and siunitx, but neither of these work -- MWEs below. TIA! Failure #1 numprint \documentclass{article} \title{Foobar} % For counting words \usepackage{countwords} \newcounter{words} \setcounter{words}{0} % For printing final value \usepackage{totcount} \regtotcounter{words} % For dummy text \usepackage{lipsum} \usepackage{numprint} \begin{document} \maketitle % Prints `1112' (no comma) \total{words} % `Should' print `1,112', but gives an error. \numprint{\total{words}} \countwordsstart{words} \lipsum[1-12] \countwordsstop{words} \end{document} I get an error: ./test.tex:27: Package numprint Error: Invalid characters `\def ' in mandatory argument of (numprint) \numprint. Allowed are (numprint) `0123456789.,eEdD+-\pm '. Failure #2 siunitx \documentclass{article} \title{Foobar} % For counting words \usepackage{countwords} \newcounter{words} \setcounter{words}{0} % For printing final value \usepackage{totcount} \regtotcounter{words} % For dummy text \usepackage{lipsum} \usepackage{siunitx} \begin{document} \maketitle % Prints `1112' (no comma) \total{words} % `Should' print `1,112', but gives an error. \num[group-separator={,}]{\total{words}} \countwordsstart{words} \lipsum[1-12] \countwordsstop{words} \end{document} I get an error: ./test.tex:27: Package siunitx Error: Invalid number '\def \c@words@totc {\c@words@totc (siunitx) }1112'. I also looked at fmtcount but found it doesn't cover thousands separators.

I'm wondering why columns in tabular seem to not add space but \hline does. Is there a way to make it so that everything overlaps? \documentclass{article} \setlength{\parindent}{0pt} \setlength{\parskip}{0pt} \setlength{\tabcolsep}{0pt} \begin{document} Line\\ Line \vspace*{-2\baselineskip} \begin{tabular}{|l|} \hline Line\\ \hline Line\\ \hline \end{tabular}%\par\prevdepth=\dp\strutbox \vspace*{-2\baselineskip} Line\\ Line \end{document} EDIT: Thank you to all who answered. Using David Carlisle's comment, I now have the below: \documentclass{article} \setlength{\parindent}{0pt} \setlength{\parskip}{0pt} \setlength{\tabcolsep}{0pt} \setlength{\lineskip}{0pt} \begin{document} \def\newhline{% \noalign{\kern-.5\arrayrulewidth}\hline\noalign{\kern-.5\arrayrulewidth}% } Line\\ Line \vspace*{-2\baselineskip} \begin{tabular}[t]{|l|} \newhline % <- causing problems Line\\ \newhline Line\\ \newhline \end{tabular}\par\prevdepth=\dp\strutbox % for overlap \vspace*{-2\baselineskip} Line\\ Line \end{document} Seems the top \newhline prevents everything from lining up.

I want to draw the graph of z = x^2 + y^2, and I am using tikz for that. I used the following command: \begin{tikzpicture}[ x={(1cm,0cm)}, y={(-0.6cm,-0.35cm)}, z={(0cm,1cm)}, line join=round, line cap=round, scale=1, ] % Axes \draw[->] (0,0,0) -- (2,0,0); \draw[->] (0,0,0) -- (0,2.5,0); \draw[->] (0,0,0) -- (0,0,4); % Graph \draw[thick,smooth,variable=\t,domain=-1.8:1.8] plot ({\t},{0},{\t*\t}); % Circle that gives a 3d impression \draw[thick,smooth,variable=\t,domain=0:360] plot ({1.8*sin(\t)},{1.8*cos(\t)},{3.24}); \end{tikzpicture} However, the circle does not "fit" the graph: How can I adjust this?

I've gone through several threads on this forum, as well as videos by Javier Bezos, and these samples, but as the title says I'm unable to get Hindi text to work within a mostly English Beamer presentation, using Babel. Polyglossia works for me: \documentclass{beamer} \usepackage{polyglossia} \setdefaultlanguage{english} \setotherlanguage{hindi} \newfontfamily\devanagarifontsf[Script=Devanagari]{Noto Sans Devanagari} \begin{document} \title{\texthindi{नमस्ते}} \author{Lorem Ipsum} \begin{frame} \titlepage \end{frame} \end{document} However, I want to switch from Polyglossia to Babel because compilation is taking too long with Polyglossia for a large presentation. But I'm unable to find a snippet that works. For e.g.: \documentclass{beamer} \usepackage[english]{babel} \babelprovide[import, onchar=ids fonts]{hindi} \babelfont[devanagari]{sf}{Noto Sans Devanagari} \begin{document} \title{नमस्ते} \author{Lorem Ipsum} \begin{frame} \titlepage \end{frame} \end{document} When I compile this snippet with lualatex, I get this error: [1 Missing character: There is no न (U+0928) in font [lmsans12-regular]:+tlig;! {/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map} Missing character: There is no म (U+092E) in font [lmsans12-regular]:+tlig;! Missing character: There is no स (U+0938) in font [lmsans12-regular]:+tlig;! Missing character: There is no ् (U+094D) in font [lmsans12-regular]:+tlig;! Missing character: There is no त (U+0924) in font [lmsans12-regular]:+tlig;! Missing character: There is no े (U+0947) in font [lmsans12-regular]:+tlig;! ] (./hindi_reproducible_eg.aux)) I'm also getting two other messages from Babel in this compilation, and I'm not sure what they mean: Package babel Info: The current font is not a babel standard family: (babel) [lmsans10-regular]:+tlig; at 10.95pt (babel) There is nothing intrinsically wrong with this warning, and (babel) you can ignore it altogether if you do not need these (babel) families. But if they are used in the document, you should be (babel) aware 'babel' will not set Script and Language for them, so (babel) you may consider defining a new family with \babelfont. (babel) See the manual for further details about \babelfont. (babel) Reported on input line 7. (./hindi_reproducible_eg.aux Package babel Info: The following font families will use the default (babel) settings for all or some languages: (babel) * \rmfamily = lmr (babel) [lmroman10-regular]:+tlig; at 10.95pt (babel) * \sffamily = lmss (babel) [lmsans10-regular]:+tlig; at 10.95pt (babel) * \ttfamily = lmtt (babel) [lmmono10-regular]: at 10.95pt (babel) There is nothing intrinsically wrong with it, but (babel) 'babel' will no set Script and Language, which could (babel) be relevant in some languages. If your document uses (babel) these families, consider redefining them with \babelfont. (babel) Reported on input line 6. ) I have LuaLaTeX version 1.18.0, Beamer version 3.72, and Babel version 25.4.

I am aware for creating historical documents, the DVI format is still in use. And there is still tex4ht, as far as I know the only way to convert latex to HTML offered in TeXlive, but, apart from this, is there any use case for the DVI format? Maybe another package relying on it. I ask because i maintain a kind of build tool (very roughly comparable with latexmk) and ask myself on the details of supporting the dvi format.

I'm having trouble understanding Asymptote's (3.11) light rendering. When I run this code below: import three; size(8cm); currentprojection = orthographic((5,4,2), up=Y); currentlight = light(new pen[]{white}, new triple[]{(1,1,1)}); draw(unitcube, surfacepen=material(cyan)); real L = 2; draw(O--L*X, Arrow3); draw(O--L*Y, Arrow3); draw(O--L*Z, Arrow3); label("$x$", L*X, E); label("$y$", L*Y, N); label("$z$", L*Z, Z); I expected it to light up the whole cube (from my viewpoint; I understand the backside might not be lit). However, I instead got this: The left side of the cube is completely dark, which does not make sense considering the unit cube should essentially be lit with the placement of the light. However, changing the perspective to (5, 4, -2) yields this: The side that's pitch black here is the side that was initially lit in the first image. Considering there was no change to the light's position, I did not expect this to happen. I experimented with the emissive argument, however that is not what I wish to do. How does the lighting actually work in asymptote, and how do I fully illuminate all three sides of the cube, using the initial orthographic projection?

I've been working with google AI on this for 2 hrs. It can't figure a solution. One time it gave me 100 lines javascript code to fix this. Then it gave 50 lines .css code which made the date vanish. Here is MWE \documentclass[12pt]{article} \usepackage{latexml} \begin{document} \title{my book} \author{me} \date{\today} \maketitle \tableofcontents \section{first section} text \end{document} latexml always adds () around the date for some reason: How to tell it not to do that? commands used >latexml --dest=A.xml A.tex >latexmlpost --format=html5 --dest=A.htm A.xml

The following is my MWE: \documentclass{article} \usepackage{mathtools} % Loads amsmath and defines \shortintertext % Logarithms \DeclareMathOperator{\lb}{lb} \NewCommandCopy{\oldlog}{\log} \newcommand*{\implicitbaselog}{% Uncomment only one of the following lines \oldlog % Uncomment to set ambiguous logarithm as default % \lb % Uncomment to set binary logarithm as default % \lg % Uncomment to set common logarithm as default % \ln % Uncomment to set natural logarithm as default } \newcommand*{\useambiguouslog}{\renewcommand*{\implicitbaselog}{\oldlog}} \newcommand*{\usebinarylog}{\renewcommand*{\implicitbaselog}{\lb}} \newcommand*{\usecommonlog}{\renewcommand*{\implicitbaselog}{\lg}} \newcommand*{\usenaturallog}{\renewcommand*{\implicitbaselog}{\ln}} \RenewDocumentCommand{\log}{e{_}}{ \IfNoValueTF{#1}{\implicitbaselog}{\oldlog_{#1}} } \begin{document} \begin{alignat*}{4} \shortintertext{With default definition of \texttt{\textbackslash implicitbaselog}: } \log x &= \oldlog x, && && && \\ \shortintertext{after \texttt{\textbackslash usebinarylog}: } \usebinarylog \log x &= \lb x \; &&\text{ and } && \; \log_3 x &&= \oldlog_3 x, \\ \shortintertext{after \texttt{\textbackslash usecommonlog}: } \usecommonlog \log x &= \lg x \; &&\text{ and } && \; \log_4 x &&= \oldlog_4 x, \\ \shortintertext{after \texttt{\textbackslash usenaturallog}: } \usenaturallog \log x &= \ln x \; &&\text{ and } && \; \log_5 x &&= \oldlog_5 x, \\ \shortintertext{after \texttt{\textbackslash useambiguouslog}: } \useambiguouslog \log x &= \oldlog x \; &&\text{ and } && \; \log_6 x &&= \oldlog_6 x. \end{alignat*} \end{document} Essentially, I would like to simply use \useambiguouslog, \usebinarylog, \usecommonlog, and \usenaturallog to change how \log is typeset in the document whenever it is not followed by a subscript indicating a specific base. Is there a way to improve my solution? Thank you in advance.

Consider the code: \documentclass{article} \usepackage{xcolor,graphicx} %\usepackage{transparent} \usepackage{tikz} \usetikzlibrary{calc} \begin{document} \begin{figure} [!htb] \centering \includegraphics[width=8em,height=12em]{example-image} \end{figure} \begin{figure} [!htb] \centering \begin{tikzpicture} \node (a) at (0,0) {\includegraphics[width=8em,height=12em]{example-image}}; \filldraw[draw=red,fill opacity=.55,fill=green!65!black] (a.north west) rectangle (a.south east); \end{tikzpicture} \end{figure} \end{document} which produces Notice that in the second image there is a lighter shade of green between the outer red frame and in the inner black frame. QUESTION: How may I change the color of the region between the two frames from "lighter shade of green" to, say, red? I compile the code with xelatex. Thank you.

I am learning context and found this problem below and looking for workaround. Below are two examples where context generates invalid XML EXAMPLE 1 When there is more than ONE paragraph in section, the XML generated is not valid. This works \setupbackend[export=yes, xhtml=yes] \starttext \startsection[title={Introduction}] A \stopsection \stoptext The XML is valid <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!-- input filename : A processing date : 2026-07-02 15:56:59-05:00 context version : 2026.04.10 18:55 exporter version : 0.36 --> <?xml-stylesheet type="text/css" href="styles/A-defaults.css" ?> <?xml-stylesheet type="text/css" href="styles/A-images.css" ?> <?xml-stylesheet type="text/css" href="styles/A-fonts.css" ?> <?xml-stylesheet type="text/css" href="styles/A-styles.css" ?> <?xml-stylesheet type="text/css" href="styles/A-templates.css" ?> <document context="2026.04.10 18:55" date="2026-07-02 15:56:59-05:00" file="A" language="en" title="A" version="0.36" xml:lang="en"> <section detail="section" chain="section" implicit="1" level="3"> <sectioncaption> <sectionnumber>1</sectionnumber> <sectiontitle>Introduction</sectiontitle> </sectioncaption> <sectioncontent> A </sectioncontent> </section> </document> Adding second paragraph, it now generates bad XML \setupbackend[export=yes, xhtml=yes] \starttext \startsection[title={Introduction}] A B \stopsection \stoptext The XML is <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!-- input filename : A processing date : 2026-07-02 15:58:06-05:00 context version : 2026.04.10 18:55 exporter version : 0.36 --> <?xml-stylesheet type="text/css" href="styles/A-defaults.css" ?> <?xml-stylesheet type="text/css" href="styles/A-images.css" ?> <?xml-stylesheet type="text/css" href="styles/A-fonts.css" ?> <?xml-stylesheet type="text/css" href="styles/A-styles.css" ?> <?xml-stylesheet type="text/css" href="styles/A-templates.css" ?> <document context="2026.04.10 18:55" date="2026-07-02 15:58:06-05:00" file="A" language="en" title="A" version="0.36" xml:lang="en"> <section detail="section" chain="section" implicit="1" level="3"> <sectioncaption> <sectionnumber>1</sectionnumber> <sectiontitle>Introduction</sectiontitle> </sectioncaption> <sectioncontent> A <break/> B </sectioncontent> </section> </document> <break/> Notice the break is inserted after end of document. This gives error with xsltproc >xsltproc transform.xsl A-export/A-raw.xml > A.htm A-export/A-raw.xml:29: parser error : Extra content at the end of the document <break/> ^ unable to parse A-export/A-raw.xml EXAMPLE 2 When using \startalignment there is extra break after document: \setupbackend[export=yes, xhtml=yes] \starttext \startalignment[middle] \setupblank[big] {\definedfont[SerifBold at 24pt]\setupinterlinespace[line=58pt] the title} \blank[medium] {\tfa m} \blank[medium] {\tfa \currentdate} \stopalignment \stoptext The XML generated also has a break after document ends: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!-- input filename : A processing date : 2026-07-02 16:15:24-05:00 context version : 2026.04.10 18:55 exporter version : 0.36 --> <?xml-stylesheet type="text/css" href="styles/A-defaults.css" ?> <?xml-stylesheet type="text/css" href="styles/A-images.css" ?> <?xml-stylesheet type="text/css" href="styles/A-fonts.css" ?> <?xml-stylesheet type="text/css" href="styles/A-styles.css" ?> <?xml-stylesheet type="text/css" href="styles/A-templates.css" ?> <document context="2026.04.10 18:55" date="2026-07-02 16:15:24-05:00" file="A" language="en" title="A" version="0.36" xml:lang="en"> the title <break/> m <break/> July 2, 2026</document> <break/> Is there a workaround? TL 2026

Please write LaTeX code using pdflatex to reproduce "MODULO 2" with an approximate outline style similar to the image, sized to 12.4 cm wide and 5.3 cm high, without using TikZ. My best attempt has been: \documentclass{article} \usepackage[utf8]{inputenc} \usepackage{xcolor} \usepackage{graphicx} \usepackage{contour} \renewcommand{\familydefault}{\sfdefault} \begin{document} \noindent \resizebox{8.5cm}{3cm}{% \contourlength{0.5pt}% \contour{black}{\textcolor{white}{\textbf{MODULO}}}% }\, \resizebox{2.6cm}{5.2cm}{% \contourlength{0.5pt}% {\textcolor{black}{\textbf{2}}}% } \end{document} Using pdfLaTeX: but I would like something as close as possible to this:

The code below: \documentclass{article} \usepackage[erewhon]{fontsetup} \usepackage{lipsum} \begin{document} \lipsum[1] {\bfseries \lipsum[2]} \begin{gather*} abcdefghijklmnopqrstuvwxyz\\ x^2+y^2=z^2\\ \sum_{n=1}^{\infty} \frac{1}{n^2} = \frac{\pi^2}{6} \end{gather*} \end{document} yields: ! LaTeX Error: Command \danger already defined. Or name \end... illegal, see p.192 of the manual. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.77 \warning} Should fontsetup(v2.6.0) do something like \let\danger\relax internally to avoid this?

Turning on LaTeX3’s experimental Tagged PDF support with the newpx fonts sometimes causes spacing between characters to be incorrect, especially when there are digits next to commas. Am I doing something wrong, or is there a workaround? The LaTex3 Project’s tagging status page lists newpx as compatible with tagging. The problem disappears if either tagging is turned off or if a different typeface (e.g. Computer Modern) is used. I am using TeXLive 2026 with pdftex. Minimal example: \DocumentMetadata{tagging=on} \documentclass{article} \usepackage{newpx} \listfiles \begin{document} \((1,2)_3\) \begin{tabular}{cccc} \((1,2)_3\) \\ \(J\) & \((1,2)_3\) \end{tabular} \end{document} Further technical info (output with \listfiles): This is pdfTeX, Version 3.141592653-2.6-1.40.29 (TeX Live 2026/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./example.tex LaTeX2e <2025-11-01> L3 programming layer <2026-05-15> (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/documentmetadata-support.ltx (/usr/share/texlive/texmf-dist/tex/latex/pdfmanagement/pdfmanagement-testphase. sty (/usr/share/texlive/texmf-dist/tex/latex/tagpdf/tagpdf-base.sty) (/usr/share/texlive/texmf-dist/tex/latex/pdfmanagement/pdfmanagement.ltx))) (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def) (/usr/share/texlive/texmf-dist/tex/latex/pdfmanagement/l3backend-testphase-pdft ex.def) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-latest.s ty (/usr/share/texlive/texmf-dist/tex/latex/tagpdf/tagpdf.sty (/usr/share/texlive/texmf-dist/tex/latex/tagpdf/tagpdf-mc-code-generic.sty)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-names.st y) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-new-or-2 .sty (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-footnotes.ltx )) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-block.st y (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-kernel-changes.sty (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/glyphtounicode-cmex.tex)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-context. sty)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-sec.sty) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-toc.sty ) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-minipage .sty (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-new-or-1 .sty)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-graphic. sty) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-float.st y) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-bib.sty) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-text.sty ) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-marginpa r.sty) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-title.st y) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-table.st y (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-math.sty (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-math.ltx) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-mathpkg.ltx) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-mathintent.ltx)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-firstaid .sty) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-testphase-tikz.sty )) (/usr/share/texlive/texmf-dist/tex/latex/pdfmanagement/pdfmanagement-firstaid.s ty) (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2025/01/22 v1.4n Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/newpx/newpx.sty `newpx'v1.551, 2025/10/30 Integrated loading of newpxmath and a text font for all latex engines (msharpe) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty) (/usr/share/texlive/texmf-dist/tex/latex/fontaxes/fontaxes.sty (/usr/share/texlive/texmf-dist/tex/latex/figureversions/figureversions.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty) (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty) (/usr/share/texlive/texmf-dist/tex/latex/carlisle/scalefnt.sty) (/usr/share/texlive/texmf-dist/tex/latex/trimspaces/trimspaces.sty) (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) (/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty)) (/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.sty (/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.tex)) IV (/usr/share/texlive/texmf-dist/tex/latex/newpx/newpxmath.sty `newpxmath' v1.551, 2025/10/30 Math macros based on pxfonts (msharpe) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty For additional information on amsmath, use the `?' option. (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) (/usr/share/texlive/texmf-dist/tex/latex/latex-lab/latex-lab-amsmath.ltx) (/usr/share/texlive/texmf-dist/tex/generic/kastrup/binhex.tex) (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex))) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/centernot.sty) amsthm NOT loaded ) (/usr/share/texlive/texmf-dist/tex/latex/newpx/newpxtext.sty `newpxtext' v1.542, 2025/06/07 Text macros taking advantage of TeXGyre Pagella and its extensions (msharpe) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty (/usr/share/texlive/texmf-dist/tex/latex/newpx/t1minzpl.fd)) (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) (/usr/share/texlive/texmf-dist/tex/latex/pdfmanagement/xcolor-patches-tmp-ltx.s ty) (/usr/share/texlive/texmf-dist/tex/latex/xpatch/xpatch.sty (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty) (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty) (/usr/share/texlive/texmf-dist/tex/latex/newpx/t1zpllf.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/t1zpltlf.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/t1zplosf.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/t1zpltosf.fd))) (./example.aux) (/usr/share/texlive/texmf-dist/tex/latex/newpx/omlnpxmi.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/unpxexa.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/lmsnpxsy.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/lmxnpxexx.fd) Info: mathml file example-mathml does not exist Info: mathml file example-luamml-mathml does not exist (/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii [Loading MPS to PDF converter (version 2006.09.02).] ) LaTeX DocumentMetadata Warning: The language has not been set in (DocumentMetadata) \DocumentMetadata. (DocumentMetadata) Setting it to 'en' as fallback. (/usr/share/texlive/texmf-dist/tex/latex/newpx/ot1minzpl.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/unpxmia.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/unpxsym.fd) (/usr/share/texlive/texmf-dist/tex/latex/newpx/unpxsyc.fd) [1{/var/lib/texmf/fo nts/map/pdftex/updmap/pdftex.map}{/usr/share/texlive/texmf-dist/fonts/enc/dvips /newpx/px-lms.enc}{/usr/share/texlive/texmf-dist/fonts/enc/dvips/newtx/ntx-ot1- tlf.enc}{/usr/share/texlive/texmf-dist/fonts/enc/dvips/newtx/ntx-ec-tlf.enc}]<< latex-list-css.html>><<latex-align-css.html>> (./example.aux) *File List* documentmetadata-support.ltx pdfmanagement-testphase.sty 2026-05-26 v0.97c LaTeX PDF management bundle tagpdf-base.sty 2026-05-17 v1.0c part of tagpdf - provide base, no-op versio ns of the user commands pdfmanagement.ltx 2026-05-26 v0.97c PDF management code l3backend-pdftex.def 2026-02-18 L3 backend support: PDF output (pdfTeX) l3backend-testphase-pdftex.def latex-lab-testphase-latest.sty 2025-09-13 v0.1d latex-lab modules tagpdf.sty 2026-05-17 v1.0c LaTeX kernel code for PDF tagging tagpdf-mc-code-generic.sty 2026-05-17 v1.0c part of tagpdf - code related to marking chunks - generic mode latex-lab-testphase-names.sty 2025-08-14 v0.8f Code related to the names of tags latex-lab-testphase-new-or-2.sty 2025-05-10 v0.86d Changes to the output rou tine latex-lab-footnotes.ltx 2025-07-04 v0.8o changes to the footnote interfaces latex-lab-testphase-block.sty 2025-07-26 v0.9k blockenv implementation latex-lab-kernel-changes.sty 2025-07-09 v0.85i General kernel and class chan ges glyphtounicode-cmex.tex latex-lab-testphase-context.sty 2025-10-09 v0.5b Providing context for insta nce, etc. latex-lab-testphase-sec.sty 2025-10-20 v0.84k Code related to the tagging of sectioning commands latex-lab-testphase-toc.sty 2025-07-02 v0.85h Code related to the tagging o f toc-like lists latex-lab-testphase-minipage.sty 2025-05-10 v0.81g Code related to the taggi ng of minipages and parboxes latex-lab-testphase-new-or-1.sty 2025-05-10 v0.85d Temporary output patches for tagging and better link support -- no longer active latex-lab-testphase-graphic.sty 2025-09-25 v0.80i Code related to the taggin g of graphics latex-lab-testphase-float.sty 2025-10-17 v0.81l Code related to the tagging of floats latex-lab-testphase-bib.sty 2025-05-09 v0.81c Code related to the tagging of bibliography and cite command latex-lab-testphase-text.sty 2025-05-10 v0.85f Code related to the tagging o f various small text commands latex-lab-testphase-marginpar.sty 2025-07-23 v0.85h Changes related to the t agging of the margin notes latex-lab-testphase-title.sty 2025-03-08 v0.85d Changes related to the taggi ng of the title latex-lab-testphase-table.sty 2025-08-01 v0.85s Code related to the tagging of tables array.sty 2025/09/25 v2.6n Tabular extension package (FMi) latex-lab-testphase-math.sty 2025-03-10 v0.8d code related to the math taggi ng latex-lab-math.ltx 2025-10-02 v0.6w Grab all the math(s) and tag it (experim ents) latex-lab-mathpkg.ltx 2025-06-20 v0.1c mathpkg adaptions latex-lab-mathintent.ltx 2025-08-03 v0.1c MathML intent attributes latex-lab-testphase-firstaid.sty 2025-11-03 v2025-11-03 Temporary patches to external packages needed for the tagging project latex-lab-testphase-tikz.sty 2025-09-27 v0.80d Code related to the tagging o f tikz pictures pdfmanagement-firstaid.sty 2026-05-26 v0.97c LaTeX PDF management bundle / f irstaid-patches article.cls 2025/01/22 v1.4n Standard LaTeX document class size10.clo 2025/01/22 v1.4n Standard LaTeX file (size option) newpx.sty 2025/10/30 v1.551 LaTeX and unicode LaTeX support for newpxmath and newpxtext, or for newpxtext and an otf math package (Michael Sharpe) fontenc.sty 2025/07/18 v2.1d Standard LaTeX package fontaxes.sty 2026-01-02 v2.0.2 Font selection axes (deprecated) figureversions.sty 2025-04-29 v1.0.1 Figure versions ifthen.sty 2024/03/16 v1.1e Standard LaTeX ifthen package (DPC) iftex.sty 2024/12/12 v1.0g TeX engine tests etoolbox.sty 2025/10/02 v2.5m e-TeX tools for LaTeX (JAW) scalefnt.sty trimspaces.sty 2009/09/17 v1.1 Trim spaces around a token list kvoptions.sty 2022-06-15 v3.15 Key value format for package options (HO) keyval.sty 2022/05/29 v1.15 key=value parser (DPC) ltxcmds.sty 2023-12-04 v1.26 LaTeX kernel commands for general use (HO) kvsetkeys.sty 2022-10-05 v1.19 Key value parser (HO) xstring.sty 2023/08/22 v1.86 String manipulations (CT) newpxmath.sty 2025/10/30 v1.551 LaTeX math support for newpx (Michael Sharpe ) amsmath.sty 2025/07/09 v2.17z AMS math features amstext.sty 2024/11/17 v2.01 AMS text amsgen.sty 1999/11/30 v2.0 generic functions amsbsy.sty 1999/11/29 v1.2d Bold Symbols amsopn.sty 2022/04/08 v2.04 operator names latex-lab-amsmath.ltx 2025-09-29 v0.1i amsmath adaptions binhex.tex xkeyval.sty 2025/11/04 v2.10 package option processing (HA) xkeyval.tex 2014/12/03 v2.7a key=value parser (HA) centernot.sty 2016/05/16 v1.4 Centers the not symbol horizontally (HO) newpxtext.sty 2025/06/07 v1.542 LaTeX and unicode LaTeX support for TeXGyreP agellaX (Michael Sharpe) fontenc.sty 2025/07/18 v2.1d Standard LaTeX package t1minzpl.fd 2021/05/25 v1.0 font definition file for T1/minzpl/TLF xcolor.sty 2024/09/29 v3.02 LaTeX color extensions (UK) color.cfg 2016/01/02 v1.6 sample color configuration pdftex.def 2025/09/29 v1.2d Graphics/color driver for pdftex mathcolor.ltx xcolor-patches-tmp-ltx.sty 2026-05-26 v0.97c patch xcolor for l3color xpatch.sty 2020/03/25 v0.3a Extending etoolbox patching commands expl3.sty 2026-05-15 L3 programming layer (loader) xparse.sty 2025-10-09 L3 Experimental document command parser textcomp.sty 2024/04/24 v2.1b Standard LaTeX package t1zpllf.fd 2021/05/25 v1.0 font definition file for T1/zpl/lf t1zpltlf.fd 2021/05/25 v1.0 font definition file for T1/zpl/tlf t1zplosf.fd 2021/05/25 v1.0 font definition file for T1/zpl/osf t1zpltosf.fd 2021/05/25 v1.0 font definition file for T1/zpl/tosf omlnpxmi.fd 2013/03/21 Fontinst v1.933 font definitions for OML/npxmi. unpxexa.fd 2013/03/24 Fontinst v1.933 font definitions for U/npxexa. lmsnpxsy.fd 2016/07/04 Fontinst v1.933 font definitions for LMS/npxsy. lmxnpxexx.fd 2016/07/04 Fontinst v1.933 font definitions for LMX/npxexx. supp-pdf.mkii ot1minzpl.fd 2021/05/25 v1.0 font definition file for OT1/minzpl/TLF unpxmia.fd 2013/03/24 Fontinst v1.933 font definitions for U/npxmia. unpxsym.fd 2023/08/16 Fontinst v1.933 font definitions for U/npxsym. unpxsyc.fd 2013/03/24 Fontinst v1.933 font definitions for U/npxsyc. *********** LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right. Package tagpdf Info: Finalizing the tagging structure: (tagpdf) Writing out ~24 structure objects (tagpdf) with ~21 'MC' leaf nodes. (tagpdf) Be patient if there are lots of objects! Package tagpdf Info: writing ParentTree Package tagpdf Info: writing IDTree Package tagpdf Info: writing RoleMap Package tagpdf Info: writing ClassMap Package tagpdf Info: writing NameSpaces Package tagpdf Info: writing StructElems Package tagpdf Info: writing Root )</usr/share/texlive/texmf-dist/fonts/type1/public/newpx/NewPXMI.pfb></usr/sha re/texlive/texmf-dist/fonts/type1/public/newpx/pxsys.pfb></usr/share/texlive/te xmf-dist/fonts/type1/public/newpx/zplr.pfb> Output written on example.pdf (1 page, 50114 bytes). Transcript written on example.log.

I asked this question before. Puttting this custom itemize in marginblock, I get this: As you can see, vertical lines disappear. Maybe this is the problem? in log : backgrounds > shapes > invalid region for 'tbg:1' %%%%%%%%%%%%%%%%%%%%%% %%% Implementation %%% %%%%%%%%%%%%%%%%%%%%%% %% Define the variables. \definecolor [MyItemizeColor] [red] \definemeasure[MyItemizeOffset] [1em] \definemeasure[MyItemizeThickness][1pt] %% Draw the rule to the left of the items. \definetextbackground[MyItemize][ mp=mpos:region:sideline, location=paragraph, framecolor=MyItemizeColor, rulethickness=\measure{MyItemizeThickness}, frameoffset=\measure{MyItemizeOffset}, ] %% Draw the bullet symbol. \startreusableMPgraphic{MyBullet} path p ; p := unitcircle scaled 5pt ; fill p withcolor white ; draw p withcolor "MyItemizeColor" withpen pencircle scaled \measure{MyItemizeThickness} ; setbounds currentpicture to boundingbox currentpicture leftenlarged ( -0.5bbwidth(currentpicture) + 0.5*\measure{MyItemizeThickness} ) ; \stopreusableMPgraphic \definesymbol[MyBullet][\reuseMPgraphic{MyBullet}] %% Define the itemize environment to use the custom symbol and rule. \defineitemgroup[MyItemize][itemize][ symbol=MyBullet, before={% \godown[0.5\measured{MyItemizeOffset}]% \starttextbackground[MyItemize]% \godown[0.5\measured{MyItemizeOffset}]% }, after={% \godown[0.5\measured{MyItemizeOffset}]% \stoptextbackground% \godown[0.5\measured{MyItemizeOffset}]% }, width=\measure{MyItemizeOffset}, ] \setupmarginblock[location=left,align=flushleft,width=3cm] %\showframe %%%%%%%%%%%%%%%%%%%%% %%% Demonstration %%% %%%%%%%%%%%%%%%%%%%%% \setuppapersize[A4, portrait] \setuplayout[ width=16cm, backspace=4cm, cutspace=1.5cm, leftmargin=3cm, leftmargindistance=4mm, ] %% Demonstration text. \starttext \startmarginblock \startMyItemize \item First item. \item Second item. \item Third item. \item Fourth item. \item Fifth item. \item Next page. \item Seventh item. \item Eighth item. \item Ninth item. \stopMyItemize \stopmarginblock \input ward \startMyItemize \item First item. \item Second item. \item Third item. \item Fourth item. \item Fifth item. \item Next page. \item Seventh item. \item Eighth item. \item Ninth item. \stopMyItemize Text after. \stoptext

I noticed that when I try to type unicode-math "⦦", the angle symbol is smaller than "∠" and "∟". Is there a way to draw another angle symbol that is outwardly slanted and the same size as "∠" and "∟"? \documentclass{article} \usepackage{unicode-math} \setmathfont{NewCMMath-Regular.otf} \begin{document} $∠∟⦦$ \end{document}

For certain tagged documents I need the following: Periods after numbers both in numbered headings and in ToC entries. Centered single-line chapter titles, no extraneous vertical space. No extraneous vertical space between chapters in List of Tables / Figures. The word “Part” / “Chapter” / “Appendix” in ToC lines for part and chapter. Up until the June 2026 release of LaTeX, I achieved the above by modifying bits copied from book.cls: \def\numberline#1{\hb@xt@\@tempdima{#1.\hfil}} %% Add period after numbers in ToC \def\@chapter[#1]#2{ ... 4 lines unchanged code ... \addcontentsline{toc}{chapter}{\@chapapp\space\thechapter.\hspace{1em}#1}% %% Custom ToC ... 7 lines unchanged code ... %%\addtocontents{lof}{\protect\addvspace{10\p@}}% %% No extra blank lines in LoF %%\addtocontents{lot}{\protect\addvspace{10\p@}}% %% No extra blank lines in LoT ... 6 lines unchanged code ... } \def\@makechapterhead#1{% %%\vspace*{50\p@}% %% Eliminate vertical space {\parindent \z@ \centering \normalfont %% Centered ... 2 lines unchanged code ... \huge\bfseries \@chapapp\space \thechapter. %% Add period after number %%\par\nobreak\vskip 20\p@ %% Eliminate newline and vertical space ... 4 lines unchanged code ... %%\vskip 40\p@ %% Eliminate vertical space }} %% Similarly modified versions of \@makeschapterhead, \@part, \@spart In the presence of \DocumentMetadata (the PDF needs to be tagged), the LaTeX June 2026 release uses the template mechanism for sectioning commands. The old fragile approach shown above no longer works. I can now achieve my first three goals by editing appropriate key-value pairs as in the following MWE: \DocumentMetadata{lang=en-us,tagging=on} \documentclass[oneside]{book} \makeatletter \def\numberline#1{\hb@xt@\@tempdima{#1.\hfil}} \EditInstance{heading}{chapter} { , after-penalty-vspace = 0pt , after-vspace = \baselineskip , prefix = \@chapapp , number-format = \thechapter. , heading-decls = \centering \parindent0pt \bfseries \Huge , contents-extra = } \EditInstance{heading}{part} { , number-format = \thepart. , heading-decls = \centering\bfseries\Huge } \DeclareInstanceCopy{headformat}{part}{std} \DeclareInstanceCopy{headformat}{chapter}{std} \makeatother \begin{document} \tableofcontents \mainmatter \part{My part} \chapter{My chapter} \section{My section} \appendix \chapter{My appendix} \end{document} Kudos to the developers for providing this more convenient and robust approach! As for the ToC lines for part and chapter, is there a key-value pair that controls how \addcontentsline gets called?, or how should I control those lines? I currently have the output but want the following output: My current (totally fragile) “solution” is to modify a copy of \__head_handle_marks_etc: \cs_set:Npn \__head_handle_marks_etc:nnnnn #1#2#3#4#5 { ... 23 lines of unchanged code ... \str_case:VnF{\l__head_name_tl} { {part}{\partname\space\thepart.\space} %% Custom ToC for Part {chapter}{\@chapapp\space\thechapter.\space} %% Custom ToC for Chapter } {\protect\numberline{ \use:c{ the \l__head_name_tl } } } %% Original code is fallback for Sections etc ... 8 lines of unchanged code ... } Is there a better way?

I have the following \documentclass[12pt,a4paper]{article} \usepackage{amsmath,amssymb} \usepackage{geometry} \usepackage{lipsum} \geometry{margin=2cm} \setlength{\parindent}{0pt} \renewcommand{\arraystretch}{1.25} \newsavebox{\leftbox} \begin{document} \begin{lrbox}{\leftbox} \begin{minipage}[t]{0.33\textwidth} \textbf{Given:}\hspace{2.5cm}\textbf{SI:} \vspace{2mm} \begin{tabular}{@{}l|l@{}} $m_1=120$ g & $0.12$ kg\\ $m_2=50$ g & $0.05$ kg\\ $c_1=4200\ \dfrac{\text{J}}{\text{kg}\cdot^\circ\text{C}}$ &\\ $c_2=920\ \dfrac{\text{J}}{\text{kg}\cdot^\circ\text{C}}$ &\\ $R=2\ \Omega$ &\\ $U=5$ V &\\ $\Delta t=12^\circ\text{C}$ &\\ $\eta=20\%$ &\\ \hline \multicolumn{2}{@{}l@{}}{\textbf{Find:}}\\ \multicolumn{2}{@{}l@{}}{$U-?$} \end{tabular} \end{minipage} \end{lrbox} \noindent \usebox{\leftbox} \hfill \begin{minipage}[t][\dimexpr\ht\leftbox+\dp\leftbox\relax][t]{0.64\textwidth} \textbf{Solution:} \vspace{2mm} \lipsum[1] \vfill \end{minipage} \lipsum[1-2] \end{document} which gives me this However I would like to write text in the right minipage as a continuous text without the need to break it (now it is causing problems with overlapping). I also would like to automatically left align the word 'SI' with the letters below it. It obviously comes from the fact that neither 'SI' or 'Given' are in the table, but that's on purpose - I need 'Given', 'SI' and 'Solution' to be on the same level vertically. How do I do that?

Is there a problem with the footnote rule? % !TEX TS-program= ConTeXt (LuaTeX) \mainlanguage[ar-dz] \setupdirections[bidi=global,method=one] \setuppapersize[A6] \usecolors[svg] \setupalign[r2l] \setupinteraction[state=start,color=navy,focus=standard] \setupwhitespace[small] \setupnote[numbercommand=\groupedcommand{(}{)}] \setupnotation [footnote] [alternative=serried, rule=paragraph, left={(}, align=r2l, %location=text, right={)}, headstyle=, stopper=] \setupfootnotes[way=bysection,align=r2l,color=navy] \setupmixedcolumns[direction=reverse] \setupbodyfont[amiri,12pt] \definestartstop[LTR] [before={\begingroup\lefttoright},after=\endgroup] \setuppagenumbering[location=] %================================ %================================ \starttext %================================ %================================ \startLTR from \goto{WikiPedia}[url(https://ar.wikipedia.org/wiki/السندباد_البحري)]: \stopLTR السِّندباد أو السِّندباد البحري\footnote{ موسوعة شبكة المعرفة الريفية نسخة محفوظة 07 مارس 2014 على موقع واي باك مشين.} هو شخصية أسطورية من شخصيات ألف ليلة وليلة وهو بحار من بغداد. عاش في فترة الخلافة العباسية، ويقال إن السندباد الحقيقي تاجر بغدادي مقيم في عُمان\footnote{د.عبد الرحمن عبد الكريم العاني، تاريخ عمان الإسلامي، مطبعة العاني، بغداد، 1985، "أطروحة دكتوراه" ص 23}. تعدّ حكاية السندباد البحري واحدة من أشهر حكايات ألف ليلة وليلة. زار السندباد الكثير من الأماكن السحرية والتقى بالكثير من الوحوش أثناء إبحاره في سواحل أفريقيا الشرقية وجنوب آسيا. \stoptext

Consider the code: \documentclass[12pt]{book} \usepackage{tikz,xcolor} \usetikzlibrary{decorations.text} % Spaceout Algorithm \def\theLetterSpace{0.5pt} \def\theWordSpace{1.5\LocalLetterSpace} \newlength\LocalLetterSpace \newcommand\spaceout[2][\theLetterSpace]{% \setlength\LocalLetterSpace{#1}\expandafter\spaceouthelpA#2 \relax\relax} \def\spaceouthelpA#1 #2\relax{% \spaceouthelpB#1\relax\relax% \ifx\relax#2\else\ \kern\theWordSpace\spaceouthelpA#2\relax\fi } \def\spaceouthelpB#1#2\relax{% #1% \ifx\relax#2\else \kern\LocalLetterSpace\spaceouthelpB#2\relax% \fi } \begin{document} \thispagestyle{empty} Here is some text. \vspace{10pt} {\spaceout[2pt]{Here is some "spaced out" text.}} \vspace{65pt} \begin{tikzpicture} \draw[-latex,white,postaction={decorate},decoration={text along path, text={I WOULD LIKE TO INCREASE SPACING BETWEEN THESE ARCHED LETTERS},text color={blue!85!black},text align=center}] (7,0) arc [start angle=180,end angle=0,radius=8]; \end{tikzpicture} \end{document} which produces: The above "spaceout" algorithm (if I recall correctly) cf. Steven B. Segeletes. As you can see, I have encountered no difficulty in applying the algorithm to a regular sentence. However, I have not been apply to apply it correctly to the arched words above. QUESTION: How may I, using this algorithm or by some other method, increase the spacing between the displayed arched letters? I compile the code with xelatex. Thank you.

I am trying to get a matrix with an overbrace and sidebrace which looks like the following; I tried the following code so far, \documentclass[12pt]{article} \usepackage{epsfig} \usepackage{amssymb} %\usepackage[dvips]{color} \usepackage{amsmath} \usepackage{amsthm} \[ \begin{array}{ccc} \overbrace{\text{Col 1}}^{\text{Label A}} & %\overbrace{\text{Col 2 \quad Col 3}}^{\text{Label B}} & %\overbrace{\text{Col 4}}^{\text{Label C}} \\ \begin{bmatrix} a_{11} & a_{12} & a_{13} \\ a_{21} & a_{22} & a_{23} \\ a_{31} & a_{32} & a_{33} \end{bmatrix} \end{array} \] \end{document} But it is not giving the desired output. Kindly help.

I have a textbook, and from it I have derived slides. To ensure that the slide contents match the book's I use catchfilebetweentags. I'm now working on the book's new edition and this package still correctly fetches the material between the tags, but it now omits spaces where the source file book.tex has line endings. Here is the derived file slides.tex. \documentclass{article} \usepackage{catchfilebetweentags} \newcommand{\catchfilefn}{book.tex} \begin{document} Introductory text \ExecuteMetaData[\catchfilefn]{firsttag} \ExecuteMetaData[\catchfilefn]{secondtag} \end{document} Here is the source file book.tex. \documentclass{book} \usepackage{blindtext} \begin{document} \blindtext %<*firsttag> Contents of first tag. This is a sentence with a line break in the middle. %</firsttag> \blindtext %<*secondtag> Contents of \textit{second} tag. One word has an\index{test} index entry. %</secondtag> \blindtext \end{document} In the output slides.pdf there is no space between the tag. and This. Similarly there is no space between a and line. Linewise for tag. and One, and an and index. I have used this package for years and not seen this behavior (its last update on CTAN is 2011). I have today's TeX Live.

I'd like to use a pgfplots axis environment to render some plots. I'd like them to be aligned with the surrounding TiKz graphics. However, I have not yet managed to find the correct options. I'm also only interested in the plotted line itself, so no ticks or axes need to be drawn in addition. So far I have this (failed) example. My goal would be aligning the coordinate system the axis environment such that the two curves are right on top of each other. With the width/height I assumed I could set the exact dimensions, but that already seems to be off. Is there a way to modify this axis-environment to match the coordinate system of the tikzpicture-environment? \documentclass{standalone} \usepackage{tikz} \usepackage{pgfplots} \pgfplotsset{compat=1.18} \begin{document} \begin{tikzpicture} \draw[lightgray] (-2, -3) grid (4, 4); \fill[lightgray] (0,0) circle (0.2); % origin \draw[green] plot [red, domain=-2:4, samples=200] (\x, {exp(-abs(\x)^2)}); \begin{axis}[ xtick=\empty, ytick=\empty, hide axis, xmin=-2, xmax=4, axis equal, width=6cm, height=7cm, anchor=south west, at={(-2cm,-2cm)}, ] \addplot [red, domain=-2:5, samples=200] (\x, {exp(-abs(\x)^2)}); \end{axis} \end{tikzpicture} \end{document}

In the MWE below, the TikZ picture is a ‘roadmap’ showing how various lemmas combine in a proof (vastly simplified from my original), and I would like to have the hyperlinked \refs to the lemmas (which are spread over multiple pages in my original). But with alt={...}, VeraPDF complains that Link annotations that target different locations shall be in separate Link or Reference structure elements If I remove alt={...}, the PDF passes validation. If I change \ref to \ref* to remove the hyperlinks, the PDF passes validation. If there is only one hyperlink in the TikZ picture, the PDF passes validation. The same problem occurs replacing on alt={...} with artifact. I understand that tagging is in development, but is there any quick fix or workaround that allows multiple hyperlinks in a TikZ picture with alt text? (Or is there perhaps some fundamental incompatibility with tagging multiple hyperlinks inside a TikZ picture?) MWE: \DocumentMetadata{ pdfversion=2.0, pdfstandard=UA-2, lang=en-GB, tagging=on, } \documentclass{article} \usepackage{unicode-math} \usepackage{hyperref} \usepackage{tikz} \newtheorem{lemma}{Lemma} \title{Test} \begin{document} Roadmap of proving the theorem: \begin{tikzpicture}[alt={Roadmap}] \node (A) at (0,0) {$A$}; \node (B) at (2,0) {$B$}; \node (C) at (4,0) {$C$}; \draw[->] (A) edge node[auto] {Lem.~\ref{lem:ab}} (B); \draw[->] (B) edge node[auto] {Lem.~\ref{lem:bc}} (C); \end{tikzpicture} \begin{lemma} \label{lem:ab} If $A$, then $B$. \end{lemma} \begin{lemma} \label{lem:bc} If $B$, then $C$. \end{lemma} \end{document}

I am experiencing a unexpected interaction between the New Computer Modern fonts and the bullets used for itemize environments. They are replaced by squared bullets and I didn't see any reference about it the documentation. Here is a MWE % !TEX TS-program = lualatex \documentclass[12pt,a4paper]{article} \usepackage[sansdefault]{fontsetup} \usepackage{lipsum} \begin{document} \lipsum[1][1-5] \begin{itemize} \item item 1 \item item 2 \item item 3 \end{itemize} \lipsum[1][1-5] \end{document}