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
For example, a syntactic form box is labeled with "SYNTAX". Forms
such as `defform' and `defthing' now support a `#:kind' option
for setting the label.
original commit: 5ff3087677ec98ea626cca25b085f3c32138d5ca
The `wrap-line' function from `scribble/text/wrap' wants a
string that's a single line, so break the initial string
based on explicit lines, first.
original commit: 9b7ef7bf699c7997ad2c254827ca6528491a6f10
Use the new `relative-in' form to make imports
resolve correctly when they are shifted among modules.
original commit: 0c95475f4ffbc343291e5529a6f4b32a91159ef1
Also add a `for-doc' require form, make `proc-doc' et al. provide
forms, make `provide/doc' an alias for `provide'.
original commit: 964020f288a73340052b471327bfe873d804eea8
Looks like it's not making any changes in the current tests (which use
the text renderer), but with words that are longer than the width the
old version would stop wrapping afetr these words. Added a test file
that fails with that and succeeds with the new one. If anyone cares
about this, it's easy to make hyphenate words that are too long for a
line.
(Also fixed some redundant frustration in the bib test...)
original commit: 084f1dcea7707adc83d180f79e6c68149dc03644
This might have output that is a little better in cases where the
wrapped string is longer than `maxlen', for example, with an input of:
" x xxxxxxxxxxxxxxxx..."
and wrapping at 10 characters, the output was
" x\nxxxxxxxxxx\nxxxxxx..."
and now it's
" x xxxx\nxxxxxxxxxx\nxx..."
original commit: efda1706d87045cbe2882c9c4b77b34a72e3594b
This should probably become documented if it's stable enough. For now
it's intended for building wrapping functions, so it's only documented
in comments the file.
original commit: 89b9ad0dde5298516934f4df016c27b60e10f86d
Generate wrappers consistent with a reader-level absence of `.'s,
instead of wrapping every pair. This change fixes the `syntax-e'
example in the Guide's description of syntax objects.
original commit: 54a6ba8d363f441d0bf3d4b15df0170215b84b8e
Use `datum->syntax' instead of `begin' to protect the string or byte
string. Danny Yoo suggested this change.
original commit: 23296615ec7cddb34257486b62094048b085ff6e
Otherwise, the width of a pict is implicitly rounded up, since
the PDF bounding box is an integer.
original commit: 4735666cd9a3a5de4e40202b23a9d8da034ef22e
There's no particular reason that any one format will have all
the information that other formats need, but it conveniently works
for now that HTML info can subsume Latex info.
original commit: a1fd742ed022035732b4a0c778168cc6b862933a
This turned out to be a bad idea. The thing is that some resources need
to be referred to in multiple ways -- for example, different texts in
links of different kinds, or using the URL directly in some cases. The
existence of `get-resource-path' is a witness for this problem, since it
was used for such cases -- this function is removed as well.
There's no point in trying to generalize this here: instead, go back to
a simpler system where a resource always returns its URL (with an
optional argument to get an absolute URL). When a `referrer'
functionality is needed, build it on top of that, in a place where it
makes more sense. (That is, in a specific code for generating content,
where there could be a decision that resources have plain links and also
a very short link for use in navbars.) Otherwise, it's usually simpler
to just define resources and referrers separately (as different
bindings, the latter uses the former).
original commit: 180651d04d554bb29a6128dd66a292d354140535
Rename `read-intern-literal' to `datum-intern-literal'.
Interning is needed only in `read-syntax' or `datum->syntax' to
set up the invariants that the bytecode compiler needs for cross-module
optimization. When `read'ing numbers from a data file, meanwhile,
interning slows things down a lot and doesn't seem worthwhile.
original commit: ee775c3cc3088a8de848399b3c1eec97bbc52b89
The value isn't used; a 'dep tag is ony to establish
dependencies, and the relevant value is with a 'form or
'def tag. Avoiding the extra value saves another 5% in
cross-reference files.
original commit: 28ee1570ae2ac68007af5798b5964a859ffcb49b
This change saves a small amount of space in cross-reference files
and some space in loaded cross-reference information.
It also saves work converting strings to mutable on deserialize,
although the performance difference seems negligible.
original commit: b2fade9206590173e4c2e346357ad13150525387
In @defform*[#:id x1 [(qqq x1)]], for example, `#:id x1' needs to
calcel the default treatment of `x1' within `(qqq x1)' as
a metavariable, while treating `qqq' as a meta-variable.
original commit: 7d2914fc8a8f2647605da1d6699d0bc54685a5f3
The renderer was using symbol style names as command names, but only
strings should be treated that way.
original commit: 0f5b53d3498f857920ff7fa438269727553dc058
instead of copying the file into place. This makes Lion's Preview happier (specifically
it now recognizes the file as a revision of the old one and updates itself instead of
treating it as a new file and opening a second window)
original commit: f9e1c41cb0a7f84766207d7a092443dbb5a17e1c
Related to the already fixed PR 12114 and PR 12133, which motivated the
error, and a few additional typos of the same kind.
(Note that it uses the symbols, but that's how they'll render anyway.)
original commit: 16cd1ad78d6495816a4869621154024652fd8da0
