Also, add 'lsquo as allowed content.
Omitting the ` conversion in the first place was over-conservative.
There's a backward-compatibility issue with this addition (i.e., a
document might contain a backquote in a decoded context that is
meant to be rendered as a backquote), but the potential problems
seem minor.
original commit: cb041850f424644937c8b494c64c066bbe5f2069
has a contract (which I'm inferring from the way
it is implemented so I might be getting it wrong)
related to PR 12966
original commit: f03274c8b77d61991231f5f7931356508b07caa3
corner of the definitions window, based on the information that check
syntax computes
This commit contains two separate changes to make this work:
- adding a new renderer, based on the text renderer, that
pulls out the contents of the blue boxes and saves them
in the doc/ directories (specifically in the files named
contract-blueboxes.rktd)
- extend check syntax to use and display the information
build by the new renderer
original commit: 0c6734f782867b0401db15eb687fd246552e17b5
code that skips over them when building the search indices.
Overall, this means that the only change most people would see
is that multiple constructors in the same class will get a warning
(and there was one of those, so fixed that too).
Also, Rackety. Specifically, transformed this surprising combination
of constructs (where all caps are placeholders for something specific):
((if PRED
(λ (c mk) BODY2)
(λ (c mk) BODY1))
content
(lambda (tag) BODY3))
into this one:
(define (mk tag) BODY3)
(if PRED
BODY1{c:=content}
BODY2{c:=content})
original commit: 8ee76c9547899f62e6f28eba1cdbba1f4d54c399
Include the URL to ACM's explanation of how to use categories,
and add some other formatting guidance that is otherwise
difficult to track down.
original commit: aa5b1e192c5d38ada197a488f9817ed7ad9df861
so when it shows up in an error message it doesn't take forever to figure
out which 'val' that is
original commit: 0ee8155527bf0118c1b035efdcc5a6a2fac4828a
Fixed problems related to sorting, more than two references for
one citation, and "specific" additions like page numbers.
Also, removed a set of parentheses around disambiguated dates
in the bibliography, because I don't think they belong there.
The doc format was confused; for example, square brackets don't mean
optional in a syntactic form documentation, but instead mean square
brackets.
original commit: 71fe28e5dcf33f33a1afbb810b0cf6cc439e6629
Also add the option to `render' from `racket/render', and
document the existing `render%' initialization argument.
original commit: f9b4c6b2268440e9e74b414e6e0b1487981c70df
For example, a `tex-addition' structure can have literal bytes
to include in the generated Latex, instead of a path to a file that
holds the content.
original commit: 2b9f57b01d55a39a70f0d0df22bc97b1874727ea
This tweak avoids adding extra space when the white-label font is
taller than the line it's attached to. It also makes the label
disappear in IE 6, but I think we can live with that.
original commit: c2924ef926c3ed62e61e5deff72f15f3065bb0ab
- added some color (mostly to try to disambiguate the lines)
- several of the things named '*-element' actually belong under content, not element.
- element has 'content', not the substructs.
- convertible?s are content's.
- the 'content' field in an element is not a list, but simply a content.
- there are a bunch of things under target-element.
- image-element was missing fields
- collect-element was missing the collect field
original commit: 411aeb99b845823aa5f9bcaebe6b686ad478ab75
