Template:descendant tree/documentation: Difference between revisions

No edit summary
Line 181: Line 181:
|ryn:lyr
|ryn:lyr
|rad-pro:lȳrdzir
|rad-pro:lȳrdzir
|rad-o:lȳrdzre
|rad-o:lȳrdzre|lȳrwre
|rad-m:lýrdzs
|rad-m:lýrdzs
|rad:lyerdzs<t:gas>
|rad:lyerdzs<t:gas>
|rad-o:lȳrwre
|rad-m:lýrus
|rad-m:lýrus
|rad:lýrus<t:air>
|rad:lýrus<t:air>
Line 200: Line 199:
}}</td></tr></table>
}}</td></tr></table>


Multiple occurrences of a language code are numbered automatically, and are displayed in order of mention. Note that different branches of hierarchical languages are sorted based on order of specification, i.e. if both <code>|ryn:</code> and <code>|ryn-o:</code> are specified twice, the first specification of <code>|ryn:</code> will be listed under the first specification of <code>|ryn-o:</code>, the second under the second etc.
Multiple occurrences of a language code are numbered automatically, and are displayed in order of specification in the template, '''not in alphabetical order of the terms'''. Note that different branches of hierarchical languages are sorted based on order of specification, i.e. if both <code>|ryn:</code> and <code>|ryn-o:</code> are specified twice, the first specification of <code>|ryn:</code> will be listed under the first specification of <code>|ryn-o:</code>, the second under the second etc.


The indexing can also be specified manually, e.g. <code>|ryn2:</code> and <code>|ryn-o2:</code>. Be aware that if some instances are numbered manually and some aren't, the code will renumber all instances in order of appearance. If you specify <code>|rad:|rad:|rad2:</code> in this order, <code>|rad2:</code> would be reassigned to <code>|rad3:</code>. This is to be borne in mind when organising borrowings. '''All code reassignments result in a script warning for your awareness.'''
The indexing can also be specified manually, e.g. <code>|ryn2:</code> and <code>|ryn-o2:</code>. Be aware that if some instances are numbered manually and some aren't, the code will renumber all instances in order of appearance. If you specify <code>|rad:|rad:|rad2:</code> in this order, <code>|rad2:</code> would be reassigned to <code>|rad3:</code>. This is to be borne in mind when organising borrowings, though the numbering can be inferred from the ordering of the branches. '''All code reassignments result in a script warning for your awareness.'''
 
<table width=100%><tr><td width=50%><pre>{{descendant tree
|hrd-pro:lȳ́rḡis
|ryn-pro:lȳ́rḡi
|ryn-o:lȳr
|ryn:lyr
|rad-pro:lȳrdzir
|rad-o:lȳrdzre|lȳrwre
|rad-m2:lýrdzs
|rad2:lyerdzs<t:gas>
|rad-m:lýrus
|rad:lýrus<t:air>
}}</pre></td><td>→</td><td>{{descendant tree
|hrd-pro:lȳ́rḡis
|ryn-pro:lȳ́rḡi
|ryn-o:lȳr
|ryn:lyr
|rad-pro:lȳrdzir
|rad-o:lȳrdzre|lȳrwre
|rad-m2:lýrdzs
|rad2:lyerdzs<t:gas>
|rad-m:lýrus
|rad:lýrus<t:air>
}}</td></tr></table>


It is also worth noting that if borrowings occur from post-initial specifications of a language, the source language code requires the number to be cited. For example, if you want to specify a <code>|rad:</code> loan from the second specification of <code>|ryn:</code>, you would need to tag it as <code>|ryn2>rad:</code>.
It is also worth noting that if borrowings occur from post-initial specifications of a language, the source language code requires the number to be cited. For example, if you want to specify a <code>|rad:</code> loan from the second specification of <code>|ryn:</code>, you would need to tag it as <code>|ryn2>rad:</code>.
<table width=100%><tr><td width=50%><pre>{{descendant tree
|hrd-pro:lȳ́rḡis
|ryn-pro:lȳ́rḡi
|ryn-o:lȳr
|ryn:lyr
|rad-pro:lȳrdzir
|rad-o:lȳrdzre|lȳrwre
|rad-m:lýrdzs
|rad:lyerdzs<t:gas>
|rad-m:lýrus
|rad:lýrus<t:air>
|rad-m2>lus:lýru
}}</pre></td><td>→</td><td>{{descendant tree
|hrd-pro:lȳ́rḡis
|ryn-pro:lȳ́rḡi
|ryn-o:lȳr
|ryn:lyr
|rad-pro:lȳrdzir
|rad-o:lȳrdzre|lȳrwre
|rad-m:lýrdzs
|rad:lyerdzs<t:gas>
|rad-m:lýrus
|rad:lýrus<t:air>
|rad-m2>lus:lýru
}}</td></tr></table>