diff options
Diffstat (limited to 'doc/context/sources/general/manuals/luametatex/luametatex-math.tex')
| -rw-r--r-- | doc/context/sources/general/manuals/luametatex/luametatex-math.tex | 454 |
1 files changed, 227 insertions, 227 deletions
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-math.tex b/doc/context/sources/general/manuals/luametatex/luametatex-math.tex index 44d7dbe19..da05485ad 100644 --- a/doc/context/sources/general/manuals/luametatex/luametatex-math.tex +++ b/doc/context/sources/general/manuals/luametatex/luametatex-math.tex @@ -68,7 +68,7 @@ The unaltered ones are: \stoptabulate For practical reasons \prm {mathchardef} will silently accept values larger -that \type {0x8000} and interpret it as \lpr {Umathcharnumdef}. This is needed +that \type {0x8000} and interpret it as \prm {Umathcharnumdef}. This is needed to satisfy older macro packages. The following new primitives are compatible with \XETEX: @@ -78,17 +78,17 @@ The following new primitives are compatible with \XETEX: \starttabulate[|l|l|r|c|l|r|] \DB primitive \BC min \BC max \BC \kern 2em \BC min \BC max \NC \NR \TB -\NC \lpr {Umathchardef} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR -\NC \lpr {Umathcharnumdef}\rlap{\high{5}} \NC -80000000 \NC 7FFFFFFF \NC \NC \NC \NC \NR -\NC \lpr {Umathcode} \NC 0 \NC 10FFFF \NC = \NC 0+0+0 \NC 7+FF+10FFFF \NC \NR -\NC \lpr {Udelcode} \NC 0 \NC 10FFFF \NC = \NC 0+0 \NC FF+10FFFF \NC \NR -\NC \lpr {Umathchar} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR -\NC \lpr {Umathaccent} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR -\NC \lpr {Udelimiter} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR -\NC \lpr {Uradical} \NC 0+0 \NC FF+10FFFF \NC \NC \NC \NC \NR -\NC \lpr {Umathcharnum} \NC -80000000 \NC 7FFFFFFF \NC \NC \NC \NC \NR -\NC \lpr {Umathcodenum} \NC 0 \NC 10FFFF \NC = \NC -80000000 \NC 7FFFFFFF \NC \NR -\NC \lpr {Udelcodenum} \NC 0 \NC 10FFFF \NC = \NC -80000000 \NC 7FFFFFFF \NC \NR +\NC \prm {Umathchardef} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR +\NC \prm {Umathcharnumdef}\rlap{\high{5}} \NC -80000000 \NC 7FFFFFFF \NC \NC \NC \NC \NR +\NC \prm {Umathcode} \NC 0 \NC 10FFFF \NC = \NC 0+0+0 \NC 7+FF+10FFFF \NC \NR +\NC \prm {Udelcode} \NC 0 \NC 10FFFF \NC = \NC 0+0 \NC FF+10FFFF \NC \NR +\NC \prm {Umathchar} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR +\NC \prm {Umathaccent} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR +\NC \prm {Udelimiter} \NC 0+0+0 \NC 7+FF+10FFFF \NC \NC \NC \NC \NR +\NC \prm {Uradical} \NC 0+0 \NC FF+10FFFF \NC \NC \NC \NC \NR +\NC \prm {Umathcharnum} \NC -80000000 \NC 7FFFFFFF \NC \NC \NC \NC \NR +\NC \prm {Umathcodenum} \NC 0 \NC 10FFFF \NC = \NC -80000000 \NC 7FFFFFFF \NC \NR +\NC \prm {Udelcodenum} \NC 0 \NC 10FFFF \NC = \NC -80000000 \NC 7FFFFFFF \NC \NR \LL \stoptabulate @@ -101,20 +101,20 @@ Specifications typically look like: The new primitives that deal with delimiter|-|style objects do not set up a \quote {large family}. Selecting a suitable size for display purposes is expected -to be dealt with by the font via the \lpr {Umathoperatorsize} parameter. +to be dealt with by the font via the \prm {Umathoperatorsize} parameter. For some of these primitives, all information is packed into a single signed -integer. For the first two (\lpr {Umathcharnum} and \lpr {Umathcodenum}), the +integer. For the first two (\prm {Umathcharnum} and \prm {Umathcodenum}), the lowest 21 bits are the character code, the 3 bits above that represent the math class, and the family data is kept in the topmost bits. This means that the values -for math families 128--255 are actually negative. For \lpr {Udelcodenum} there +for math families 128--255 are actually negative. For \prm {Udelcodenum} there is no math class. The math family information is stored in the bits directly on top of the character code. Using these three commands is not as natural as using the two- and three|-|value commands, so unless you know exactly what you are doing and absolutely require the speedup resulting from the faster input scanning, it is better to use the verbose commands instead. -The \lpr {Umathaccent} command accepts optional keywords to control various +The \prm {Umathaccent} command accepts optional keywords to control various details regarding math accents. See \in {section} [mathacc] below for details. There are more new primitives and all of these will be explained in following @@ -123,11 +123,11 @@ sections: \starttabulate[|l|l|] \DB primitive \BC value range (in hex) \NC \NR \TB -\NC \lpr {Uroot} \NC 0 + 0--FF + 10FFFF \NC \NR -\NC \lpr {Uoverdelimiter} \NC 0 + 0--FF + 10FFFF \NC \NR -\NC \lpr {Uunderdelimiter} \NC 0 + 0--FF + 10FFFF \NC \NR -\NC \lpr {Udelimiterover} \NC 0 + 0--FF + 10FFFF \NC \NR -\NC \lpr {Udelimiterunder} \NC 0 + 0--FF + 10FFFF \NC \NR +\NC \prm {Uroot} \NC 0 + 0--FF + 10FFFF \NC \NR +\NC \prm {Uoverdelimiter} \NC 0 + 0--FF + 10FFFF \NC \NR +\NC \prm {Uunderdelimiter} \NC 0 + 0--FF + 10FFFF \NC \NR +\NC \prm {Udelimiterover} \NC 0 + 0--FF + 10FFFF \NC \NR +\NC \prm {Udelimiterunder} \NC 0 + 0--FF + 10FFFF \NC \NR \LL \stoptabulate @@ -135,13 +135,13 @@ sections: \startsection[title={Math styles}] -\subsection{\lpr {mathstyle}} +\subsection{\prm {mathstyle}} \topicindex {math+styles} It is possible to discover the math style that will be used for a formula in an expandable fashion (while the math list is still being read). To make this -possible, \LUATEX\ adds the new primitive: \lpr {mathstyle}. This is a \quote +possible, \LUATEX\ adds the new primitive: \prm {mathstyle}. This is a \quote {convert command} like e.g. \prm {romannumeral}: its value can only be read, not set. Beware that contrary to \LUATEX\ this is now a proper number so you need to use \type {\number} o r\type {\the} in order to serialize it. @@ -171,7 +171,7 @@ preceding use of that family). The style switching primitives like \prm {textstyle} are turned into nodes so the styles set there are frozen. The \prm {mathchoice} primitive results in four lists being constructed of which one is used in the second pass. The fact that -some automatic styles are not yet known also means that the \lpr {mathstyle} +some automatic styles are not yet known also means that the \prm {mathstyle} primitive expands to the current style which can of course be different from the one really used. It's a snapshot of the first pass state. As a consequence in the following example you get a style number (first pass) typeset that can actually @@ -244,27 +244,27 @@ Using \prm {begingroup} \unknown\ \prm {endgroup} instead gives: \blank $\displaystyle \getbuffer[2]$ \blank \blank $\textstyle \getbuffer[2]$ \blank -This might look wrong but it's just a side effect of \lpr {mathstyle} expanding +This might look wrong but it's just a side effect of \prm {mathstyle} expanding to the current (first pass) style and the number being injected in the list that gets converted in the second pass. It all makes sense and it illustrates the importance of grouping. In fact, the math choice style being effective afterwards has advantages. It would be hard to get it otherwise. -\subsection{\lpr {Ustack}} +\subsection{\prm {Ustack}} \topicindex {math+stacks} There are a few math commands in \TEX\ where the style that will be used is not known straight from the start. These commands (\prm {over}, \prm {atop}, \prm {overwithdelims}, \prm {atopwithdelims}) would therefore normally return -wrong values for \lpr {mathstyle}. To fix this, \LUATEX\ introduces a special -prefix command: \lpr {Ustack}: +wrong values for \prm {mathstyle}. To fix this, \LUATEX\ introduces a special +prefix command: \prm {Ustack}: \starttyping $\Ustack {a \over b}$ \stoptyping -The \lpr {Ustack} command will scan the next brace and start a new math group +The \prm {Ustack} command will scan the next brace and start a new math group with the correct (numerator) math style. \subsection{The new \type {\cramped...style} commands} @@ -312,7 +312,7 @@ are described as follows: In \LUATEX\ one can set the styles in more detail which means that you sometimes have to set both normal and cramped styles to get the effect you want. (Even) if -we force styles in the script using \prm {scriptstyle} and \lpr +we force styles in the script using \prm {scriptstyle} and \prm {crampedscriptstyle} we get this: \startbuffer[demo] @@ -360,7 +360,7 @@ Now we get: \startsection[title={Math parameter settings}] -\subsection {Many new \lpr {Umath*} primitives} +\subsection {Many new \tex {Umath*} primitives} \topicindex {math+parameters} @@ -371,62 +371,62 @@ has resulted in turning some hard codes properties into parameters. \starttabulate \DB primitive name \BC description \NC \NR \TB -\NC \lpr {Umathquad} \NC the width of 18 mu's \NC \NR -\NC \lpr {Umathaxis} \NC height of the vertical center axis of +\NC \prm {Umathquad} \NC the width of 18 mu's \NC \NR +\NC \prm {Umathaxis} \NC height of the vertical center axis of the math formula above the baseline \NC \NR -\NC \lpr {Umathoperatorsize} \NC minimum size of large operators in display mode \NC \NR -\NC \lpr {Umathoverbarkern} \NC vertical clearance above the rule \NC \NR -\NC \lpr {Umathoverbarrule} \NC the width of the rule \NC \NR -\NC \lpr {Umathoverbarvgap} \NC vertical clearance below the rule \NC \NR -\NC \lpr {Umathunderbarkern} \NC vertical clearance below the rule \NC \NR -\NC \lpr {Umathunderbarrule} \NC the width of the rule \NC \NR -\NC \lpr {Umathunderbarvgap} \NC vertical clearance above the rule \NC \NR -\NC \lpr {Umathradicalkern} \NC vertical clearance above the rule \NC \NR -\NC \lpr {Umathradicalrule} \NC the width of the rule \NC \NR -\NC \lpr {Umathradicalvgap} \NC vertical clearance below the rule \NC \NR -\NC \lpr {Umathradicaldegreebefore}\NC the forward kern that takes place before placement of +\NC \prm {Umathoperatorsize} \NC minimum size of large operators in display mode \NC \NR +\NC \prm {Umathoverbarkern} \NC vertical clearance above the rule \NC \NR +\NC \prm {Umathoverbarrule} \NC the width of the rule \NC \NR +\NC \prm {Umathoverbarvgap} \NC vertical clearance below the rule \NC \NR +\NC \prm {Umathunderbarkern} \NC vertical clearance below the rule \NC \NR +\NC \prm {Umathunderbarrule} \NC the width of the rule \NC \NR +\NC \prm {Umathunderbarvgap} \NC vertical clearance above the rule \NC \NR +\NC \prm {Umathradicalkern} \NC vertical clearance above the rule \NC \NR +\NC \prm {Umathradicalrule} \NC the width of the rule \NC \NR +\NC \prm {Umathradicalvgap} \NC vertical clearance below the rule \NC \NR +\NC \prm {Umathradicaldegreebefore}\NC the forward kern that takes place before placement of the radical degree \NC \NR -\NC \lpr {Umathradicaldegreeafter} \NC the backward kern that takes place after placement of +\NC \prm {Umathradicaldegreeafter} \NC the backward kern that takes place after placement of the radical degree \NC \NR -\NC \lpr {Umathradicaldegreeraise} \NC this is the percentage of the total height and depth of +\NC \prm {Umathradicaldegreeraise} \NC this is the percentage of the total height and depth of the radical sign that the degree is raised by; it is expressed in \type {percents}, so 60\% is expressed as the integer $60$ \NC \NR -\NC \lpr {Umathstackvgap} \NC vertical clearance between the two +\NC \prm {Umathstackvgap} \NC vertical clearance between the two elements in an \prm {atop} stack \NC \NR -\NC \lpr {Umathstacknumup} \NC numerator shift upward in \prm {atop} stack \NC \NR -\NC \lpr {Umathstackdenomdown} \NC denominator shift downward in \prm {atop} stack \NC \NR -\NC \lpr {Umathfractionrule} \NC the width of the rule in a \prm {over} \NC \NR -\NC \lpr {Umathfractionnumvgap} \NC vertical clearance between the numerator and the rule \NC \NR -\NC \lpr {Umathfractionnumup} \NC numerator shift upward in \prm {over} \NC \NR -\NC \lpr {Umathfractiondenomvgap} \NC vertical clearance between the denominator and the rule \NC \NR -\NC \lpr {Umathfractiondenomdown} \NC denominator shift downward in \prm {over} \NC \NR -\NC \lpr {Umathfractiondelsize} \NC minimum delimiter size for \type {\...withdelims} \NC \NR -\NC \lpr {Umathlimitabovevgap} \NC vertical clearance for limits above operators \NC \NR -\NC \lpr {Umathlimitabovebgap} \NC vertical baseline clearance for limits above operators \NC \NR -\NC \lpr {Umathlimitabovekern} \NC space reserved at the top of the limit \NC \NR -\NC \lpr {Umathlimitbelowvgap} \NC vertical clearance for limits below operators \NC \NR -\NC \lpr {Umathlimitbelowbgap} \NC vertical baseline clearance for limits below operators \NC \NR -\NC \lpr {Umathlimitbelowkern} \NC space reserved at the bottom of the limit \NC \NR -\NC \lpr {Umathoverdelimitervgap} \NC vertical clearance for limits above delimiters \NC \NR -\NC \lpr {Umathoverdelimiterbgap} \NC vertical baseline clearance for limits above delimiters \NC \NR -\NC \lpr {Umathunderdelimitervgap} \NC vertical clearance for limits below delimiters \NC \NR -\NC \lpr {Umathunderdelimiterbgap} \NC vertical baseline clearance for limits below delimiters \NC \NR -\NC \lpr {Umathsubshiftdrop} \NC subscript drop for boxes and subformulas \NC \NR -\NC \lpr {Umathsubshiftdown} \NC subscript drop for characters \NC \NR -\NC \lpr {Umathsupshiftdrop} \NC superscript drop (raise, actually) for boxes and subformulas \NC \NR -\NC \lpr {Umathsupshiftup} \NC superscript raise for characters \NC \NR -\NC \lpr {Umathsubsupshiftdown} \NC subscript drop in the presence of a superscript \NC \NR -\NC \lpr {Umathsubtopmax} \NC the top of standalone subscripts cannot be higher than this +\NC \prm {Umathstacknumup} \NC numerator shift upward in \prm {atop} stack \NC \NR +\NC \prm {Umathstackdenomdown} \NC denominator shift downward in \prm {atop} stack \NC \NR +\NC \prm {Umathfractionrule} \NC the width of the rule in a \prm {over} \NC \NR +\NC \prm {Umathfractionnumvgap} \NC vertical clearance between the numerator and the rule \NC \NR +\NC \prm {Umathfractionnumup} \NC numerator shift upward in \prm {over} \NC \NR +\NC \prm {Umathfractiondenomvgap} \NC vertical clearance between the denominator and the rule \NC \NR +\NC \prm {Umathfractiondenomdown} \NC denominator shift downward in \prm {over} \NC \NR +\NC \prm {Umathfractiondelsize} \NC minimum delimiter size for \type {\...withdelims} \NC \NR +\NC \prm {Umathlimitabovevgap} \NC vertical clearance for limits above operators \NC \NR +\NC \prm {Umathlimitabovebgap} \NC vertical baseline clearance for limits above operators \NC \NR +\NC \prm {Umathlimitabovekern} \NC space reserved at the top of the limit \NC \NR +\NC \prm {Umathlimitbelowvgap} \NC vertical clearance for limits below operators \NC \NR +\NC \prm {Umathlimitbelowbgap} \NC vertical baseline clearance for limits below operators \NC \NR +\NC \prm {Umathlimitbelowkern} \NC space reserved at the bottom of the limit \NC \NR +\NC \prm {Umathoverdelimitervgap} \NC vertical clearance for limits above delimiters \NC \NR +\NC \prm {Umathoverdelimiterbgap} \NC vertical baseline clearance for limits above delimiters \NC \NR +\NC \prm {Umathunderdelimitervgap} \NC vertical clearance for limits below delimiters \NC \NR +\NC \prm {Umathunderdelimiterbgap} \NC vertical baseline clearance for limits below delimiters \NC \NR +\NC \prm {Umathsubshiftdrop} \NC subscript drop for boxes and subformulas \NC \NR +\NC \prm {Umathsubshiftdown} \NC subscript drop for characters \NC \NR +\NC \prm {Umathsupshiftdrop} \NC superscript drop (raise, actually) for boxes and subformulas \NC \NR +\NC \prm {Umathsupshiftup} \NC superscript raise for characters \NC \NR +\NC \prm {Umathsubsupshiftdown} \NC subscript drop in the presence of a superscript \NC \NR +\NC \prm {Umathsubtopmax} \NC the top of standalone subscripts cannot be higher than this above the baseline \NC \NR -\NC \lpr {Umathsupbottommin} \NC the bottom of standalone superscripts cannot be less than +\NC \prm {Umathsupbottommin} \NC the bottom of standalone superscripts cannot be less than this above the baseline \NC \NR -\NC \lpr {Umathsupsubbottommax} \NC the bottom of the superscript of a combined super- and subscript +\NC \prm {Umathsupsubbottommax} \NC the bottom of the superscript of a combined super- and subscript be at least as high as this above the baseline \NC \NR -\NC \lpr {Umathsubsupvgap} \NC vertical clearance between super- and subscript \NC \NR -\NC \lpr {Umathspacebeforescript} \NC additional space added before a super- or subprescript (bonus setting) \NC \NR -\NC \lpr {Umathspaceafterscript} \NC additional space added after a super- or subscript \NC \NR -\NC \lpr {Umathconnectoroverlapmin}\NC minimum overlap between parts in an extensible recipe \NC \NR +\NC \prm {Umathsubsupvgap} \NC vertical clearance between super- and subscript \NC \NR +\NC \prm {Umathspacebeforescript} \NC additional space added before a super- or subprescript (bonus setting) \NC \NR +\NC \prm {Umathspaceafterscript} \NC additional space added after a super- or subscript \NC \NR +\NC \prm {Umathconnectoroverlapmin}\NC minimum overlap between parts in an extensible recipe \NC \NR \LL \stoptabulate @@ -533,39 +533,39 @@ dimension parameter. For math fonts, this should be set to zero. \LL \stoptabulate -Note 1: \OPENTYPE\ fonts set \lpr {Umathlimitabovekern} and \lpr -{Umathlimitbelowkern} to zero and set \lpr {Umathquad} to the font size of the +Note 1: \OPENTYPE\ fonts set \prm {Umathlimitabovekern} and \prm +{Umathlimitbelowkern} to zero and set \prm {Umathquad} to the font size of the used font, because these are not supported in the \type {MATH} table, -Note 2: Traditional \TFM\ fonts do not set \lpr {Umathradicalrule} because +Note 2: Traditional \TFM\ fonts do not set \prm {Umathradicalrule} because \TEX82\ uses the height of the radical instead. When this parameter is indeed not set when \LUATEX\ has to typeset a radical, a backward compatibility mode will kick in that assumes that an oldstyle \TEX\ font is used. Also, they do not set -\lpr {Umathradicaldegreebefore}, \lpr {Umathradicaldegreeafter}, and \lpr +\prm {Umathradicaldegreebefore}, \prm {Umathradicaldegreeafter}, and \prm {Umathradicaldegreeraise}. These are then automatically initialized to $5/18$quad, $-10/18$quad, and 60. -Note 3: If \TFM\ fonts are used, then the \lpr {Umathradicalvgap} is not set +Note 3: If \TFM\ fonts are used, then the \prm {Umathradicalvgap} is not set until the first time \LUATEX\ has to typeset a formula because this needs parameters from both family~2 and family~3. This provides a partial backward -compatibility with \TEX82, but that compatibility is only partial: once the \lpr +compatibility with \TEX82, but that compatibility is only partial: once the \prm {Umathradicalvgap} is set, it will not be recalculated any more. -Note 4: When \TFM\ fonts are used a similar situation arises with respect to \lpr +Note 4: When \TFM\ fonts are used a similar situation arises with respect to \prm {Umathspaceafterscript}: it is not set until the first time \LUATEX\ has to typeset a formula. This provides some backward compatibility with \TEX82. But -once the \lpr {Umathspaceafterscript} is set, \prm {scriptspace} will never be +once the \prm {Umathspaceafterscript} is set, \prm {scriptspace} will never be looked at again. -Note 5: Traditional \TFM\ fonts set \lpr {Umathconnectoroverlapmin} to zero +Note 5: Traditional \TFM\ fonts set \prm {Umathconnectoroverlapmin} to zero because \TEX82\ always stacks extensibles without any overlap. -Note 6: The \lpr {Umathoperatorsize} is only used in \prm {displaystyle}, and is +Note 6: The \prm {Umathoperatorsize} is only used in \prm {displaystyle}, and is only set in \OPENTYPE\ fonts. In \TFM\ font mode, it is artificially set to one scaled point more than the initial attempt's size, so that always the \quote {first next} will be tried, just like in \TEX82. -Note 7: The \lpr {Umathradicaldegreeraise} is a special case because it is the +Note 7: The \prm {Umathradicaldegreeraise} is a special case because it is the only parameter that is expressed in a percentage instead of a number of scaled points. @@ -581,16 +581,16 @@ math font Cambria, but were useful enough to be added. \startsection[title={Math spacing}] -\subsection{Setting inline surrounding space with \lpr {mathsurround[skip]}} +\subsection{Setting inline surrounding space with \prm {mathsurround} and \prm {mathsurroundskip}} \topicindex {math+spacing} Inline math is surrounded by (optional) \prm {mathsurround} spacing but that is a fixed -dimension. There is now an additional parameter \lpr {mathsurroundskip}. When set to a +dimension. There is now an additional parameter \prm {mathsurroundskip}. When set to a non|-|zero value (or zero with some stretch or shrink) this parameter will replace \prm {mathsurround}. By using an additional parameter instead of changing the nature of \prm {mathsurround}, we can remain compatible. In the meantime a bit more -control has been added via \lpr {mathsurroundmode}. This directive can take 6 values +control has been added via \prm {mathsurroundmode}. This directive can take 6 values with zero being the default behaviour. \start @@ -614,14 +614,14 @@ with zero being the default behaviour. \starttabulate[|c|c|c|pl|] \DB mode \BC x\$x\$x \BC x \$x\$ x \BC effect \NC \NR \TB -\OneLiner{0}{obey \prm {mathsurround} when \lpr {mathsurroundskip} is 0pt} +\OneLiner{0}{obey \prm {mathsurround} when \prm {mathsurroundskip} is 0pt} \OneLiner{1}{only add skip to the left} \OneLiner{2}{only add skip to the right} \OneLiner{3}{add skip to the left and right} \OneLiner{4}{ignore the skip setting, obey \prm {mathsurround}} \OneLiner{5}{disable all spacing around math} -\OneLiner{6}{only apply \lpr {mathsurroundskip} when also spacing} -\OneLiner{7}{only apply \lpr {mathsurroundskip} when no spacing} +\OneLiner{6}{only apply \prm {mathsurroundskip} when also spacing} +\OneLiner{7}{only apply \prm {mathsurroundskip} when no spacing} \LL \stoptabulate @@ -637,7 +637,7 @@ node and not always treated as normal glue: it travels with the begin and end math nodes. Also, method 6 and 7 will zero the skip related fields in a node when applicable in the first occasion that checks them (linebreaking or packaging). -\subsection{Pairwise spacing and \lpr {Umath...spacing} commands} +\subsection{Pairwise spacing and \tex {Umath...spacing} commands} \topicindex {math+spacing} @@ -648,70 +648,70 @@ types, but for completeness' sake, here is the whole list: \starttwocolumns \startlines -\lpr {Umathordordspacing} -\lpr {Umathordopspacing} -\lpr {Umathordbinspacing} -\lpr {Umathordrelspacing} -\lpr {Umathordopenspacing} -\lpr {Umathordclosespacing} -\lpr {Umathordpunctspacing} -\lpr {Umathordinnerspacing} -\lpr {Umathopordspacing} -\lpr {Umathopopspacing} -\lpr {Umathopbinspacing} -\lpr {Umathoprelspacing} -\lpr {Umathopopenspacing} -\lpr {Umathopclosespacing} -\lpr {Umathoppunctspacing} -\lpr {Umathopinnerspacing} -\lpr {Umathbinordspacing} -\lpr {Umathbinopspacing} -\lpr {Umathbinbinspacing} -\lpr {Umathbinrelspacing} -\lpr {Umathbinopenspacing} -\lpr {Umathbinclosespacing} -\lpr {Umathbinpunctspacing} -\lpr {Umathbininnerspacing} -\lpr {Umathrelordspacing} -\lpr {Umathrelopspacing} -\lpr {Umathrelbinspacing} -\lpr {Umathrelrelspacing} -\lpr {Umathrelopenspacing} -\lpr {Umathrelclosespacing} -\lpr {Umathrelpunctspacing} -\lpr {Umathrelinnerspacing} -\lpr {Umathopenordspacing} -\lpr {Umathopenopspacing} -\lpr {Umathopenbinspacing} -\lpr {Umathopenrelspacing} -\lpr {Umathopenopenspacing} -\lpr {Umathopenclosespacing} -\lpr {Umathopenpunctspacing} -\lpr {Umathopeninnerspacing} -\lpr {Umathcloseordspacing} -\lpr {Umathcloseopspacing} -\lpr {Umathclosebinspacing} -\lpr {Umathcloserelspacing} -\lpr {Umathcloseopenspacing} -\lpr {Umathcloseclosespacing} -\lpr {Umathclosepunctspacing} -\lpr {Umathcloseinnerspacing} -\lpr {Umathpunctordspacing} -\lpr {Umathpunctopspacing} -\lpr {Umathpunctbinspacing} -\lpr {Umathpunctrelspacing} -\lpr {Umathpunctopenspacing} -\lpr {Umathpunctclosespacing} -\lpr {Umathpunctpunctspacing} -\lpr {Umathpunctinnerspacing} -\lpr {Umathinnerordspacing} -\lpr {Umathinneropspacing} -\lpr {Umathinnerbinspacing} -\lpr {Umathinnerrelspacing} -\lpr {Umathinneropenspacing} -\lpr {Umathinnerclosespacing} -\lpr {Umathinnerpunctspacing} -\lpr {Umathinnerinnerspacing} +\prm {Umathordordspacing} +\prm {Umathordopspacing} +\prm {Umathordbinspacing} +\prm {Umathordrelspacing} +\prm {Umathordopenspacing} +\prm {Umathordclosespacing} +\prm {Umathordpunctspacing} +\prm {Umathordinnerspacing} +\prm {Umathopordspacing} +\prm {Umathopopspacing} +\prm {Umathopbinspacing} +\prm {Umathoprelspacing} +\prm {Umathopopenspacing} +\prm {Umathopclosespacing} +\prm {Umathoppunctspacing} +\prm {Umathopinnerspacing} +\prm {Umathbinordspacing} +\prm {Umathbinopspacing} +\prm {Umathbinbinspacing} +\prm {Umathbinrelspacing} +\prm {Umathbinopenspacing} +\prm {Umathbinclosespacing} +\prm {Umathbinpunctspacing} +\prm {Umathbininnerspacing} +\prm {Umathrelordspacing} +\prm {Umathrelopspacing} +\prm {Umathrelbinspacing} +\prm {Umathrelrelspacing} +\prm {Umathrelopenspacing} +\prm {Umathrelclosespacing} +\prm {Umathrelpunctspacing} +\prm {Umathrelinnerspacing} +\prm {Umathopenordspacing} +\prm {Umathopenopspacing} +\prm {Umathopenbinspacing} +\prm {Umathopenrelspacing} +\prm {Umathopenopenspacing} +\prm {Umathopenclosespacing} +\prm {Umathopenpunctspacing} +\prm {Umathopeninnerspacing} +\prm {Umathcloseordspacing} +\prm {Umathcloseopspacing} +\prm {Umathclosebinspacing} +\prm {Umathcloserelspacing} +\prm {Umathcloseopenspacing} +\prm {Umathcloseclosespacing} +\prm {Umathclosepunctspacing} +\prm {Umathcloseinnerspacing} +\prm {Umathpunctordspacing} +\prm {Umathpunctopspacing} +\prm {Umathpunctbinspacing} +\prm {Umathpunctrelspacing} +\prm {Umathpunctopenspacing} +\prm {Umathpunctclosespacing} +\prm {Umathpunctpunctspacing} +\prm {Umathpunctinnerspacing} +\prm {Umathinnerordspacing} +\prm {Umathinneropspacing} +\prm {Umathinnerbinspacing} +\prm {Umathinnerrelspacing} +\prm {Umathinneropenspacing} +\prm {Umathinnerclosespacing} +\prm {Umathinnerpunctspacing} +\prm {Umathinnerinnerspacing} \stoplines \stoptwocolumns @@ -736,7 +736,7 @@ marked \type {*} in the \TEX book. These will not actually be used as those combinations of atoms cannot actually happen, but it seemed better not to break orthogonality. They are initialized to zero. -\subsection{Local \lpr {frozen} settings with} +\subsection{Local \prm {frozen} settings with} Math is processed in two passes. The first pass is needed to intercept for instance \type {\over}, one of the few \TEX\ commands that actually has a @@ -777,12 +777,12 @@ unprocessed math list. The result looks as follows: \blank \getbuffer \blank -\subsection{Checking a state with \lpr {ifmathparameter}} +\subsection{Checking a state with \prm {ifmathparameter}} When you adapt math parameters it might make sense to see if they are set at all. When a parameter is unset its value has the maximum dimension value and you might for instance mistakenly multiply that value to open up things a bit, which gives -unexpected side effects. For that reason there is a convenient checker: \lpr +unexpected side effects. For that reason there is a convenient checker: \prm {ifmathparameter}. This test primitive behaves like an \prm {ifcase}, with: \starttabulate[|c|l|] @@ -794,14 +794,14 @@ unexpected side effects. For that reason there is a convenient checker: \lpr \LL \stoptabulate -\subsection{Skips around display math and \lpr {mathdisplayskipmode}} +\subsection{Skips around display math and \prm {mathdisplayskipmode}} \topicindex {math+spacing} The injection of \prm {abovedisplayskip} and \prm {belowdisplayskip} is not symmetrical. An above one is always inserted, also when zero, but the below is only inserted when larger than zero. Especially the latter makes it sometimes hard -to fully control spacing. Therefore \LUATEX\ comes with a new directive: \lpr +to fully control spacing. Therefore \LUATEX\ comes with a new directive: \prm {mathdisplayskipmode}. The following values apply: \starttabulate[|c|l|] @@ -814,14 +814,14 @@ to fully control spacing. Therefore \LUATEX\ comes with a new directive: \lpr \LL \stoptabulate -\subsection {Nolimit correction with \lpr {mathnolimitsmode}} +\subsection {Nolimit correction with \prm {mathnolimitsmode}} \topicindex {math+limits} -There are two extra math parameters \lpr {Umathnolimitsupfactor} and \lpr +There are two extra math parameters \prm {Umathnolimitsupfactor} and \prm {Umathnolimitsubfactor} that were added to provide some control over how limits are spaced (for example the position of super and subscripts after integral -operators). They relate to an extra parameter \lpr {mathnolimitsmode}. The half +operators). They relate to an extra parameter \prm {mathnolimitsmode}. The half corrections are what happens when scripts are placed above and below. The problem with italic corrections is that officially that correction italic is used for above|/|below placement while advanced kerns are used for placement at the @@ -868,15 +868,15 @@ When the mode is set to one, the math parameters are used. This way a macro package writer can decide what looks best. Given the current state of fonts in \CONTEXT\ we currently use mode 1 with factor 0 for the superscript and 750 for the subscripts. Positive values are used for both parameters but the subscript -shifts to the left. A \lpr {mathnolimitsmode} larger that 15 is considered to +shifts to the left. A \prm {mathnolimitsmode} larger that 15 is considered to be a factor for the subscript correction. This feature can be handy when experimenting. -\subsection {Controlling math italic mess with \lpr {mathitalicsmode}} +\subsection {Controlling math italic mess with \prm {mathitalicsmode}} \topicindex {math+italics} -The \lpr {mathitalicsmode} parameter can be set to~1 to force italic correction +The \prm {mathitalicsmode} parameter can be set to~1 to force italic correction before noads that represent some more complex structure (read: everything that is not an ord, bin, rel, open, close, punct or inner). We show a Cambria example. @@ -902,7 +902,7 @@ example. This kind of parameters relate to the fact that italic correction in \OPENTYPE\ math is bound to fuzzy rules. So, control is the solution. -\subsection {Influencing script kerning with \lpr {mathscriptboxmode}} +\subsection {Influencing script kerning with \prm {mathscriptboxmode}} \topicindex {math+kerning} \topicindex {math+scripts} @@ -911,7 +911,7 @@ If you want to typeset text in math macro packages often provide something \type {\text} which obeys the script sizes. As the definition can be anything there is a good chance that the kerning doesn't come out well when used in a script. Given that the first glyph ends up in an \prm {hbox} we have some control over this. -And, as a bonus we also added control over the normal sublist kerning. The \lpr +And, as a bonus we also added control over the normal sublist kerning. The \prm {mathscriptboxmode} parameter defaults to~1. \starttabulate[|c|l|] @@ -957,7 +957,7 @@ italics, while other fonts can lack kerns. \NC dejavu \NC \Show{1}{0}{dejavu} \NC\Show{1}{1}{dejavu} \NC \Show{2}{1}{dejavu} \NC \Show{2}{2}{dejavu} \NC \Show{3}{3}{dejavu} \NC \NR \stoptabulate -Kerning between a character subscript is controlled by \lpr {mathscriptcharmode} +Kerning between a character subscript is controlled by \prm {mathscriptcharmode} which also defaults to~1. Here is another example. Internally we tag kerns as italic kerns or font kerns @@ -990,19 +990,19 @@ control over what one can turn on and off. \LL \stoptabulate -\subsection{Forcing fixed scripts with \lpr {mathscriptsmode}} +\subsection{Forcing fixed scripts with \prm {mathscriptsmode}} We have three parameters that are used for this fixed anchoring: \starttabulate[|c|l|] \DB parameter \BC register \NC \NR -\NC $d$ \NC \lpr {Umathsubshiftdown} \NC \NR -\NC $u$ \NC \lpr {Umathsupshiftup} \NC \NR -\NC $s$ \NC \lpr {Umathsubsupshiftdown} \NC \NR +\NC $d$ \NC \prm {Umathsubshiftdown} \NC \NR +\NC $u$ \NC \prm {Umathsupshiftup} \NC \NR +\NC $s$ \NC \prm {Umathsubsupshiftdown} \NC \NR \LL \stoptabulate -When we set \lpr {mathscriptsmode} to a value other than zero these are used +When we set \prm {mathscriptsmode} to a value other than zero these are used for calculating fixed positions. This is something that is needed for instance for chemistry. You can manipulate the mentioned variables to achieve different effects. @@ -1027,7 +1027,7 @@ formula. % if needed we can put the value in stylenodes but maybe more should go there -\subsection{Penalties: \lpr {mathpenaltiesmode}} +\subsection{Penalties: \prm {mathpenaltiesmode}} \topicindex {math+penalties} @@ -1051,7 +1051,7 @@ makes sense. As a bonus we also provide two extra penalties: They default to inifinite which signals that they don't need to be inserted. When set they are injected before a binop or rel noad. This is an experimental feature. -\subsection{Equation spacing: \lpr {matheqnogapstep}} +\subsection{Equation spacing: \prm {matheqnogapstep}} By default \TEX\ will add one quad between the equation and the number. This is hard coded. A new primitive can control this: @@ -1069,17 +1069,17 @@ is divided by 1000 which is the usual way to mimmick floating point factors in \startsection[title={Math constructs}] -\subsection {Unscaled fences and \lpr{mathdelimitersmode}} +\subsection {Unscaled fences and \prm{mathdelimitersmode}} \topicindex {math+fences} -The \lpr {mathdelimitersmode} primitive is experimental and deals with the +The \prm {mathdelimitersmode} primitive is experimental and deals with the following (potential) problems. Three bits can be set. The first bit prevents an unwanted shift when the fence symbol is not scaled (a cambria side effect). The second bit forces italic correction between a preceding character ordinal and the fenced subformula, while the third bit turns that subformula into an ordinary so that the same spacing applies as with unfenced variants. Here we show Cambria -(with \lpr {mathitalicsmode} enabled). +(with \prm {mathitalicsmode} enabled). \starttexdefinition Whatever #1 \NC \type{\mathdelimitersmode = #1} @@ -1142,16 +1142,16 @@ In typeset form this looks like: \getbuffer -\subsection[mathacc]{Accent handling with \lpr {Umathaccent}} +\subsection[mathacc]{Accent handling with \prm {Umathaccent}} \topicindex {math+accents} \LUATEX\ supports both top accents and bottom accents in math mode, and math accents stretch automatically (if this is supported by the font the accent comes from, of course). Bottom and combined accents as well as fixed-width math accents -are controlled by optional keywords following \lpr {Umathaccent}. +are controlled by optional keywords following \prm {Umathaccent}. -The keyword \type {bottom} after \lpr {Umathaccent} signals that a bottom accent +The keyword \type {bottom} after \prm {Umathaccent} signals that a bottom accent is needed, and the keyword \type {both} signals that both a top and a bottom accent are needed (in this case two accents need to be specified, of course). @@ -1191,20 +1191,20 @@ fraction only applies to the stepwise selected shapes and is mostly meant for th \type {overlay} location. It also works for the other locations but then it concerns the width. -\subsection{Building radicals with \lpr {Uradical} and \lpr {Uroot}} +\subsection{Building radicals with \prm {Uradical} and \prm {Uroot}} \topicindex {math+radicals} -The new primitive \lpr {Uroot} allows the construction of a radical noad -including a degree field. Its syntax is an extension of \lpr {Uradical}: +The new primitive \prm {Uroot} allows the construction of a radical noad +including a degree field. Its syntax is an extension of \prm {Uradical}: \starttyping \Uradical <fam integer> <char integer> <radicand> \Uroot <fam integer> <char integer> <degree> <radicand> \stoptyping -The placement of the degree is controlled by the math parameters \lpr -{Umathradicaldegreebefore}, \lpr {Umathradicaldegreeafter}, and \lpr +The placement of the degree is controlled by the math parameters \prm +{Umathradicaldegreebefore}, \prm {Umathradicaldegreeafter}, and \prm {Umathradicaldegreeraise}. The degree will be typeset in \prm {scriptscriptstyle}. @@ -1267,16 +1267,16 @@ next higher height and kern pair, or the highest one in the character (if there value high enough in the character), or simply zero (if the character has no math kern pairs at all). -\subsection{Scripts on extensibles: \lpr {Uunderdelimiter}, \lpr {Uoverdelimiter}, -\lpr {Udelimiterover}, \lpr {Udelimiterunder} and \lpr {Uhextensible}} +\subsection{Scripts on extensibles: \prm {Uunderdelimiter}, \prm {Uoverdelimiter}, +\prm {Udelimiterover}, \prm {Udelimiterunder} and \prm {Uhextensible}} \topicindex {math+scripts} \topicindex {math+delimiters} \topicindex {math+extensibles} -The primitives \lpr {Uunderdelimiter} and \lpr {Uoverdelimiter} allow the +The primitives \prm {Uunderdelimiter} and \prm {Uoverdelimiter} allow the placement of a subscript or superscript on an automatically extensible item and -\lpr {Udelimiterunder} and \lpr {Udelimiterover} allow the placement of an +\prm {Udelimiterunder} and \prm {Udelimiterover} allow the placement of an automatically extensible item as a subscript or superscript on a nucleus. The input: @@ -1294,18 +1294,18 @@ $\Udelimiterunder 0 "2194 {\hbox{\strut delimiterunder}}$ \blank \startnarrower \getbuffer \stopnarrower \blank -The vertical placements are controlled by \lpr {Umathunderdelimiterbgap}, \lpr -{Umathunderdelimitervgap}, \lpr {Umathoverdelimiterbgap}, and \lpr +The vertical placements are controlled by \prm {Umathunderdelimiterbgap}, \prm +{Umathunderdelimitervgap}, \prm {Umathoverdelimiterbgap}, and \prm {Umathoverdelimitervgap} in a similar way as limit placements on large operators. -The superscript in \lpr {Uoverdelimiter} is typeset in a suitable scripted style, -the subscript in \lpr {Uunderdelimiter} is cramped as well. +The superscript in \prm {Uoverdelimiter} is typeset in a suitable scripted style, +the subscript in \prm {Uunderdelimiter} is cramped as well. These primitives accepts an optional \type {width} specification. When used the also optional keywords \type {left}, \type {middle} and \type {right} will determine what happens when a requested size can't be met (which can happen when we step to successive larger variants). -An extra primitive \lpr {Uhextensible} is available that can be used like this: +An extra primitive \prm {Uhextensible} is available that can be used like this: \startbuffer $\Uhextensible width 10cm 0 "2194$ @@ -1330,7 +1330,7 @@ $\Uhextensible width 1pt middle 0 "2194$ font metrics are involved we have a different code path for traditional fonts end \OPENTYPE\ fonts. -\subsection{Fractions and the new \lpr {Uskewed} and \lpr {Uskewedwithdelims}} +\subsection{Fractions and the new \prm {Uskewed} and \prm {Uskewedwithdelims}} \topicindex {math+fractions} @@ -1348,7 +1348,7 @@ vertical gap for skewed fractions. Of course some guessing is needed in order to implement something that uses them. And so we now provide a primitive similar to the other fraction related ones but with a few options so that one can influence the rendering. Of course a user can also mess around a bit with the parameters -\lpr {Umathskewedfractionhgap} and \lpr {Umathskewedfractionvgap}. +\prm {Umathskewedfractionhgap} and \prm {Umathskewedfractionvgap}. The syntax used here is: @@ -1414,9 +1414,9 @@ The optional arguments are also supported but we have one extra option: \type \Uover style \scriptstyle {top} {bottom} \stoptyping -The complete list of these commands is: \lpr {Uabove}, \lpr {Uatop}, \lpr -{Uover}, \lpr {Uabovewithdelims}, \lpr {Uatopwithdelims}, \lpr {Uoverwithdelims}, -\lpr {UUskewed}, \lpr {UUskewedwithdelims}. As with other extensions we use a +The complete list of these commands is: \prm {Uabove}, \prm {Uatop}, \prm +{Uover}, \prm {Uabovewithdelims}, \prm {Uatopwithdelims}, \prm {Uoverwithdelims}, +\prm {UUskewed}, \prm {UUskewedwithdelims}. As with other extensions we use a leading \type {U} and because we already had extra skew related primitives we end up with a \type {UU} there. This obscurity is not that big an issue because normally such primitives are wrapped in a macro. Here are a few examples: @@ -1437,7 +1437,7 @@ $\Uover style \scriptscriptstyle {1234} {5678} $\blank These render as: \getbuffer -\subsection {Math styles: \lpr {Ustyle}} +\subsection {Math styles: \prm {Ustyle}} This primitive accepts a style identifier: @@ -1453,7 +1453,7 @@ This in itself is not spectacular because it is equivalent to Both commands inject a style node and change the current style. However, as in other places where \LUAMETATEX\ expects a style you can also pass a number in the range -zero upto seven (like the ones reported by the primitive \lpr {mathstyle}). So, the +zero upto seven (like the ones reported by the primitive \prm {mathstyle}). So, the next few lines give identical results: \startbuffer @@ -1467,7 +1467,7 @@ Like: \inlinebuffer . Values outside the valid range are ignored. There is an extra option \type {norule} that can be used to suppress the rule while keeping the spacing compatible. -\subsection {Delimiters: \type{\Uleft}, \lpr {Umiddle} and \lpr {Uright}} +\subsection {Delimiters: \type{\Uleft}, \prm {Umiddle} and \prm {Uright}} \topicindex {math+delimiters} @@ -1520,8 +1520,8 @@ non|-|zero value. \startsection[title={Extracting values}] -\subsection{Codes and using \lpr {Umathcode}, \lpr {Umathcharclass}, \lpr -{Umathcharfam} and \lpr {Umathcharslot}} +\subsection{Codes and using \prm {Umathcode}, \prm {Umathcharclass}, \prm +{Umathcharfam} and \prm {Umathcharslot}} \topicindex {math+codes} @@ -1558,7 +1558,7 @@ do the following: \relax} \stoptyping -\subsection {Last lines and \lpr{predisplaygapfactor}} +\subsection {Last lines and \prm{predisplaygapfactor}} \topicindex {math+last line} @@ -1586,8 +1586,8 @@ get the length of the last line, the following will often work too: \startsection[title={Math mode}] -\subsection {Verbose versions of single|-|character math commands like \lpr {Usuperscript} -and \lpr {Usubscript}} +\subsection {Verbose versions of single|-|character math commands like \prm {Usuperscript} +and \prm {Usubscript}} \topicindex {math+styles} @@ -1597,24 +1597,24 @@ and \lpr {Usubscript}} \starttabulate[|l|l|] \DB primitive \BC explanation \NC \NR \TB -\NC \lpr {Usuperscript} \NC duplicates the functionality of \type {^} \NC \NR -\NC \lpr {Usubscript} \NC duplicates the functionality of \type {_} \NC \NR -\NC \lpr {Ustartmath} \NC duplicates the functionality of \type {$}, % $ +\NC \prm {Usuperscript} \NC duplicates the functionality of \type {^} \NC \NR +\NC \prm {Usubscript} \NC duplicates the functionality of \type {_} \NC \NR +\NC \prm {Ustartmath} \NC duplicates the functionality of \type {$}, % $ when used in non-math mode. \NC \NR -\NC \lpr {Ustopmath} \NC duplicates the functionality of \type {$}, % $ +\NC \prm {Ustopmath} \NC duplicates the functionality of \type {$}, % $ when used in inline math mode. \NC \NR -\NC \lpr {Ustartdisplaymath} \NC duplicates the functionality of \type {$$}, % $$ +\NC \prm {Ustartdisplaymath} \NC duplicates the functionality of \type {$$}, % $$ when used in non-math mode. \NC \NR -\NC \lpr {Ustopdisplaymath} \NC duplicates the functionality of \type {$$}, % $$ +\NC \prm {Ustopdisplaymath} \NC duplicates the functionality of \type {$$}, % $$ when used in display math mode. \NC \NR \LL \stoptabulate -The \lpr {Ustopmath} and \lpr {Ustopdisplaymath} primitives check if the current +The \prm {Ustopmath} and \prm {Ustopdisplaymath} primitives check if the current math mode is the correct one (inline vs.\ displayed), but you can freely intermix the four mathon|/|mathoff commands with explicit dollar sign(s). -\subsection{Script commands \lpr {Unosuperscript} and \lpr {Unosubscript}} +\subsection{Script commands \prm {Unosuperscript} and \prm {Unosubscript}} \topicindex {math+styles} \topicindex {math+scripts} @@ -1640,8 +1640,8 @@ results in \inlinebuffer[script]. \topicindex {math+text} \topicindex {text+math} -The commands \prm {mathchar}, and \lpr {Umathchar} and control sequences that are -the result of \prm {mathchardef} or \lpr {Umathchardef} are also acceptable in +The commands \prm {mathchar}, and \prm {Umathchar} and control sequences that are +the result of \prm {mathchardef} or \prm {Umathchardef} are also acceptable in the horizontal and vertical modes. In those cases, the \prm {textfont} from the requested math family is used. @@ -1649,7 +1649,7 @@ requested math family is used. \startsection[title={Goodies}] -\subsection {Flattening: \lpr {mathflattenmode}} +\subsection {Flattening: \prm {mathflattenmode}} \topicindex {math+flattening} @@ -1669,7 +1669,7 @@ This renders as: \blank \start \mathflattenmode\plusone \getbuffer[sample] \stop \blank -When we set \lpr {mathflattenmode} to 31 we get: +When we set \prm {mathflattenmode} to 31 we get: \blank \start \mathflattenmode\numexpr1+2+4+8+16\relax \getbuffer[sample] \stop \blank @@ -1709,7 +1709,7 @@ There are a couple of experimental features. They will stay but details might change, for instance more control over spacing. We just show some examples and let your imagination work it out. First we have prescripts: -\subsection {Prescripts with \lpr {Usuperprescript} and {Usubprescript}} +\subsection {Prescripts with \prm {Usuperprescript} and {Usubprescript}} \startbuffer \hbox{$ @@ -1754,7 +1754,7 @@ These more verbose triggers can be used to build interfaces: \blank \getbuffer \blank -\subsection {Prescripts with \lpr {Usuperprescript} and {Usubprescript}} +\subsection {Prescripts with \prm {Usuperprescript} and {Usubprescript}} You can change the class of a math character on the fly: |