Template:bg-derived verbs/documentation

Overview
The purpose of this template is to simplify the task of adding derived verbs to the  section of a Bulgarian verb entry. Like in other Slavic languages, Bulgarian verbs exhibit the following two properties:
 * rich opportunities for verbal derivation using prefixes such as, , , , etc.
 * variants that differ by aspect: perfective or imperfective

With the help of this template, you can save yourself a lot of typing by specifying the prefixes to use, and the perfective/imperfective "stems" to attach them to.

Motivating examples
Here are a few motivating examples to provide some intuition about how this template is used. You can find an in-depth explanation of template options in the next section.

чета́
This is a straightforward example where we wish to list pairs of perfective and imperfective derived verbs, given a base pattern for the perfective and imperfective form and a list of prefixes to apply. By default, the pattern (introduced by ) starts with the perfective base. The resulting derived verbs will be sorted alphabetically.

produces:

садя́
This example demonstrates the support for more than one "base" per aspect, as well as the ability to manually override things e.g. when not all per-aspect options make sense.

produces:

летя́
This example demonstrates the ability to specify multiple groups of derived verbs, which is useful in cases where are more than 2-3 possible derived verbs per prefix. It also shows the ability to sort each group separately (in alphabetical order) by using a line with just a hyphen. Leaving that line out would result in all 5 verb pairs being sorted amongst each other, which is also valid - use your judgment.

produces:

Template options in depth

 * 1) In the most basic use, a slash separates corresponding aspectually paired derived verbs, normally inputted and displayed in the order perfective, imperfective. (Use 1 to switch this and cause both the input and display to put imperfective before perfective.) To include multiple (normally synonymous) verbs for a given aspect, separate them with commas. Use a hyphen by itself to indicate that there is no verb for that aspect.
 * 2) If a line is preceded by , the verbs on that line specify a suffix template. This line is not displayed, but establishes a set of suffixes to be added to later-specified prefixes. For example,   specifies a suffix template consisting of perfective  and imperfective.
 * 3) If a line has no slash or comma in it, it is a prefix, which is added to the most recently-established suffix template to form the aspect pair. For example,,  and  respectively specify derived verbs /, / and /.
 * 4) If a line with a slash in it has a verb ending in a hyphen, that verb is treated as a prefix and added to the suffix in the corresponding position for the most recently specified suffix template. For example, given , the line   expands to  , which translates to an aspectual pair with perfective  and no imperfective. (Similarly,   translates to an aspectual pair with imperfective  and no perfective.)
 * 5) Normally, all specified paired verbs are automatically sorted lexicographically, ignoring accents. However, a line consisting of a hyphen by itself delineates sorting groups; sorting only happens within a group.
 * 6) Any verb (including prefixes and suffixes) can be followed by one or more inline modifiers. These use the same syntax as in col and variants; alter/alt; syn/ant/etc.; and several other classes of templates. The basic format of an inline modifier is   where   specifies a property to attach to the verb and   is the corersponding value. The recognized properties are as follows:
 * 7) *  (a qualifier preceding the verb);
 * 8) *  (a qualifier following the verb);
 * 9) *  (one or more comma-separated "genders"; here, they should be   or   to override the aspect; use   to specify a biaspectual derived verb such as ;
 * 10) *  or   (a gloss);
 * 11) *  (a part of speech, as in the pos parameter to link/l);
 * 12) *  (override the auto-generated transliteration);
 * 13) *  (specify a transcription, as in the ts parameter to link/l; provided for completeness but makes no sense for Bulgarian);
 * 14) *  (literal meaning);
 * 15) *  (sense ID, as in the id parameter to link/l).