Specifying `#:link-target? #f' gets blue-box typesetting without
declaring documentaton for a binding.
original commit: 5c4a7db828b1e1d7d43047b6ba32b8a00297df44
This commit extends make-base-eval, make-base-eval-factory, and
make-eval-factory with an #:eval and input-program inputs so that
these functions are more like racket/sandbox make-evaluator.
original commit: 213430f728b33486fcc8334058a833f9d8c9de78
These result from something like
@racket[(x y)]
being treated by Scribble as multiple RktXXX items rather than one. As
a result the Markdown emitted was:
`(``x`` ``y``)`
But obviously instead we want:
`(x y)`
Kludgosity alert: Although it would probably be more-correct to
consolidate the RktXXX items at the Scribble structure level, I don't
easily see how. `@racket` is baking in the concept of Racket
lexing (classifying text as various kinds of Racket elements). This is
handy when the render will be HTML or Latek, and is benignly N/A when
it will be plain text. But it's a bit square-peg/round-hole when the
render will be Markdown. Rather than attempt to "un-lex" the Scribble
structures (I'm having trouble seeing how), I'm handling it
"after-the-fact" -- adjusting the generated Markdown text.
If anyone thinks the preceding is an elaborate rationalization for an
ugly kludge, I wouldn't argue, but I would need some help
understanding the preferable way to go about it.
original commit: 59bba2d197a42448d21c7f899d197b890adc7c9e
Unlike plain `racketblock`, `examples` and `interaction` are
"nested". As a result we emitted bad Markdown like:
```racket
Examples:
```racket
some-code
```
```
Markdown code blocks can't nest, so this needs to be:
```racket
Examples:
some-code
```
Also: Updated the unit test with examples of `examples` and
`interaction`.
original commit: a5f6686270239484a5e7b2e6864c9bd5627d937d
Use this open in the HtDP language documentation in the same
way as for `defproc', which fixes the docs for `pi', `e', etc.
original commit: 8d03995b628771e529aa56403dbdd29a8e0926d5
Also defines the "@-form" term in the @-syntax section due to its
frequency.
Closes PR-12589.
original commit: 61db1d64058214426343bb50d0dfa5c5300a0d29
Based on David Van Horn's suggestion.
Also, make both `author' and `authorinfo' work (even when mixed).
original commit: c9c4d33a2f93cac296c43d0ba04663a870d31664
A recent change improved "on this page" handling and also
fixed a short-circuit test to almost certainly do what
was originally intended, but the test was wrong, so just
get rid of it.
original commit: 2d5884b26a8aa96cab469b31c8b4d16190f854a9
Related to PR 13305: I tried to use zero-width-space to force appropriate
line breaks, but unfortunately under Opera on Linux, this shows as
unsupported character glyphs.
Since I can't reliably use zero-width-space, I'm backtracking to the
prior solution on introducing spans with the mywbr class. However,
I've added in a   element to the content of the span, as suggested
elsewhere on the web. This appears to fix the _gcpointer issue that
Eric sees.
original commit: 7323dde0eabf54dafb85d0e882ccefbf33e5535f
A part with style property 'toc-hidden no longer
hides child sections, which makes it consistent with Latex/PDF
rendering.
A part with style 'grouper and 'unnumbered does not make its
child parts render as more nested, which is consistent with
'gruper without 'unnumbered. An unnumbered grouper is represented
as "" in a section-number list (while #f is still used for
unnumbered non-grouper layers).
original commit: 23d0627acc36998dc76ebd840276c80f47cab459
The zero width space is a more robust way to add place to line-wrap,
according to: http://www.quirksmode.org/oddsandends/wbr.html
Closes PR 13305.
original commit: 29031f0972ead0d3cd26d61f163b5e5b59e9ffce
These languages set the default class for Latex rendering, and also
adjust Latex commands so that top-level sections are chapters, etc.
original commit: 09d4aa3d79066e73e93727fd18a5805873e63acf
