3.1 Base Document Format
Functions provided by this library, such as title and italic, might be called from Racket as
(title #:tag "how-to" "How to Design " (italic "Great") " Programs")
They can also be called with @ notation as
@title[#:tag "how-to"]{How to Design @italic{Great} Programs} |
Although the procedures are mostly design to be used from @ mode, they are easier to document in Racket mode (partly because we have scribble/manual).
3.1.1 Document Structure
procedure
(title [ #:tag tag #:tag-prefix tag-prefix #:style style #:version vers #:date date] pre-content ...+) → title-decl? tag : (or/c #f string? (listof string?)) = #f tag-prefix : (or/c #f string? module-path?) = #f style : (or/c style? #f string? symbol? (listof symbol?)) = #f vers : (or/c string? #f) = #f date : (or/c string? #f) = #f pre-content : pre-content?
The style argument can be a style structure, or it can be one of the following: a #f that corresponds to a “plain” style, a string that is used as a style name, a symbol that is used as a style property, or a list of symbols to be used as style properties. For information on styles, see part. For example, a style of 'toc causes sub-sections to be generated as separate pages in multi-page HTML output.
The tag-prefix argument is propagated to the generated structure (see Tags). If tag-prefix is a module path, it is converted to a string using module-path-prefix->string.
The vers argument is propagated to the title-decl structure. Use "" as vers to suppress version rendering in the output.
The date argument is propagated to the title-decl structure via a document-date style property. Use "" as date to suppress date rendering in Latex output.
The section title is automatically indexed by decode-part. For the index key, leading whitespace and a leading “A”, “An”, or “The” (followed by more whitespace) is removed.
procedure
(section [ #:tag tag #:tag-prefix tag-prefix #:style style] pre-content ...+) → part-start? tag : (or/c #f string? (listof string?)) = #f tag-prefix : (or/c #f string? module-path?) = #f style : (or/c style? #f string? symbol? (listof symbol?)) = #f pre-content : pre-content?
procedure
(subsection [ #:tag tag #:tag-prefix tag-prefix #:style style] pre-content ...+) → part-start? tag : (or/c #f string? (listof string?)) = #f tag-prefix : (or/c #f string? module-path?) = #f style : (or/c style? #f string? symbol? (listof symbol?)) = #f pre-content : pre-content?
procedure
(subsubsection [ #:tag tag #:tag-prefix tag-prefix #:style style] pre-content ...+) → part-start? tag : (or/c #f string? (listof string?)) = #f tag-prefix : (or/c #f string? module-path?) = #f style : (or/c style? #f string? symbol? (listof symbol?)) = #f pre-content : pre-content?
procedure
(subsubsub*section [ #:tag tag #:tag-prefix tag-prefix #:style style] pre-content ...+) → paragraph? tag : (or/c #f string? (listof string?)) = #f tag-prefix : (or/c #f string? module-path?) = #f style : (or/c style? #f string? symbol? (listof symbol?)) = #f pre-content : pre-content?
syntax
(include-section module-path)
procedure
(author+email author-name [ #:obfuscate? obfuscate?]) → element? author-name : elem email : string? obfuscate? : any/c = #f
Note that author+email is not a replacement for author. The author+email function is often used in combination with author.
3.1.2 Blocks
procedure
(para [#:style style] pre-content ...) → paragraph?
style : (or/c style? string? symbol? #f) = #f pre-content : pre-content?
The style argument can be a style, #f to indicate a “plain” style, a string that is used as a style name, or a symbol that is used as a style name. (Note that section and para treat symbols differently as style arguments.)
procedure
(nested [#:style style] pre-flow ...) → nested-flow?
style : (or/c style? string? symbol? #f) = #f pre-flow : pre-flow?
The style argument is handled the same as para. The 'inset and 'code-inset styles cause the nested flow to be inset compared to surrounding text, with the latter particularly intended for insetting code.
procedure
(centered pre-flow ...) → nested-flow?
pre-flow : pre-flow?
procedure
(margin-note pre-flow ... [#:left? left?]) → block?
pre-flow : pre-flow? left? : any/c = #f
If left? is true, then the note is shown on the opposite as it would normally be shown (which is the left-hand side for HTML output). Beware of colliding with output for a table of contents.
procedure
(margin-note* pre-content ... [#:left? left?]) → element?
pre-content : pre-content? left? : any/c = #f
procedure
(itemlist itm ... [#:style style]) → itemization?
itm : items/c style : (or/c style? string? symbol? #f) = #f
The style argument is handled the same as para. The 'ordered style numbers items, instead of just using a bullet.
value
procedure
cells : (listof (listof (or/c block? content? 'cont))) style : (or/c style? string? symbol? #f) = #f sep : (or/c block? content? #f) = #f
If sep is not #f, it is inserted between every column in the table. Otherwise, the default style places no space between table columns.
Use 'cont as a cell to continue the content of the preceding cell in a row in the space that would otherwise be used for a new cell. A 'cont must not appear as the first cell in a row.
The style argument is handled the same as para.
@tabular[#:sep @hspace[1] (list (list "soup" "gazpacho") (list "soup" "tonjiru"))] @tabular[#:style 'boxed (list (list @bold{recipe} @bold{vegetable}) (list "caldo verde" "kale") (list "kinpira gobō" "burdock") (list "makizushi" 'cont))]
procedure
indent : exact-nonnegative-integer? = 0 str : string?
The strs are not decoded with decode-content, so (verbatim "---") renders with three hyphens instead of an em dash. Beware, however, that reading @verbatim converts @ syntax within the argument, and such reading occurs well before arguments to verbatim are delivered at run-time. To disable simple @ notation within the verbatim argument, verbatim is typically used with |{...}| or similar brackets, like this:
@verbatim|{ |
Use @bold{---} like this... |
}| |
which renders as
Use @bold{---} like this... |
Even with |{...}|, beware that consistent leading whitespace is removed by the parser; see Alternative Body Syntax for more information.
See also literal.
3.1.3 Text Styles and Content
procedure
pre-content : pre-content? style : (or style? string? symbol? #f) = #f
procedure
pre-content : pre-content?
procedure
pre-content : pre-content?
procedure
pre-content : pre-content?
procedure
pre-content : pre-content?
procedure
(superscript pre-content ...) → element?
pre-content : pre-content?
procedure
pre-content : pre-content?
procedure
pre-content : pre-content?
procedure
pre-content : pre-content?
Beware that @ for a literal call performs some processing before delivering arguments to literal. The literal form can be used with |{...}| or similar brackets to disable @ notation within the literal argument, like this:
@literal|{@bold{---}}| |
which renders as
@literal|{@bold{---}}| |
See also verbatim.
procedure
(image path [ #:scale scale #:suffixes suffixes] pre-content ...) → element? path : (or/c path-string? (cons/c 'collects (listof bytes?))) scale : real? = 1.0 suffixes : (listof #rx"^[.]") = null pre-content : pre-content?
The path is relative to the current directory, which is set by setup-plt and scribble to the directory of the main document file. The path argument also can be a result of path->main-collects-relative.
The strings in suffixes are filtered to those supported by given renderer, and then the acceptable suffixes are tried in order. The HTML renderer supports ".png", ".gif", and ".svg", while the Latex renderer supports ".png", ".pdf", and ".ps" (but ".ps" works only when converting Latex output to DVI, and ".png" and ".pdf" work only for converting Latex output to PDF).
Note that when the suffixes library is non-empty, then the path argument should not have a suffix.
3.1.4 Spacing
procedure
(nonbreaking pre-content ...) → element?
pre-content : pre-content?
procedure
n : exact-nonnegative-integer?
See .__ for an example.
The following example illustrates both ._ and .__:
#lang scribble/base My name is Mr@._ T@.__ I pity the fool who can't typeset punctuation.
3.1.5 Links
procedure
(hyperlink url pre-content ... [ #:underline? underline? #:style style]) → element? url : string? pre-content : pre-content? underline? : any/c = #t
style : (or/c style? string? symbol? #f) = (if underline? #f "plainlink")
procedure
(secref tag [ #:doc module-path #:tag-prefixes prefixes #:underline? underline?]) → element? tag : string? module-path : (or/c module-path? #f) = #f prefixes : (or/c (listof string?) #f) = #f underline? : any/c = #t
If #:doc module-path is provided, the tag refers to a tag with a prefix determined by module-path. When setup-plt renders documentation, it automatically adds a tag prefix to the document based on the source module. Thus, for example, to refer to a section of the Racket reference, module-path would be '(lib "scribblings/reference/reference.scrbl").
The #:tag-prefixes prefixes argument similarly supports selecting a particular section as determined by a path of tag prefixes. When a #:doc argument is provided, then prefixes should trace a path of tag-prefixed subsections to reach the tag section. When #:doc is not provided, the prefixes path is relative to any enclosing section (i.e., the youngest ancestor that produces a match).
For HTML output, the generated reference is the hyperlinked title of the elements in the section’s title content, except that elements with the 'aux style property are omitted in the hyperlink label. If underline? is #f, then the hyperlink is rendered in HTML without an underline.
For Latex output, the generated reference’s format depends on the document style. By default, only the section number is shown in the reference, but the scribble/manual style shows the title after the section number. Customize the output (see Extending and Configuring Scribble Output) by redefining the \BookRef, etc., macros (see Predefined Latex Macros).
procedure
(Secref tag [ #:doc module-path #:tag-prefixes prefixes #:underline? underline?]) → element? tag : string? module-path : (or/c module-path? #f) = #f prefixes : (or/c (listof string?) #f) = #f underline? : any/c = #t
procedure
(seclink tag [ #:doc module-path #:tag-prefixes prefixes #:underline? underline?] pre-content ...) → element? tag : string? module-path : (or/c module-path? #f) = #f prefixes : (or/c (listof string?) #f) = #f underline? : any/c = #t pre-content : pre-content?
procedure
(other-doc module-path [ #:underline? underline?]) → element? module-path : module-path? underline? : any/c = #t
procedure
(elemref t pre-content ... [ #:underline? underline?]) → element? t : (or/c tag? string?) pre-content : pre-content? underline? : any/c = #t
3.1.6 Indexing
procedure
(index words pre-content ...) → index-element?
words : (or/c string? (listof string?)) pre-content : pre-content?
Use index when an index entry should point to a specific word or phrase within the typeset document (i.e., the pre-content). Use section-index, instead, to create an index entry that leads to a section, instead of a specific word or phrase within the section.
procedure
(index* words word-contents pre-content ...) → index-element?
words : (listof string?) word-contents : (listof list?) pre-content : pre-content?
procedure
(as-index pre-content ...) → index-element?
pre-content : pre-content?
procedure
(section-index word ...) → part-index-decl?
word : string?
procedure
(index-section [#:tag tag]) → part?
tag : (or/c #f string?) = "doc-index"
3.1.7 Tables of Contents
procedure
procedure
(local-table-of-contents [#:style style]) → delayed-block?
style : (or/c symbol? #f) = #f
The meaning of the style argument depends on the output type, but 'immediate-only normally creates a table of contents that contains only immediate sub-sections of the enclosing section. See also the 'quiet style of part (i.e., in a part structure, not supplied as the style argument to local-table-of-contents), which normally suppresses sub-part entries in a table of contents.
3.1.8 Tags
The exports of scribble/tag are all re-exported by scribble/base.