ftilmann
OK, I had quick look. Great to see that it works out of the box by providing simply a new style option. This make is easy to accept in principle...
Very sorry about the delay - I merged without any further modifications. Thanks a lot for contributing this PR
Thanks for the reminder. Indeed that task got lost over the summer holidays. I just uploaded to 1.3.4 to CTAN - usually takes a little while until it is checked...
This is a known limitation. I cite from the documentation of latexdiff: > There is an incompatibility between the C package, which C uses for underlining and striking out in...
Closed as Duplicate of #188
Yes, indeed this looks like a way forward - I will need to test this and then put some logic in that does the markup correctly if lua-ul is imported,...
As there is a solution now when using lualatex and I can't do anything about the limitations of ulem, I am closing this
The simplest implementation would be to introduce another markupstyle UNDERLINE_LUA which would be activated with `latexdiff -t UNDERLINE_LUA`. The only issue I see with this is discoverability, as few people...
This has just bitten me: Following the installation instructions I got ``` (prs) ~/apps/pyraysum 43> pip install pyraysum Collecting pyraysum Using cached pyraysum-1.0.0.tar.gz (1.4 MB) Preparing metadata (setup.py) ... error...
In case of changes the markup will possibly not be very fine-grained, but at least identical parts with nested arrays will no longer throw an error.