ftilmann

I am sorry that you wasted so much time on finding the bug. Fixing this would essentially entail copying both input files old.tex and new.tex into a temporary file, which...

Can you make your input files available (it must be possible for me to download the very exact bytes), ideally reduced to a minimum set that still reproduces the error....

If you find out your encoding (for example latin9), and you use `\usepackage[latin9]{encoding}` in the first 20 lines of your preamble (obviously replace latin9 as appropriate), then it should work...

Maybe you can try `--encoding=ascii` option to latexdiff (or the encoding your text uses, if you know it). If the offending characters are just in the comments I expect this...

Yes, tabular is a weakness - other have pointed out similar issues. I need to think of a way to deal with all the possibilities in a robust way.

latexdiff by default excludes from markup all commands except 'white-listed' ones known to contain only text. With the option `--append-context2cmd=newglossaryentry` you essentially tell latexdiff that \newglossaryentry's second argument is text...

The only actual 'fix' is of course to remove the --append-context2cmd option but of course it leaves your changes in the glossary unmarked.

@megies There are two sub-issues I raised: 1. The azimuth calculation as currently implemented is wrong - a code change is needed here, and this cannot be addressed with a...

I can see the problem but this would be very difficult to fix as latexdiff would have to follow the whole logic of the conditional expressions. The promise of latexdiff...

Note to myself: Indeed this PR is breaking the standard verbatim environment so will put this on hold for now. minted seems quite a popular package, so still worth keeping...