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
