<\body> <\explain> >> >> <|explain> These primitives are used for producing large delimiters, like in the formula <\equation*> >>\>. Matching left and right delimiters are automatically sized so as contain the enclosed expression. Between matching left and right delimiters, the formula may contain an arbitrary number of middle delimiters, which are sized in a similar way. Contrary to , the depth of a large delimiter is not necessarily equal to its height, so as to correctly render formulas like <\equation*> f>> The user may override the automatically determined size by specifying additional length parameters or and . For instance, <\tm-fragment> xy> is rendered as <\equation*> fxy The may also be a number , in which case the -th available size for the delimiter is taken. For instance, <\tm-fragment> z> is rendered as <\equation*> gz \; <\explain> <|explain> This primitive is used in order to produce big operators as in <\equation> >a*z The size of the operator depends on whether the formula is rendered in ``display style'' or not. Formulas in separate equations, like (), are said to be rendered in display style, contrary to formulas which occur in the main text, like >a*z>. The user may use to override the current settings. Notice that the formula () is internally represented as <\tm-fragment> >a*z> The invisible big operator > is used to indicate the end of the scope of >. <\explain> <|explain> The primitive is used in order to render fractions like >. In display style, the numerator and denominator are rendered in the normal size, but display style is turned of when typesetting and . When the display style is turned of, then the arguments are rendered in script size. For instance, the content <\tm-fragment> +++\>>>> is rendered in display style as <\equation*> +++\>>> <\explain> <|explain> The primitive is used in order to render square roots like > or -th roots like >. The root symbol is automatically sized so as to encapsulate the : <\equation*> +z>|i+j> <\explain> <|explain> These primitives are used in order to attach a to the preceeding box in a horizontal concatenation (in the case of right scripts) or the next one (in the case of left scripts). When there is no such box, then the script is attached to an empty box. Moreover, when both a subscript and a superscript are specified on the same side, then they are merged together. For instance, the expression <\tm-fragment> +x=y+> is rendered as <\equation*> +x=y+ When a right script is attached to an operator (or symbol) which accepts limits, then it is rendered below or above instead of beside the operator: <\equation*> lim\>a Scripts are rendered in a smaller font in non-display style. Nevertheless, in order to keep formulas readable, the size is not reduced below script-script-size. <\explain> <|explain> Left and right primes are similar to left and right superscripts, except that they behave in a different way when being edited. For instance, when your cursor is behind the prime symbol in > and you press backspace, then the prime is removed. If you are behind > and you press backspace several times, then you first enter the superscript, next remove and finally remove the superscript. Notice also that is necessarily a string of concatenated prime symbols. For instance, >> is represented by >>. <\explain> <|explain> The and tags are used to explicitly attach a below or above a given . Both can be mixed in order to produce content with both a script below and above: <\equation*> |\> x can be produced using <\tm-fragment> |\> x> <\explain> <|explain> These primitives can be used in order to produce wide accents above or below some mathematical . For instance >> corresponds to the markup >>. <\explain> <|explain> This primitive is mainly used for producing negated symbols or expressions, such as >> or >. <\explain> >|child-n> <|explain> This primitive is used to produce a tree with a given and children until . The primitive should be used recursively in order to produce trees. For instance, <\equation*> |2|y|z>> corresponds to the markup <\tm-fragment> |2|y|z>>> In the future, we plan to provide further style parameters in order to control the rendering.