Adjustments to PGbasicmacros.pl for compatibility with MathBook XML #288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two things are done here.
One puts harmless LaTeX comments into hardcopy output for a problem that designate the beginning and ending of any solution, any hint, and the problem preamble that the beginproblem macro creates. These comments are going to be used by MathBook XML to parse a problem into chunks: preamble, statement(s), hint(s), solution(s).
The preamble is largely ignored, although PGML preamble content is put into the document preamble of MBX latex output.
Statement(s), hint(s), solution(s) are each handled separately by MBX in different ways depending on processing flags.
The other thing that is done here is that
$envir->{setNumber}) ne 'not defined'
is added to the conditions for thebeginproblem
macro to refrain from printing a header. This is the condition in play when a problem is accessed as outlined at http://michaelgage.blogspot.com/2015/06/whether-writing-full-text-book-or-just.html.