diff options
author | Vladimír Vondruš <mosra@centrum.cz> | 2017-11-25 17:37:26 (GMT) |
---|---|---|
committer | Vladimír Vondruš <mosra@centrum.cz> | 2017-11-25 17:37:26 (GMT) |
commit | b6a7abf02652b74872b9c676fcfa545e18d9bde7 (patch) | |
tree | f6ba2e5962f62fbf27f2058e241b36ae5adc373c /testing/example_test.cpp | |
parent | 4f45bd20d4da7d40c793ec4c4c13558581e995ac (diff) | |
download | Doxygen-b6a7abf02652b74872b9c676fcfa545e18d9bde7.zip Doxygen-b6a7abf02652b74872b9c676fcfa545e18d9bde7.tar.gz Doxygen-b6a7abf02652b74872b9c676fcfa545e18d9bde7.tar.bz2 |
Encode invalid XML characters instead of skipping them.
The <sp> element in <programlisting> has a new optional attribute
`value`, which contains value of given invalid ASCII character. In
case of space, the `value` attribute is omitted.
Use cases for this: including snippets of *very esoteric* languages,
markup that makes use of the advanced ASCII formatting characters or
for example highlighting a console output containing ANSI color codes
(which is my case, in fact).
Regarding backwards compatibility -- as files with such ASCII
characters are very rare, I don't expect this minor difference in the
output to be a problem. Besides that, such ASCII characters are often
replaced by a space in many applications anyway.
A test snippet was extended to contain a special character so this
difference in behavior could be verified.
Diffstat (limited to 'testing/example_test.cpp')
-rw-r--r-- | testing/example_test.cpp | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/testing/example_test.cpp b/testing/example_test.cpp index f589023..a117b63 100644 --- a/testing/example_test.cpp +++ b/testing/example_test.cpp @@ -1,5 +1,7 @@ void main() { + const char* a = "Some special character here: "; + Test t; t.example(); } |