David Carlisle

I can't think of a reason (nor is one documented) although test coverage is rather sketchy...

We should probably highlight this more, but the command needs to be protected ``` \documentclass{article} \begin{document} \protected\def\DontChangeCase#1{\textit{#1}} \MakeUppercase{This is \NoCaseChange{\DontChangeCase{obviously}} working.} \AddToNoCaseChangeList{\DontChangeCase} \MakeUppercase{This is \DontChangeCase{not} working!} \expandafter\show\csname l_text_case_exclude_arg_tl\endcsname \end{document} ```

@josephwright you mean support un `\protected` commands, as in the original example here?

@josephwright I'm not sure I see that? if I have `\def\Name#1{}` and add it to No case change list, I may still want this to be expanded out by `\text_expand:n`...

@mrpiggi you can (locally if necessary) define the command as something like `\def\foo#1#2#3{\NoCaseChange{\realfoo{#1}{#2}{#3}}}` which will make the three argument `\foo` grab all three arguments and guard them from the case...

doesn't the `\hypersetup` usage in Juan's answer on the page you link to work for you? (also please note that questions are better asked on stackexchange, this is a bug...

Ok thanks for the test file. I can confirm that it doesn't work, but this is a feature request rather than a bug, I think. As far as I can...

A small clarification on my last comment having read more of the dvisvgm manual again... dvisvgm does explicitly support the html-based hypertex specials but these are somewhat limited (predating hyperref)...

Actually I'm going to re-open this, as I say it may be possible to use literal svg specials to do more even without explicit link annotation support in the driver...

I'll leave Frank to ponder on the best way to track font substitutions, but an alternative approach to the particular use case would be to select the font and then...