Rob/Sean...
It looks like the root of the recent issue Sean discovered (
https://groups.google.com/g/pretext-support/c/yTIZZ68KMoY) is that the rendering of newlines in Parsons blocks differs between HTML output and the manifest.
Here is the exercise Sean identified the problem in:
https://github.com/sean-fitzpatrick/APEXCalculusPTX/blob/f21d5dcf98a6ff0868519f25f8633ecfe7fa7291/ptx/sec_optimization.ptx#L585This block:
<block order="2">
<p>
The <em>fundamental equation</em> is <m>S= 2\pi r^2 + 2\pi r h</m>
</p>
</block>
Renders as this in the HTML:
<div class="para" id="APEX-PROTEUS-optimization-2-v1-3-2-1">The <em class="emphasis">fundamental equation</em> is <span class="process-math">\(S= 2\pi r^2 + 2\pi r h\)</span>
</div>
---
It renders as this in the manifest:
<pre class="parsonsblocks" data-question_label="" style="visibility: hidden;" data-language="natural" data-adaptive="true" data-noindent="true"><div class="para" id="APEX-PROTEUS-optimization-2-v1-3-1-1">The quantity to minimize is the total surface area of the cylinder.</div>
---
Notice where the final </div> is placed.
Various templates insert newlines in the output. It looks like when XSL produces output with method="xml", those newlines are treated differently than when using method="html".
The HTML output uses method="html", but the runestone-manifest file uses "xml".
Rob - that is the issue, but I don't know how it would best be solved. Something like this did come up before in:
https://groups.google.com/d/msgid/pretext-dev/MTAwMDAzNC5iZWV6ZXI.1695911201%40quikprotect