Stefan Richthofer

I think a Javadoc comment ``/** ... */`` does in general not support backslash-escaping. The content is much like html. It rather supports ``&blah;`` escaping. I will check how actual...

It turns out that there is indeed one type of backslash escape sequence supported by Javadoc: that of the form ``\uxxxx`` for arbitrary unicode characters. I ran the following test...

``` /** * * x\x y\y * * x\\x y\\y * * x\nx y\ny * * x\tx y\ty * * x\"x y\"y * * x\u1234x y\u1234y * * x"x y"y...

One thing to mention about ``\uXXXX``: Doxygen does currently not support this way to enter unicode. On the other hand I recognized that Javadoc often rejects ``&#YYYY;`` I cannot tell...

Also worth noting: The unicode marker ``u`` may optionally be doubled, so ``\uuXXXX`` is also a valid input. I checked that this is also accepted by Javadoc, e.g. ``x\uu1234x y\uu1234y``...

I noticed that Doxygen does not treat ``\`` as an escape character when used in a ``{@code ... }`` environment. I guess this is also the case for some or...

Attempting to convert it to ``\`` turns out even worse. It is completely removed outside of ``code`` or ``verbatim``. Inside it is turned into ``\``. Is that the right behavior...

For the record, I now help myself with a filter that replaces all backslashes by ``\`` (instead of ``\``); I guess after your commit, also ``\`` would do. Anyway, I...