<\body> <\explain> <|explain> The operand must evaluate to a literal string, it is used as a target name which can be referred to by , and tags. Label names should be unique in a document and in a project. Examples in this section will make references to an example named ``there''. <\tm-fragment> > <\explain> <|explain> The operand must evaluate to a literal string, which is the name of a defined in the current document or in another document of the current project. <\tm-fragment> > The is typeset as the value of the variable at the point of the target . The variable is set by many numbered structures: sections, figures, numbered equations, etc. A reacts to mouse clicks as an hyperlink. <\explain> <|explain> The operand must evaluate to a literal string, which is the name of a defined in the current document or in another document of the current project. <\tm-fragment> > The is typeset as the number of the page containing the target . Note that page numbers are only computed when the document is typeset with page-breaking, that is not in ``automatic'' or ``papyrus'' page type. A reacts to mouse clicks as an hyperlink. <\explain> <|explain> This primitive produces an hyperlink with the visible text pointing to . The is typeset as inline . The must evaluate to a literal string in syntax and can point to local or remote documents, positions inside documents can be be specified with labels. The following examples are typeset as hyperlinks pointing to the label ``there'', respectively in the same document, in a document in the same directory, and on the web. <\tm-fragment> > > > If the document is not editable, the hyperlink is traversed by a simple click, if the document is editable, a double-click is required. <\explain> <|explain> The operand must be a literal string and is interpreted as a file name. The content of this file is typeset in place of the tag, which must be placed in . <\explain> <|explain> Bind a to a double mouse click on . For instance, when clicking , you may launch an . This action is encoded by >. When clicking on actions, the user is usually prompted for confirmation, so as to avoid security problems. The user may control the desired level of security in . Programmers may also declare certain routines to be ``secure''. programs which only use secure routines are executed without confirmation from the user.