Closed schoeps closed 9 months ago
Color is there, but the case changing is breaking it.
Actually – you should not use the color directly in there but you can wrap it…
\documentclass[design=2023]{tudabeamer}
\begin{document}
\begin{frame}{Test \NoCaseChange{\textcolor{TUDa-1b}{\MakeUppercase{Test}}}}
\end{frame}
\end{document}
And thanks for providing an example for the documentation!
I am personally not a big fan of colors in headlines but people sometimes want to use it anyway... can we fix it globally? Is there a way to sneak in the color definitions into the capitalization (which I am also not a fan of :) ).
Sure there is, but it will confuse users even more if it works for those colors but not for others. So I don't think it's a good idea.
What would work for those users would be creating some macro taking care of it. Those are handled without case change. Just arguments are not.
edit: Other option would be to only use Uppercase for the font there, this requires fontspec. But that would lead to the different results for text copied out of the document.
Would it be enough to define the TUDa colors (additionally) in capitals?
Yes. For that specific usecase it would work. But as I said I don't think it's a good idea to do that in the bundle. People who are debugging might be confused of this.
I still will use your example for the docs and I will also add an option to deactivate the case change using an option, as there might be more complex use cases.
TUDa colors seem to be not available in frametitles: