Open Alex-Jordan opened 2 months ago
which seems undesirable
Debatable. ;-) Take it to pretext-dev
for any necessary discussion.
This is a conscious decision, as static formats have no notion of an introduction, then a statment, then a conclusion. They wouldn't know what to do with it. So introduction and conclusion become melded into the statement. See the otherwise
in the pretext-assembly
template starting at about line 2411.
The point is: we have to fashion something that is universally recognized by existing PreText conversions.
I think the issue is having one output format present content in one order, and a different format presents content in a different order, if the author meant for one piece of content to logically follow the other.
I'll propose a solution on -dev. Later.
On Fri, Sep 13, 2024, 5:56 PM Rob Beezer @.***> wrote:
which seems undesirable
Debatable. ;-) Take it to pretext-dev for any necessary discussion.
This is a conscious decision, as static formats have no notion of an introduction, then a statment, then a conclusion. They wouldn't know what to do with it. So introduction and conclusion become melded into the statement. See the otherwise in the pretext-assembly template starting at about line 2411.
The point is: we have to fashion something that is universally recognized by existing PreText conversions.
— Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/PreTeXtBook/pretext/issues/2255*issuecomment-2350752914__;Iw!!Ka_JY85zDv0FFw!gJaSbdO8t9xSh7GCVZByKq7QD8cDnMRiDQOUKYnNoyTKZkHX93K9MPIjPSdNUIqIYvMC4JE3lHZCOLu-YLUUIK7lKsA$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABEDOAB5NAB4C2GGKHN4LT3ZWOCUZAVCNFSM6AAAAABOEDHO5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQG42TEOJRGQ__;!!Ka_JY85zDv0FFw!gJaSbdO8t9xSh7GCVZByKq7QD8cDnMRiDQOUKYnNoyTKZkHX93K9MPIjPSdNUIqIYvMC4JE3lHZCOLu-YLUU1IRhdqg$ . You are receiving this because you authored the thread.Message ID: @.***>
Take a look at the first exercise here: https://pretextbook.org/examples/webwork/sample-chapter/sample-chapter.pdf#page=6
The "That was a simple problem. Let’s move on." is authored in a
conclusion
in source. The source is structured:Something about what happens with
webwork-reps
in-assembly
is causing theintroduction
,webwork-reps/static/statement
, andconclusion
to come out immediately one after the other. So then the hint/answer/solution comes after the conclusion, which seems undesirable. In HTML static preview, hint/answer/solution all come before the conclusion.(Can you tell I am looking closely at PDF output to get Tacoma progress posted?)