4.3.7 Links
See also Links.
An element where the
decoded
pre-content is hyperlinked to the definition
of
id.
Alias of
hyperlink for backward compatibility.
Alias of
other-doc for backward compatibility.
Produces an element for the
decoded
pre-content, and
also defines a term that can be referenced elsewhere using
tech.
The content->string result of the decoded
pre-content is used as a key for references, but normalized
as follows:
A trailing “ies” is replaced by “y”.
A trailing “s” is removed.
Consecutive hyphens and whitespaces are all replaced by a
single space.
These normalization steps help support natural-language references
that differ slightly from a defined form. For example, a definition of
“bananas” can be referenced with a use of “banana”.
If style? is true, then defterm is used on
pre-content.
Produces an element for the
decoded
pre-content, and
hyperlinks it to the definition of the key as established by
deftech. If
key is false, the decoded content is
converted to a string (using
content->string) to use as a
key; in either case, the key is normalized in the same way as for
deftech. The
#:doc and
#:tag-prefixes
arguments support cross-document and section-specific references, like
in
secref.
With the default style files, the hyperlink created by tech
is somewhat quieter than most hyperlinks: the underline in HTML output
is gray, instead of blue, and the term and underline turn blue only
when the mouse is moved over the term.
In some cases, combining both natural-language uses of a term and
proper linking can require some creativity, even with the
normalization performed on the term. For example, if “bind” is
defined, but a sentence uses the term “binding,” the latter can be
linked to the former using @tech{bind}ing.
Like
tech, but the link is not quiet. For example, in HTML
output, a hyperlink underline appears even when the mouse is not over
the link.