Template:affixusex/documentation

This template creates usage examples for affix entries in the format word + -suffix → suffixed word or prefix- + word → prefixed word. More complex entries are also possible, e.g.:
 * word1 + word2 + -suffix → suffixed word
 * prefix- + word1 + word2 → prefixed word
 * word1 + -suffix1 → suffixed word 1 + -suffix2 → suffixed word 2
 * prefix1- + word1 → prefixed word 1 + -suffix2 → suffixed word 2
 * word1 (qualifier) + word2 → combined word

Numbered parameters

 * 1
 * the language code;


 * 2, 3, ...
 * usage example components.

If the page's name is a prefix, it will normally be interpolated into the components before the first one. Similarly, if the page's name is a suffix, it will normally be interpolated into the components before the last one. Such interpolated affixes will be displayed without any link. This will not happen if the page's name (including if decorated with extra diacritics) appears among the components, or if an affix among the components is preceded by an exclamation point (!). Such affixes will likewise be displayed without any link. You can entirely suppress the interpolation of the page name into the components using nointerp, and override the form of the interpolated affix (e.g. adding extra diacritics, as an alternative to explicitly inserting the affix among the components) using altaff. Note that the value specified using altaff has to look like a prefix or suffix for it to be interpolated, as with the page's name.

Normally, components are separated by a plus sign (+), except that between the second-to-last and last components a right arrow will be displayed (→); but this can be overridden by  attached to the component or using arrowN.

If a given component is in a different language than what is specified in 1, prefix the component with the language code of its language, e.g.  or.

Named parameters

 * altaff
 * The affix's alternative display text (only used when no affix is present among the components and when nointerp isn't given).


 * nointerp
 * Suppress the automatic interpolation of an affix into the components when no affix is present among the components.


 * t1, t2, t3, ... or gloss1, gloss2, gloss3, ...
 * The translation of a given component.


 * alt1, alt2, alt3, ...
 * The alternative display text of a given component.


 * tr1, tr2, tr3, ...
 * The transliteration of a given component.


 * ts1, ts2, ts3, ...
 * The transcription of a given component, in languages where the transliteration and transcription differ markedly (see ).


 * g1, g2, g3, ...
 * The gender of a given component (multiple comma-separated genders may be specified for a given component).


 * lit1, lit2, lit3, ...
 * The literal meaning of a given component.


 * pos1, pos2, pos3, ...
 * The part of speech of a given component.


 * q1, q2, q3, ...
 * Qualifier text to display before a given component, in parens and normally italicized.


 * qq1, qq2, qq3, ...
 * Qualifier text to display after a given component, in parens and normally italicized.


 * arrow1, arrow2, arrow3, ...
 * Should be a boolean value (, ,  , etc.), and if specified, an arrow will appear before the component instead of a plus sign.


 * joiner1, joiner2, joiner3, ...
 * If specified, override the arrow or plus sign that appears before the component with the specified text or symbol.


 * fulljoiner1, fulljoiner2, fulljoiner3, ...
 * If specified, override the arrow or plus sign that appears before the component, as well as the spaces on either side, with the specified text or symbol (e.g. use ,&amp;#32; to insert a comma between the first and second components).


 * id1, id2, id3, ...
 * The sense ID of a given component (see ).


 * accel1, accel2, accel3, ...
 * The acceleration tag of a given component (see ).


 * sc
 * The script code of the components (rarely needs to be specified).


 * lang1, lang2, lang3, ...
 * The language code of a given component, if that component is in a different language from the remaining components. It is preferable to specify such a language code as a prefix to the component itself, e.g. using  or , instead of using lang N.


 * sc1, sc2, sc3, ...
 * The script code of a given component where langN is also given (rarely needs to be specified).


 * pagename
 * Override the page name used when deciding whether to interpolate a prefix or suffix. Useful especially on documentation and test pages.

Inline modifiers
All of the per-term parameters described above can alternatively be specified as inline modifiers, using a syntax like  to specify modifiers such as transliterations, genders, glosses and qualifiers. In this example, for the Russian term, the gloss "to cut off, to chop off" and gender  (perfective) are given. Specifically, the following modifiers are recognized; see the above documentation for more information on the exact meaning of each modifier.
 * or : gloss
 * : alternative display text
 * : transliteration
 * : transcription, for languages where the transliteration and pronunciation are markedly different
 * : comma-separated list of gender/number specifications
 * : literal meaning
 * : part of speech
 * : qualifier, e.g. rare; this appears before the component, parenthesized and italicized
 * : qualifier, e.g. rare; this appears after the component, parenthesized and italicized
 * : part of speech
 * : change the plus sign before the component to a right arrow
 * : override the arrow or plus sign before the component with the specified text or symbol
 * : override the arrow or plus sign before the component, along with the spaces on either side, with the specified text or symbol
 * : sense ID
 * : acceleration tag
 * : language code for the component; overrides the lang parameter; can also be specified inline using e.g.  or
 * : script code for the component

Examples
The following code, for use in : generates Note how the suffix is interpolated before the final component.

The following code, for use in, is similar, but specifies the affix explicitly: It generates:

The following code for, shows how to specify a term derived from a component in a different language: It generates: Note how the Latin word, with a macron in it, is correctly linked to a page that does not include the macron in its name.

The following code, for, shows how to handle the situation where the suffix itself has extra decoration (a length mark, an acute accent indicating stress, etc.): It generates: In this case, an explicit affix (or altaff) is needed because the entry itself is named, without the length mark.

The following code is equivalent: It generates:

The following is a more complex example, for use in : It generates (with the prefix interpolated before the first component):

The following is a significantly more complex example, for use in and demonstrating the way perfective verbs are derived from imperfective verbs and vice-versa: It generates: