Last codeblock REP 103 renders message comments as headings

[SuperJappie08]

I noticed that the last codeblock of REP-103 is rendering incorrectly.
Some comments have been converted to headings.

• Original (Web): REP 103
• New (Web): REP 103

Original RST:

https://github.com/ros-infrastructure/rep/blob/11ca24a41f31480dfb9562ba99f2a5b93d3ebda5/rep-0103.rst?plain=1#L191-L199

New MarkDown

reps/_posts/rep-0103.md

Lines 165 to 171 in 0dded92

	Six Dimensional
	# # Row-major representation of the 6x6 covariance matrix
	# # The orientation parameters use a fixed-axis representation.
	# # In order, the parameters are:
	# # (x, y, z, rotation about X axis, rotation about Y axis, rotation about Z axis)
	float64[36] covariance

Note

If the conversion process was automated, this might have happened more often.

[SuperJappie08]

REP 107 is also affected.

[SuperJappie08]

A quick regex search on the markdown files (/^#\s+#/) has identified the following affected REPs per error category:

Comments as Headings

• 103: Message comments as headings
• 104
• 107
• 126: Some shell comments as heading
• 136: last code block
• 147

Comments added to the line above with extra '# ' characters

• 12: Literal codeblock example
• 112: Manifest example
• 126: Shell comments, but also as heading
• 133: Custom envhook example
• 137: All YAML comments
• 141: YAML Block comments
• 2008: CMake Comments

Others

• 12, 104, 112, 133: Some strange new content at the bottom, near Copyright (I noticed this quite late, maybe I missed a few)
• 137: Random [_config]{.title-ref} sections in the webpage
• 147: Mermaid graph rendering
• 2008: Multiple RST block annotations left in Markdown

[SuperJappie08]

@tfoote, I've noticed a lot of these lines were last edited by you in 3a048ab.
Could something have gone weird there?

[tfoote]

Yeah, this was a script. Thanks for identifying those places. We had noticed the tables had failed but not inside the code blocks

[SuperJappie08]

Maybe it is possible to switch to ``` style codeblocks.
Potentially syntax highlighting could also be enabled (by specifying the language).

EDIT: I am not sure if that is supported in all MarkDown flavors by default.

[tfoote]

I think this should be github flavored markdown so the ``` should work.