David Carlisle

please provide a small test document, also is the problem still there with `texlive revision: 67755` ie ``` \ProvidesPackage{textcase} [2023/07/27 v1.04 Text only upper/lower case changing (DPC)] ```

I assume, although you do not mention it, or provide any example showing the problem, that this is about the typewriter package. The version here allows you to set the...

oh wow, I guess so, I must admit when I've wanted an html input in recent years I've hooked Henri Sivonen's java parser https://about.validator.nu/htmlparser/ as a sax parser for Saxon,...

you can also use `\NoCaseChange{\cref{...}}`

I'm certainly keen to incorporate amsmath patches from unicode-math and lualatextex-math.sty into amsmath, not so sure about breqn/flexisym which seem rather more experimental...

Mostly it's because you wrapped the term in `{...}` preventing line breaking. I removed that and also removed the nested `\text{$..` which didn't seem to be preventing line breaking in...

@nasser1 thanks yes that's essentially the same issue if you use the version in the branch https://github.com/wspr/breqn/tree/gh52 then you get the expected layout with texlive 2021

@u-fischer this is possibly enough, without introducing a new package dependency? ``` \documentclass{article} \usepackage{titlesec} \makeatletter \def\removelabel#1\label#2#3\label#4\relax{#1#3} \def\ttl@straight@i#1[#2]#3{% \expandafter\def\expandafter\@currentlabelname\expandafter{% \removelabel#2\label{}\label{}\relax}% for nameref \gdef\ttl@savemark{\csname#1mark\endcsname{#3}}% \let\ttl@savewrite\@empty \def\ttl@savetitle{#3}% \gdef\thetitle{\csname the#1\endcsname}% \if@noskipsec \leavevmode \fi \par...

@u-fischer hmm we could also fix this in the kernel by copying the normalization used by `\addtocontents` to `\label` ``` \documentclass{article} \usepackage{titlesec} \makeatletter \def\label#1{\@bsphack \begingroup \UseHookWithArguments{label}{1}{#1}% \protected@write\@auxout{% \let\label\@gobble \let\index\@gobble \let\glossary\@gobble%...

It's not a notation I've seen, of course there is no reason authors can't define it if they need it but I don't see that it's needed in a core...