tagging of \multicolumn currently fails as colortbl redefines the new definition in array.sty (LaTeX 2024-06-01)

This here should resolve this:

\DocumentMetadata{testphase={phase-III,table},pdfversion=1.7,uncompress}
\documentclass{article}
\usepackage{colortbl}
\makeatletter\ExplSyntaxOn
\IfFormatAtLeastTF{2024-06-01}{%
\long\def\multicolumn#1#2#3{%
   \multispan{#1}\begingroup
   \tbl_update_multicolumn_cell_data:n {#1}
   \def\@addamp{\if@firstamp \@firstampfalse \else
                \@preamerr 5\fi}%
   \@mkpream{#2}\@addtopreamble\@empty
   \endgroup
   \UseTaggingSocket{tbl/colspan}{#1}%
   \def\@sharp{#3}%
   \let\CT@cell@color\relax
   \let\CT@column@color\relax
   \let\CT@do@color\relax
   \@arstrut \@preamble
   \null
   \ignorespaces}}{}  
\ExplSyntaxOff
\begin{document}
\begin{tabular}{ll}
\multicolumn{2}{l}{\cellcolor{red}Test multicolumn}\\
\rowcolor{green} A & B \\
\end{tabular}

\end{document}

(An alternative would be to add the \let commands directly to array.sty?)

I'd like to keep de whole variability in grey level and angle of each character but with the option of justified text

I was trying to use mylatex, but compilation stops right at the beginning returning an "Undefined control sequence l.126 \makeatletter" error.
Here is the mwe:

\documentclass{article}
\usepackage{fontspec}
\usepackage{lipsum,showframe}
\begin{document}
\lipsum
\end{document}

which I tried to compile using lualatex -ini mylatex.ltx mwe.
I tried compiling this on Windows 10 Home 64-bit 1909 with TeXLive 2020 updated on the 28th of October.

Hi David,

Would it be possible to move some colortbl 's features to hhline ? For example, colortbl allows users to use the >{...} column modifier with hhline. However, I think it should be a default feature for hhline.

Mainly, it would allow users to change the width of the rules inside a \hhline command without having to load colortbl package. Something like this :

\hhline{->{\setlength{\arrayrulewidth}{0.8pt}}-}

I think it is absurd to load colortbl to be able to do this kind of tricks that are not related to color inside tables. As the developper of a LaTeX table generator, I would like to include a feature to control the width of specific rules, but this is an important limitation.

Thank you,

Xavier

I am transcribing a problem related to the use of textcase in TeX Live 2023 (63868 ) with brazilian characters (used in abntex2.sty).
It seems that the problem is related to brazilian accented characters.

13] [14] [15] [16] [17] [18] [19] [20]
(./abntex2-modelo-trabalho-academico.lof) [21] [22]
(./abntex2-modelo-trabalho-academico.loq) [23] [24]
(./abntex2-modelo-trabalho-academico.lot) [25] [26] [27] [28] [29{/usr/local/te
xlive/2023/texmf-dist/fonts/enc/dvips/lm/lm-rm.enc}{/usr/local/texlive/2023/tex
mf-dist/fonts/enc/dvips/lm/lm-mathit.enc}{/usr/local/texlive/2023/texmf-dist/fo
nts/enc/dvips/lm/lm-mathsy.enc}] [30] (./abntex2-modelo-trabalho-academico.toc
! Argument of \MakeUppercase (arg 1) has an extra }.
<inserted text>
                \par
l.13 ...Uppercase []{Introdução}}{33}{chapter.1}

This is described here (in portuguese): https://groups.google.com/g/abntex2/c/gXsyDKgTbQw

Downgrading textcase solves the problem:
tlmgr install --file textcase.r52092.tar.xz
tlmgr restore textcase 52092

I have no more information, but since I didn't see anything here, I imagined that at list registering it would be useful.

Thanks for your work.

I'm beginner use latex. Can you show me how to align tex at both the left and right in typewriter package? Thanks.

All use of the package, for example

\documentclass{article}

\usepackage{tabulary}

\begin{document}

\begin{tabulary}{1.0\linewidth}{L}
  x
\end{tabulary}
\end{document}

Produce the error message

! Missing \cr inserted.
<inserted text> 
                \cr 
l.9 \end{tabulary}
                  
? 

This should be fixed in the current head of this repository, but opening the issue for the record.

Consider the following examples:

--- abc.tex ---

\documentclass{article}
\begin{document}
abc
\end{document}

--- abc.ini ---

\input mylatex.ltx \relax%

Make a subdirectory named "build" by mkdir build.

Then the following command leads to error:
lualatex -ini --output-directory=build/ \&lualatex abc.ini "\nonstopmode" "\input" abc.tex
The output is

This is LuaHBTeX, Version 1.15.0 (TeX Live 2022)  (INITEX)
 restricted system commands enabled.
(./abc.ini
LaTeX2e <2021-11-15> patch level 1
 L3 programming layer <2022-02-24>
(/usr/local/texlive/2022/texmf-dist/tex/latex/mylatex/mylatex.ltx))
! I can't find file `'.
<to be read again> 
\nonstopmode 
<*> &lualatex abc.ini \nonstopmode
                                \input abc.tex
(Press Enter to retry, or Control-D to exit)
Please type another input file name:^D  
! Emergency stop.
<to be read again> 
\nonstopmode 
<*> &lualatex abc.ini \nonstopmode
                                \input abc.tex
 301 words of node memory still in use:
   1 hlist, 1 dir, 3 kern, 1 glyph, 1 attribute, 39 glue_spec, 1 attribute_list
 nodes
   avail lists: 2:10,3:3,4:1
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on abc.log.

However, any of the following variants runs without error:
lualatex -ini \&lualatex abc.ini "\nonstopmode" "\input" abc.tex (omitting --output-directory option)
lualatex -ini --output-directory=build/ \&lualatex abc.ini abc.tex (without \TeXcode \input syntax)
pdflatex -ini --output-directory=build/ \&pdflatex abc.ini "\nonstopmode" "\input" abc.tex (pdflatex instead of lualatex)
In other words, the error occurs only with the combination of lualatex, \TeXcode \input and --output-directory option. This affects preview-latex, subsystem of AUCTeX: https://lists.gnu.org/archive/html/auctex/2022-06/msg00020.html

Is there any fix or workaround for this error?

Originally posted by @ikumikeita in #15 (comment)

Hello,

I've got the following issue: the title of journal's article should be capitalized, text from \thanks{} inside the \title{} is \NoCaseChangeed, but \o is still capitalized. Here is MWE:

\documentclass{article}
\usepackage{textcase}

\makeatletter
\def\title#1{\gdef\@title{\MakeUppercase{#1}}}
\let\case@thanks\thanks
\def\thanks#1{\NoCaseChange{\case@thanks{#1}}}
\makeatother

\begin{document}
\title{My title\thanks{Thanks to Hedda Hassel M\o rch}}
\author{My Name}
\maketitle
\end{document}

Thanks,
Giedrius

As described in https://tex.stackexchange.com/questions/86211/colortbl-and-amsmath-conflict, after loading colortbl, one cannot use amsmath's align environment inside a table anymore.

commit c66feb4 adds a LaTeX counter alias so \roman{rownum} works like \romannumeral\rownum in the \rownum code imported from xcolor

The xcolor code only activates \rownum if \rowcolors is active which may have made sense to minimise the xcolor patch but feels wrong here, I have modifed the test file base result in that commit so it shows row 3 as III even without colors (so the test currently fails as this is not implemented)

@lvjr If this causes you problems please comment here. There is no rush to release anything to ctan so we can adjust things to avoid clashes.

\documentclass{article}
\pagestyle{empty}
\usepackage{colortbl,hhline} \setlength\arrayrulewidth{1pt}
\begin{document}
\begin{tabular}{c|c|c}
\hline
 A  & B  & C  \\ \hhline{= >{\arrayrulecolor{blue}}==}
100 & 10 & 1  \\ \hhline{=>{\arrayrulecolor{blue}}==}
\end{tabular}
\end{document}

First \hhline is completely black.

Specifically, case 5 does not work: the bold \alpha is not printed at all.

Hi, the bm doc (v1.2f, last revised 2023/07/08) says

In the fourth example the \mathrm{\bm{g}} is essentially equivalent to \mathrm{\mbox{\boldmath$g$}}

on page 3. I believe what is intended has an extra {} around the g

In the fourth example the \mathrm{\bm{{g}}} is essentially equivalent to \mathrm{\mbox{\boldmath$g$}}

The casual reader will have had difficulties tor reconcile the sentence without extra {} about the example 4 as above with the description of example 2 behaviour.

With the colortbl package, the optional overhang argument seems to be ignored when using \cellcolor. E.g., \cellcolor{red}[0pt] content prints [0pt] content into the corresponding table cell.

BTW, I'm not sure whether overhang specs are supposed to work with \cellcolor, but it isn't evident from the documentation that they shouldn't.

The following example shows tabulary is over-wide if p is used (but m works)

\documentclass{article}
\usepackage{tabulary}
\def\x{one two three four five six seven eight nine ten }
\def\xy{Red \x. Green \x\x. Blue\x. }
\def\xyz{\xy\xy}
\begin{document}

\noindent
\begin{tabulary}{\textwidth}{p{5cm}LL}
\xyz&\xyz&\xyz\\
1&2&3  
\end{tabulary}


\noindent
\begin{tabulary}{\textwidth}{m{5cm}LL}
\xyz&\xyz&\xyz\\
1&2&3  
\end{tabulary}
\end{document}

A user suggests

275c275
<   \ifnum\@chnum<4
---
 >   \ifnum\@chnum<6
369c369
<   \ifnum\@chnum<4
---
 >   \ifnum\@chnum<6

Which looks eminently plausible, although this code hasn't changed in any substantial way since last century...

Recording here. More analysis required on what the real intention was (although the current behaviour is clearly wrong)

It is difficult to get mylatex.ltx to work with filenames containing non-ascii characters (with pdflatex) since those are active (the everyjob execution done when first macro of mylatex.ltx is encountered when generating preamble gives to non-ascii characters their real inputenc+utf8 meanings).

(I have edited my initial wording which was erroneous)

$ etex -ini \&pdflatex mylatex.ltx ééé
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
 restricted \write18 enabled.
entering extended mode
(/usr/local/texlive/2018/texmf-dist/tex/latex/carlisle/mylatex.ltx
LaTeX2e <2018-04-01> patch level 5
) (/usr/local/texlive/2018/texmf-dist/tex/latex/tools/.tex File ignored)

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
<*> &pdflatex mylatex.ltx é
                            éé
? X
No pages of output.
Transcript written on mylatex.log.

Very recently commits have been pushed to AUCTeX and the development version is able to cope successfully (for pdftex engine, as xetex and luatex are not concerned by this of course) with using mylatex.ltx to generate cached preambles even for filenames with non-ascii characters (and spaces). Many years ago already a hack into \dump had been put in place by AUCTeX maintainer to cope with filenames containing spaces. (not contiguous)

Thus signalling this issue for it to get documented perhaps, but not pushing too much for a fix as this will probably break the AUCTeX manoeuvers ;-)

Dear David,

first of all thank you for your work on all these useful LaTeX packages! While reviewing the changes to longtable.sty I've noticed some inconsistency compared to the original patch. I believe that the line

\ifLT@ivcompat\global\vsize\@colroom\fi  

should rather be

\ifLT@ivcompat\else\global\vsize\@colroom\fi  

Cheers,
Andrzej

Hi David,
I am not a programmer in any sense, but know enough to be able to make a real mess. Anyway, is there a way to set the font from the .tex file instead of at the .sty level?

First I would like to thank you for your immense contribution and brilliant work! Your font system was really what I needed! However, for my language, I need some characters with punctuation, could you please provide the basic information on how I can do this?

Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ó (U+00F3) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ô (U+00F4) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no É (U+00C9) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no á (U+00E1) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ê (U+00EA) in font cmtt10x!
Missing character: There is no í (U+00ED) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ç (U+00E7) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!
Missing character: There is no ã (U+00E3) in font cmtt10x!

The sansmathaccent package (used by beamer) wants to setup some math fonts as late as possible (to be able not to do it if the preamble changed the settings) but before bm (as it doesn't work later). Currently is used the filehook package and its \AtBeginOfFile command, but this breaks in some documents due to an incompability with scrlfile.

Couldn't bm add some hook for font setup so that filehook is no longer needed in such cases?

\RequirePackage{filehook}
\def\AtBeginOfFile#1#2{}%disable filehook command in sansmathaccent
\documentclass{beamer}
%\usepackage{bm} %doesn't work, accent wrong
% how to activate this only if bm is loaded?
\DeclareSymbolFont{pureletters}{OT1}{mathkerncmss}{m}{sl}
\SetSymbolFont    {pureletters}{bold}{OT1}{mathkerncmss}{bx}{sl}

\usepackage{bm}
\begin{document}
\begin{frame}
$\tilde{M} \bm{\tilde{M}}$
\end{frame}
\end{document}

Dear David,

Thank you very much for this lovely .sty.

On Ubuntu 18.04 with TeXstudio 2.12.6 (6631:16db084dae24), lualatex (This is LuaTeX, Version 1.0.4 (TeX Live 2017/Debian)), some mathmatical symbols do not appear.
In addition to them, \mathbb{N} also does not work.

Hello.
First, let me thank you for your package numdef.sty. I use it a lot.
Today, I encountered an issue with fp package (\FPeval command). see below :

\num\FPeval\field1{1/7}            % Command  \field1 is created
field1 = \field1                   % and is correctly displayed
	
\num\FPeval\field2{2*\field1}      % This fails!
field2 = \field2	

Here is the error message:

! Argument of \doaction has an extra }.
<inserted text> 
                \par 
l.48 	\num\FPeval\field2{2*\protect\field1}
                                           
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.

Runaway argument?
 ]0.142857142857142857\FP@upn@debug {+++ result of upn-expression is \ETC.
! Paragraph ended before \doaction was complete.
<to be read again> 
                   \par 
l.48 	\num\FPeval\field2{2*\field1}
                                           
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.

I also tried this: \num\FPeval\field2{2*\ptotect\field1} and \num\FPeval\field2{2*\field{1}} but it failed too.
Do you think of a workaround?
Maybe have I missed something...

Thank you in advance!

On
https://tex.stackexchange.com/questions/63535/align-columns-in-multiple-tables/63544#63544
you show us a solution to get two longtables with the same width.

1. Should it be possible to include this feature directly in longtable.
2. Should it be possible to make it compatible with arydshln?

For the point 2, cf this problematic MWE.

\documentclass[]{article}
\usepackage[margin=0.5cm,landscape,a4paper]{geometry}
\usepackage{longtable}

\usepackage{arydshln}
\makeatletter
\def\dontchopLT{\let\LT@entry@chop\relax}
\def\resumeLT{%
\let\zzz\stepcounter
\def\yyy{LT@tables}
\def\stepcounter##1{%
  \def\xxx{##1}%
  \ifx\xxx\yyy\else\zzz{##1}\fi}}
\makeatother

\begin{document}
\centering





{\dontchopLT
\begin{longtable}{|c|c*{26}{|c}|}
  \hline
  ms&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s\\
  \hline
\end{longtable}}





{\resumeLT
\begin{longtable}{|c|c*{26}{|c}|}
  \hline
  ms&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s&s\\
  \hline
\end{longtable}}

\end{document}

I used longtable and booktabs. For some reason I wanted only normal lines instead of the\toprule etc commands.
I used

\let\toprule\hline
\let\midrule\hline
\let\bottomrule\hline

for a short test. The lines of the first and last column now filled the complete text width.
Is this the intended behaviour with up-to-date TL2024?

\documentclass{article}

\usepackage{longtable}
%\usepackage{booktabs}

\let\toprule\hline
\let\midrule\hline
\let\bottomrule\hline

\begin{document}

\begin{longtable}{l|c|r} 
\caption{Multipage table.}\label{tab:table1}\\\toprule 
\emph{Value 1} & {\emph{Value 2}} & \emph{Value 3}\\
$\alpha$ & $\beta$ & {$\gamma$} \\\midrule
\endfirsthead                 
\toprule
\emph{Value 1} & {\emph{Value 2}} & \emph{Value 3}\\
$\alpha$ & $\beta$ & {$\gamma$} \\\midrule
\endhead                      
\midrule 
\multicolumn{3}{r}{Fortsetzung $\rightarrow$}\\ 
\endfoot 
\bottomrule
\endlastfoot 
1 & 1110.1 & a\\  2 & 10.1 & b\\  3 & 23.113231 & c\\  1 & 1110.1 & a\\  2 & 
10.1 & b\\  3 & 23.113231 & c\\
1 & 1110.1 & a\\  2 & 10.1 & b\\  3 & 23.113231 & c\\  1 & 1110.1 & a\\  2 & 
10.1 & b\\  3 & 23.113231 & c\\
\end{longtable}

Changing all to \hline instead of the \let commands works fine.

The command \providecommand\ttfontsize{20pt} written before the \usepackage{typewriter} command is thoroughly ignored. Not a warning, not a change in the document.
I tried various sizes.

from https://tex.stackexchange.com/questions/514498/beginfilecontentstabelle-tex-will-not-overwrite-existing-file

\documentclass{article}
\usepackage{etex}
\begin{filecontents}[overwrite]{ipsum.tex}
  dolor
\end{filecontents}
\begin{document}
  \input{ipsum.tex}
  sit
\end{document}

gives at the second compilation, when filecontents tries to overwrite the file

! No room for a new \write .
\ch@ck ...\else \errmessage {No room for a new #3}
                                                  \fi 
l.237 \begin{filecontents}[overwrite]{ipsum.tex}
                                                
? 

! LaTeX Error: Trying to overwrite `test-utf8.tex'.

Consider this file abc.tex

\documentclass{article}
\begin{document}
abc
\end{document}

and try to generate a format:

$ xetex -ini \&xelatex mylatex.ltx abc
This is XeTeX, Version 3.14159265-2.6-0.99999 (TeX Live 2018) (INITEX)
 restricted \write18 enabled.
entering extended mode
(/usr/local/texlive/2018/texmf-dist/tex/latex/carlisle/mylatex.ltx
LaTeX2e <2018-04-01> patch level 5
) (./abc.tex (/usr/local/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/size10.clo)) )
Beginning to dump on file mylatex.fmt
 (preloaded format=mylatex 2018.6.1)
71708 strings of total length 90452
59166 memory locations dumped; current usage is 348&56891
4228 multiletter control sequences
\font\nullfont=nullfont
\font\OMX/cmex/m/n/5=cmex10
\font\tenln=line10
\font\tenlnw=linew10
\font\tencirc=lcircle10
\font\tencircw=lcirclew10
\font\OT1/cmr/m/n/5=cmr5
\font\OT1/cmr/m/n/7=cmr7
\font\OT1/cmr/m/n/10=cmr10
\font\OML/cmm/m/it/5=cmmi5
\font\OML/cmm/m/it/7=cmmi7
\font\OML/cmm/m/it/10=cmmi10
\font\OMS/cmsy/m/n/5=cmsy5
\font\OMS/cmsy/m/n/7=cmsy7
\font\OMS/cmsy/m/n/10=cmsy10
\font\TU/lmr/m/n/10=[lmroman10-regular]:mapping=tex-text;
! Can't \dump a format with native fonts or font-mappings.
<*> &xelatex mylatex.ltx abc
                            
? H
You really, really don't want to do this.
It won't work, and only confuses me.
(Load them at runtime, not as part of the format file.)

? X
No pages of output.
Transcript written on mylatex.log.

see this TeX.SE question for details : How to change text color with typewriter package?.

It seems that the xcolor package doesn't work to get colored text with the typewriter package.

As some of us are forced to do bad things, it would be great if it was possible to put the \caption below the longtable, as of now this is not possible with the package like it is, as it misses the ability to define a special first foot. Therefore \endfirstfoot would be much appreciated.

There is a working version of \endfirstfoot on TeX.SX from Heiko Oberdiek: https://tex.stackexchange.com/a/68448/117050

It only has issues with hyperlinks by hyperref.

Hi David,

I shared your new package on the lilypond-user list (http://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00426.html), and apart from very interested feedback a discussion arose about whether typewriter fonts should have double spaces after punctuation.

There was no definite conclusion but it seems that in some languages/cultures two spaces are required after the fullstop while in others only one is to be used.

I would suggest to make the package behave similarly to regular typesetting with LaTeX: by default print two spaces, and when \frenchspacing is active print only one.

Dear David,

The following variation of the sample file provided in LaTeX bugs database entry tools/3512 still causes text to overflow the bottom of the page.

\documentclass[a4paper,12pt]{article}
\usepackage{longtable}
% Viel Text erzeugen
\newcommand{\baz}{foo foo foo foo foo foo foo foo}
\newcommand{\qux}{\baz\baz\baz\baz\baz\baz\baz\baz}
\begin{document}

\begin{figure}\vspace{5cm}\end{figure}

\begin{longtable}{llll}
bar & bar & bar & bar
\end{longtable}

\begin{figure}\vspace{5cm}\end{figure}

\qux\qux\qux\qux\qux\qux\qux\qux
\qux\qux\qux\qux\qux\qux\qux\qux
\end{document}

I believe this behaviour is what the following comment from StackExchange question 203629 also refers to:

When I say it fixed it I mean it fixed my issue where I had 1 float and 1 longtable, not 1 long table with a float before and after. – Dalupus Oct 18 '14 at 15:33

Cheers,
Yvan

When attempting to compile

\documentclass[preview]{standalone}

\usepackage[english]{babel}
\usepackage{amsmath}
\usepackage{amssymb}

\begin{document}

\begin{align*}
\psi(x) = 1.67
\end{align*}

\end{document}

I get

C:\Users\Daryl\dev\speedup-latex>latex -ini mylatex.ltx 1db01b6b2822b336.tex
This is pdfTeX, Version 3.141592653-2.6-1.40.23 (TeX Live 2021/W32TeX) (INITEX)
 restricted \write18 enabled.
(c:/texlive/2021/texmf-dist/tex/latex/mylatex/mylatex.ltx
! Undefined control sequence.
l.126 \makeatletter

?

I have a calendar document that I build every day where I color cells with \cellcolor - today, all of the empty cells looked really weird, see the following minimal working example:

\documentclass[border=.2cm]{standalone}

\usepackage{xcolor}
\usepackage{colortbl}

\begin{document}

  \begin{tabular}{|p{4cm}|c|}
    \hline
    \multicolumn{2}{|l|}{
      \cellcolor{blue!20}
      Die Hintergrundfarbe der nächsten Zelle ist kaputt:
    } \\
    \cellcolor{red!40} &
    \cellcolor{red!40} \\
    \multicolumn{2}{|l|}{
      \cellcolor{blue!20}
      Mit \texttt{\textbackslash hfill} geht es:
    } \\
    \cellcolor{orange!40} \hfill &
    \cellcolor{orange!40} \hfill \\
    \multicolumn{2}{|l|}{
      \cellcolor{blue!20}
      Mit anderem Inhalt auch:
    } \\
    \cellcolor{green!40} hallo &
    \cellcolor{green!40} hallo \\ \hline
  \end{tabular}

\end{document}

I assume that this is due to a recent update to colortbl?

If I run pslatex -help, latex will complain with ! I can't find file `-help'., because it receives the literal "-help" which gets interpreted as a file name instead of an option.

It all comes from the line

Hello,

yesterday I bothered you in TeX LaTeX StackExchange with my attempts of compiling the program dvipaste for debian buster.

I have an i386-vanilla TeX-Live-installation:

• LaTeX2e <2020-10-01> patch level 4
• L3 programming layer <2021-01-09>
• xparse <2020-03-03>
• dvips.def 2017/06/20 v3.1d

I now managed to get a binary which, apart from one problem, seems to work on debian buster:

• The test-suite provided in the dvipaste-package, where dvi-files are created via plain TeX, works.

• But with my vanilla TeX-Live-installation the test-suite provided by the package grfpaste, where dvi-files are created via LaTeX, works out only if the .dvi-files that are to be pasted are created while the following two conditions are met:

  1. An older dvips.def is in use. (I tested with dvips.def 2014/04/23 v3.0j which I copied from my old Win95-MiKTeX2.4-installation to the directory where grfp1.tex, gefp2.tex and grfp3.tex are stored.)
  2. l3backend-dvips.def is "neutralized" by placing an empty file l3backend-dvips.def into the directory where the files to compile are placed.

  Seems these conditions need to be met for the .dvi-files that are to be pasted but don't need to be met for the .dvi-file where stuff is to be pasted to.

As long as I just compile grfp1.tex and grfp2.tex on my up-to-date vanilla TeX Live installation in the more recent debian-buster platform with recent dvips.def and with l3backend-dvips.def not "neutralized", i.e., without obeying these conditions, and then apply my dvipaste-binary for debian-buster, within the resulting .dvi-file those copied portions do not show up that stem from the first \sendout/from the first page of a .dvi-file whose content is to be copied.

By the way:

When I compile grfp1.tex and grfp2.tex and grfp3.tex on my old Win95-MiKTeX2.4-installation and do not apply the DOS-binary (DVIPASTE.EXE) shipped along with the dvipaste-package but move the resulting .dvi-files to my more recent debian buster-platform and apply the dvipaste-binary created for the more recent debian-buster-platform, then everything works out also.

For control:

Vice versa: When I compile grfp1.tex and grfp2.tex and grfp3.tex on my up-to-date vanilla TeX Live installation in the more recent debian-buster platform (with recent dvips.def and with l3backend-dvips.def not "neutralized") and do not apply the dvipaste-binary created for the more-recent debian-buster-platform, but move the resulting .dvi-files to my old Win95-MiKTeX2.4-installation and apply the DOS-binary (DVIPASTE.EXE) shipped along with the dvipaste-package, then things don't work out on the old platform.

When I compile grfp1.tex and grfp2.tex and grfp3.tex on my old Win95-MiKTeX2.4-installation and on that old platform do apply the DOS-binary (DVIPASTE.EXE) shipped along with the dvipaste-package, then everything works out.

In short:

( ⟨.dvi-files compiled with LaTeX on platform⟩ ) AND ( ⟨dvipaste-binary of platform⟩ ) → ⟨result⟩.

(.dvi-files compiled with LaTeX - TeX Live 2020/debian buster) AND (dvipaste-binary of TeX Live 2020/debian buster) → things don't work out.

(.dvi-files compiled with LaTeX - TeX Live 2020/debian buster) AND (dvipaste-binary of Win95/MiKTeX 2.4) → things don't work out.

(.dvi-files compiled with LaTeX on Win95/MiKTeX 2.4) AND (dvipaste-binary of Win95/MiKTeX 2.4) → things do work out.

(.dvi-files compiled with LaTeX on Win95/MiKTeX 2.4) AND (dvipaste-binary of TeX Live 2020/debian buster) → things do work out.

(.dvi-files compiled with LaTeX - TeX Live 2020/debian buster with old dvips.def and with l3backend-dvips.def neutralized) AND (dvipaste-binary of TeX Live 2020/debian buster) → things do work out.

(.dvi-fFiles compiled with LaTeX - TeX Live 2020/debian buster with old dvips.def and with l3backend-dvips.def neutralized) AND (dvipaste-binary of Win95/MiKTeX 2.4) → things do work out.

In order to obtain that binary I compiled via sudo make all after doing the following changes:

In dvipaste.c I removed the lines:

1247  #ifndef MICROSOFTC
1248  #define strnicmp strncmp
1249  #define strcmp strcmp
1250  #endif

Reason:

1248 #define strnicmp strncmp

This is for handling the situation of using a c-compiler where strnicmp is not defined. strnicmp, if defined, usually is case-insensitive comparing of n characters of a string while strncmp usually is case-sensitive comparing of n characters of a string. I suppose case-insensitive comparing shouldn't be turned into case-sensitive comparing except when comparing filenames and turning from a system with case-insensitive file names (e.g., MS-DOS) to a system with case-sensitive filenames (e.g., some Unix/Linux).

1249 #define strcmp strcmp - is redundant.

I used the following config.h

#define ANSI /* To use ANSI functions instead of old-style K&R functions. */
#undef MICROSOFTC
#define LITTLENDIAN
#ifndef MICROSOFTC
/* Despite the phrase "case" being in the functions' names */
/* strncasecmp/strcasecmp do case-insensitive comparing. */
#define strnicmp strncasecmp
#define stricmp strcasecmp
/* Seems K&R c didn't need the following two includes. */
/* Dunno if checking for MICROSOFTC not being defined */
/* or checking for ANSI being defined is the appropriate */
/* condition for inclusion. In my scenario both conditions */
/* are met. */
#include <unistd.h>
#include <stdlib.h>
#endif
#ifdef ANSI
/* Other things in ANSI C are good, but this is a crock */
#define READ_BINARY "rb"
#define WRITE_BINARY "wb"
#else
/* The good old simple and logical K&R I/O */
#define READ_BINARY "r"
#define WRITE_BINARY "w"
#endif

I did not yet find the time to track down what goes wrong in dvipaste when using newer dvips.def and non-neutralized l3backend-dvips.def.

I suppose the problem has to do with the ways in which dvipaste "decides" what to copy into the target .dvi-file and that therefore the algorithms implemented in the dvipaste-program would need some alteration.

But my c-knowledge is rusty. The first and last time I was seriously confronted with c-programming was during a course at the university in 1998. (Back in school we had to program everything in Pascal. BASIC and Turbo Assembler were en vogue also.) So the undertaking of grasping dvipaste.c and probably modifying it correctly would take some time.

Thank you for taking the time to read through my elaborations. ;-)

Sincerely

Ulrich

Hello,
I noticed that colortbl "breaks" '\hdotsfor' command from amsmath package. Please consider the following two examples.

First example without package 'colortbl':

\documentclass{article}

\usepackage{amsmath}

\begin{document}

This is an example borrowed from the amsmath package documentation:
\begin{equation}
  \begin{pmatrix}
    D_1t&-a_{12}t_2&\dots&-a_{1n}t_n\\
    -a_{21}t_1&D_2t&\dots&-a_{2n}t_n\\
    \hdotsfor[2]{4}\\
    -a_{n1}t_1&-a_{n2}t_2&\dots&D_nt
  \end{pmatrix}
\end{equation}

\end{document}

Second example, with package 'colortbl'

\documentclass{article}

\usepackage{colortbl}
\usepackage{amsmath}

\begin{document}

This is an example borrowed from the amsmath package documentation:
\begin{equation}
  \begin{pmatrix}
    D_1t&-a_{12}t_2&\dots&-a_{1n}t_n\\
    -a_{21}t_1&D_2t&\dots&-a_{2n}t_n\\
    \hdotsfor[2]{4}\\
    -a_{n1}t_1&-a_{n2}t_2&\dots&D_nt
  \end{pmatrix}
\end{equation}

\end{document}

The second example shows that '\hdotsfor' command works differently when the 'colortbl' package is used.

https://tex.stackexchange.com/a/119575

numdef has been life savior for me for a while (Found it here). Thanks a lot for it.

Unfortunately, I am facing difficulty to make \listoffigures work properly with it. I am using pdflatex on Linux. Here is a simple code to reproduce the error:

\documentclass{article}
\usepackage{amsmath, amssymb, amsfonts}

\usepackage{numdef} 
\num\newcommand{\B0}[0]{B$_{\text{0}}$}

\begin{document}
\listoffigures % works fine without this line

Hello world! This is \B0.

\begin{figure}
  \centering
  Here goes the fig..
  \caption{Hello again! This is \B0-caption.}
\end{figure}

\end{document}

Here is the error:

$ pdflatex test.tex 
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
 restricted \write18 enabled.
entering extended mode
(./test.tex
LaTeX2e <2011/06/27>
Babel <3.9h> and hyphenation patterns for 2 languages loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/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/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/home/cbhushan/texmf/tex/latex/local/numdef.sty) (./test.aux) (./test.lof
(./test.lof (./test.lof (./test.lof (./test.lof (./test.lof (./test.lof
(./test.lof (./test.lof (./test.lof (./test.lof (./test.lof (./test.lof
(./test.lof
! TeX capacity exceeded, sorry [text input levels=15].
\@filef@und ->test.lof 

l.1 ...B$_{\text {0}}$\num@count = 0-caption.}}{1}

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on test.log.

And here is the content of test.lof (test.log is similar to the output above).

\contentsline {figure}{\numberline {1}{\ignorespaces Hello again! This is \edef \B {\B }\futurelet \@tempa \let \afterassignment \let 0=0B$_{\text {0}}$\num@count = \afterassignment \let 0=0B$_{\text {0}}$\num@count = \afterassignment \let 0=0B$_{\text {0}}$\num@count = 0-caption.}}{1}

This document prints the head twice on the second page:

\documentclass{article}
\usepackage{longtable}
\begin{document}
\vspace*{42\baselineskip}

\begin{longtable}{l}
\caption{title}\endhead
abc\\
abc
\end{longtable}

\end{document}

The issue disappears if one add this patch:

\documentclass{article}
\usepackage{longtable}
\usepackage{xpatch}
\makeatletter
\xpatchcmd\LT@start{\vskip\LTpre}{\vskip\LTpre\endgraf}{}{\fail}
\makeatother
\begin{document}
\vspace*{42\baselineskip}

\begin{longtable}{l}
\caption{title}\endhead
abc\\
abc
\end{longtable}

\end{document}

Following source throws an error (blkarray 2015/02/27 v0.07):

\documentclass{article}
\usepackage{blkarray}
\begin{document}
\begin{blockarray}{lrr}
\hline 
Aaa & Bbb & Ccc \\ \hline
Ddd\footnote{footnote-d} & Eee & Fff \\
Ggg\footnote{footnote-g} & Hhh & Iii \\ \hline
\end{blockarray}
\end{document}

! TeX capacity exceeded, sorry [input stack size=5000].
\font@name ->
            \OMX/cmex/m/n/5 
l.11 \end{blockarray}

It seems like infitnite loop inside \textasteriskcentered etc.

The change of definition of @fnsymbol at LaTeX2e 2015/01/01 seems critical; actually, adding following code after \usepackage{blkarray} works fine:

\makeatletter
\def\BA@fnsymbol#1{\ensuremath{%
   \ifcase#1\or *\or \dagger\or \ddagger\or \mathsection\or
     \mathparagraph\or \|\or **\or \dagger\dagger
     \or \ddagger\ddagger \else\@ctrerr\fi}}%
\makeatother

Can this problem be solved? Thanks.

Dear David,

Thanks for provided XML supported latex package and could you have latest all mathml supported xmt file?

The parameters l and c for the tabular environment are no longer working since the last update of the package in texlive 2024. It is still working in texlive 2023 which does not have the update of the colortbl package.
\begin{tabular}{cl}
...
\end{tabular}
throws an error "Undefinded control sequence ... \adl@dashcolor ..."

see this TeX.SE question for details : How to use the typewriter package "locally"?.

Is there a way to enclose the effects of the typewriter package locally, into an enviroment for exemple (with something like \typewriterON...\typewriterOFF or \begin{typewriter}..\end{typewriter})?

\usepackage{colortbl} changes the spacing of tables even when no other commands from the package are used.

Minimal reproduction

\documentclass{article}
\usepackage{colortbl}  % comment this line out to show difference

\begin{document}

\begin{tabular}{|l|c|}
  one&two\\
  three&four
\end{tabular}

$
\begin{array}{ccc}
  ~1~&~2~&~3~&~4~&~5~&~6~&~7~&~8~&~9
\end{array}
$

\end{document}

Without importing colortbl:

Importing colortbl using \usepackage{colortbl}:

The difference is easier to see when superimposing both PDFs (red is without importing, blue is with \usepackage{colortbl}:

Files for reproduction

no_import.log
no_import.pdf
with_import.log
with_import.pdf

Dear David, thanks for your new package! I have just added it to my regular column about new packages on CTAN for the next issue of TeXnische Komödie. I think it's a nice idea to have it at hand, but I wonder whether simulating a typewriter as it used to be in the 1960s really would mean to have it typeset characters at a random quality? As far as I remember, typewriters used to produce a layout that was very much the same for each character you typed. E.g., every lower case e used to look the same because the lever in the typewriter that printed the character on the sheet of paper had a characteristically singular mechanics. This was so singular that even the police could recognise which typewriter was used to produce a particular letter etc. So, you might like to drop the idea of typesetting characters "at random" instead of making them unique one by one, in fact in order to reduce variety in output. Typewriters produced a move vivid layout, that's right, but not that lively, I'm afraid. ;) Cheers, Jürgen.

The following MCE:

\documentclass{article}
\usepackage{textcase}
\begin{document}
\MakeTextLowercase{Café}
\end{document}

used to compile (with pdflatex) like a charm with an up to date TL 2021 but, with an up to date TL 2022, that's not the case anymore:

! LaTeX Error: Invalid UTF-8 byte sequence (��\ifx).

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.24 \MakeTextLowercase{Café}