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.:
|1=
|2=
, |3=
, ...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 <arrow:1>
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. la:minūtia
or grc:]
.
|altaff=
|nointerp=
isn't given).|nointerp=
|t1=
, |t2=
, |t3=
, ... or |gloss1=
, |gloss2=
, |gloss3=
, ...|alt1=
, |alt2=
, |alt3=
, ...|tr1=
, |tr2=
, |tr3=
, ...|ts1=
, |ts2=
, |ts3=
, ...{{m}}
).|g1=
, |g2=
, |g3=
, ...|lit1=
, |lit2=
, |lit3=
, ...|pos1=
, |pos2=
, |pos3=
, ...|q1=
, |q2=
, |q3=
, ...|qq1=
, |qq2=
, |qq3=
, ...|arrow1=
, |arrow2=
, |arrow3=
, ...y
, 1
, true
, etc.), and if specified, an arrow will appear before the component instead of a plus sign.|joiner1=
, |joiner2=
, |joiner3=
, ...|fulljoiner1=
, |fulljoiner2=
, |fulljoiner3=
, ...|fulljoiner2=, 
to insert a comma between the first and second components).|id1=
, |id2=
, |id3=
, ...{{m}}
).|accel1=
, |accel2=
, |accel3=
, ...{{m}}
).|sc=
|lang1=
, |lang2=
, |lang3=
, ...la:minūtia
or grc:]
, instead of using |langN=
.|sc1=
, |sc2=
, |sc3=
, ...|langN=
is also given (rarely needs to be specified).|pagename=
All of the per-term parameters described above can alternatively be specified as inline modifiers, using a syntax like отсе́чь<t:to ], to ] ]><g:pf>
to specify modifiers such as transliterations, genders, glosses and qualifiers. In this example, for the Russian term отсе́чь (otséčʹ, “to cut off, to chop off”), the gloss "to cut off, to chop off" and gender pf
(perfective) are given. Specifically, the following modifiers are recognized; see the above documentation for more information on the exact meaning of each modifier.
t
or gloss
: glossalt
: alternative display texttr
: transliterationts
: transcription, for languages where the transliteration and pronunciation are markedly differentg
: comma-separated list of gender/number specificationslit
: literal meaningpos
: part of speechq
: qualifier, e.g. rare; this appears before the component, parenthesized and italicizedqq
: qualifier, e.g. rare; this appears after the component, parenthesized and italicizedpos
: part of speecharrow
: change the plus sign before the component to a right arrowjoiner
: override the arrow or plus sign before the component with the specified text or symbolfulljoiner
: override the arrow or plus sign before the component, along with the spaces on either side, with the specified text or symbolid
: sense IDaccel
: acceleration taglang
: language code for the component; overrides the |lang=
parameter; can also be specified inline using e.g. la:minūtia
or grc:]
sc
: script code for the componentThe following code, for use in Portuguese -ada:
#: {{afex|pt|chegar<t:to arrive>|chegada<t:arrival>}}
generates
Note how the suffix is interpolated before the final component.
The following code, for use in Russian -овый (-ovyj), is similar, but specifies the affix explicitly:
#: {{afex|ru|зо́нтик<g:m-in><t:]>|-овый|зо́нтиковый<t:umbrella {{q|relational}}>}}
It generates:
The following code for Portuguese -ário, shows how to specify a term derived from a component in a different language:
#: {{afex|pt|la:lūna<t:moon>|lunário<t:calendar based on moon phases>}}
It generates:
Note how the Latin word lūna, with a macron in it, is correctly linked to a page that does not include the macron in its name.
The following code, for Latin -tūra, shows how to handle the situation where the suffix itself has extra decoration (a length mark, an acute accent indicating stress, etc.):
#: {{afex|la|scrībō<t:to write>|-tūra|scrīptūra<t:scripture>}}
It generates:
In this case, an explicit affix (or |altaff=
) is needed because the entry itself is named -tura, without the length mark.
The following code is equivalent:
#: {{afex|la|scrībō<t:to write>|altaff=-tūra|scrīptūra<t:scripture>}}
It generates:
The following is a more complex example, for use in Russian над- (nad-):
#: {{afex|ru|гроб<t:]><qq:poetic>|-ие<pos:noun-forming suffix>|надгро́бие<t:]><lit:thing '''over''' the grave>}}
It generates (with the prefix interpolated before the first component):
The following is a significantly more complex example, for use in Russian -ать (-atʹ) and demonstrating the way perfective verbs are derived from imperfective verbs and vice-versa:
#: {{afex|ru|от-|сечь<t:to ], to ]><g:impf>|отсе́чь<t:to ], to ] ]><g:pf><arrow:1><qq:underlying stem {{lang|ru|отсе́к-}}>|-а́ть|отсека́ть<g:impf>}}
It generates:
{{prefixusex}}
/{{prefex}}
, {{suffixusex}}
/{{sufex}}
: alternatives specifically for prefixes or suffixes{{ux}}
: to format general usage examples