Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This hack just changes in the DATA section: ulem -> lua-ul [normalem] -> \sout -> \strikeThrough \uwave -> \underLine When this is used, output must be compiled with lualatex. Some thoughts on implementing this in upstream latexdiff: 1. To make this an actual option, instead of hardcoding this change, one would probably want to make general commands that call the right ulem or lua-ul commnad, with separate preamble sections for either ulem: \RequirePackage[normalem]{ulem} \newcommand[1]{\DIFstrikethrough}{\sout{ftilmann#1}} \newcommand[1]{\DIFunderline}{\uwave{ftilmann#1}} or lua-ul \RequirePackage{lua-ul} \newcommand[1]{\DIFstrikethrough}{\strikeThrough{ftilmann#1}} \newcommand[1]{\DIFunderline}{\underLine{ftilmann#1}} and then could make these changes instead \RequirePackage[normalem]{ulem} -> \sout -> \DIFstrikethrough \uwave -> \underLine This, however, would require adding in the logic to have either lua-ul or ulem into the code. I also hope the indirection like this won't break some LaTeX macro somewhere but can't be sure of that. Other options I considered would be: - duplicating all these sections to have a ulem and a lua-ul version (yuck) - searching for these words and replacing them when reading in preamble sections (D:) - simply eliminating ulem support (working around it certainly seems to have caused a lot of headaches for the creators of latexdiff) 2. lua-ul doesn't have the capacity out of the box to produce wavy underlines like ulem, but is very configurable and it could be added. Instructions are even in the lua-ul manual.
- Loading branch information
cb6c513
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub changing TeX
#1
to a link to issue ftilmann#1 is unfortunate.