From 2890026598b46314fc611c0067e5a066b0a08bb9 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Thu, 16 Jan 2020 17:55:08 -0700 Subject: [PATCH] Work around a doxygen bug that triggers in step-10. --- doc/doxygen/scripts/make_step.pl | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/doxygen/scripts/make_step.pl b/doc/doxygen/scripts/make_step.pl index e1ef0704ac..0089ba82b4 100644 --- a/doc/doxygen/scripts/make_step.pl +++ b/doc/doxygen/scripts/make_step.pl @@ -87,6 +87,18 @@ print system $^X, "$cmake_source_dir/doc/doxygen/scripts/create_anchors", "$cmake_source_dir/examples/$step/doc/intro.dox"; + +# Start the commented program by writing two empty lines. We have had +# cases where the end of the intro.dox was missing a newline, and in +# that case doxygen might get confused about what is being added here +# to the end of an existing line. So add a newline. +# +# But then we also had a situation where doxygen was confused about a +# line starting with an anchor (see #9357). It's not clear what the +# cause is, but making sure that there is an empty line in between +# solves the problem -- so a second newline character. +print " *\n"; +print " *\n"; print " * \n"; print " *

The commented program

\n"; @@ -94,6 +106,11 @@ system $^X, "$cmake_source_dir/doc/doxygen/scripts/program2doxygen", "$cmake_sou system $^X, "$cmake_source_dir/doc/doxygen/scripts/create_anchors", "$cmake_source_dir/examples/$step/doc/results.dox"; + +# Move to the stripped, plain program. The same principle as above +# applies for newlines. +print " *\n"; +print " *\n"; print "

The plain program

-- 2.39.5