Yes, exactly that. Especially with short examples. Can't be avoided with long ones.
I'll see what is possible to do.
I'll start working on conversion of
Atlantis Manual and I'll make a PR to your
documentationrework_part1_conversion There is already one waiting.
A PR on a PR...
never would have thought of that.
I see you are "fixing and correcting" things... IMO, for speed, that should be left for after the LaTeX conversion is finished. Not having to worry about whether, e.g., parameter x has more possible values has helped progress, as I only have to think about making the text show up with +/- the correct formatting. I'm signaling stuff that needs checking with TODOs as I happen to find them, but that is it, I'm not "derailing" the LaTeX train to go dig into the code, editing a file or running a sim to check something.
Another thing: the Atlantis manual should be inside the Orbiter User Manual, as opposed to being a separate file. Same for DG, ShuttleA, etc.
At the end we would have 3 pdf files:
Orbiter User Manual - explain Orbiter, how to configure and use it, along with the included vessels, MFDs and bases
Orbiter Developer Manual - addons, vessels, bases, planets, textures, meshes, code, lua, etc
Orbiter Technical Reference - collection of papers/articles detailing the theory behind some feature or capability
I'm just finishing another bunch of additions (tried to finish them yesterday, but gave up as I had been up for 21h) and will commit them soon. I'll then will have to leave for a while, but will be back later today.