Template:inherited/documentation

This template is used to format the etymology of terms inherited from an earlier stage of the same language. Please only use it under the header 'Etymology'.

When to use
This template is intended for terms that have an unbroken chain of inheritance from the source term in question. For directly borrowed terms, use. For other cases, use.

For example, can be traced all the way back to Proto-Indo-European, and thus it is directly inherited from that Proto-Indo-European term. , meanwhile, was inherited from Old English, but was borrowed in Old English from Latin. Any inheritance that occurred before a break in the chain does not count as inheritance, and would use. was inherited from Middle English, which borrowed it from Old French, which inherited it from Latin. The English term is thus inherited from Middle English, but not from Latin.

This template should not be used for terms that were reformed morphologically during their history. A morphological change breaks the chain of inheritance. The English term does not derive exactly from ; the stem of the word was extended with a suffix at some point ( > ) and thus cannot be considered an inheritance from the original stem. Instead, it is derived from this stem and should therefore use. Likewise, can be traced back to Proto-Germanic, but this term was created anew in Proto-Germanic and cannot be traced back further. However, its individual parts can be traced to Proto-Indo-European and the root, so it is derived from these roots, but not inherited.

See also.

Morphological roots normally have no descendants. Rather, roots are used in word formation, and only the words thus formed have descendants. Consequently, this template should not be used to mark derivation from ancestral roots. English is not inherited from the root, rather it is inherited from a verb derived from this root,. An exception is if the root is itself inherited as another root. In this situation using is legitimate. This is mainly the case with Semitic languages, which still have recognisable and productive roots. Similar considerations apply with other morphological elements such as prefixes and suffixes as well. They are only inherited if they remain as recognisable and (somewhat) productive affixes throughout the history of the language. If the affixes are merely present in the word, but are not recognised as meaningful and distinct morphological elements, then they are no longer considered affixes and thus can't be considered descendants.

Parameters

 * 1
 * The language code (see Languages) of the language which inherited the term, which should be the language of the section that the template is placed in.


 * 2
 * The language code of the language which the term was inherited from. This language needs to be recognized by Module:languages as an ancestor of the language inheriting the term: either as a direct ancestor, or connected by a chain of direct ancestorships.
 * E.g. the direct ancestor of Old French is Latin, whose direct ancestor is Old Latin, whose direct ancestor is Proto-Italic, whose direct ancestor is Proto-Indo-European; therefore it is possible to mark Old French words as inherited from Proto-Indo-European.


 * 3
 * The term in the source language that this term was inherited from. If empty, generates a term request ([Term?]) and places the entry in a term request category, except in some cases like derivations from families or substrates. To override this and disable the term request, use "-".


 * 4 or alt
 * An alternative display form to show for the term, see and.


 * 5 or t or gloss
 * A gloss/translation for the term, see and.


 * tr
 * A transliteration for the term, see and.


 * pos
 * A part of speech indication for the term, see and.


 * g, g2, g3 and so on
 * Gender and number, as in and ; see Module:gender and number for details.


 * lit
 * A literal translation for the term, see and.


 * id
 * A sense id for the term, see and.


 * sc
 * Script code to use. The template can usually figure out the correct code, so this is rarely needed. When no code is given, the template will try to detect the script based on the characters of the word, and if it fails to detect the script, the code  will be used.


 * sort
 * Sort key. Not normally needed.


 * 1
 * Suppress categorization.