Laenkea

Template:descendant tree/documentation: Difference between revisions

Template Discussion

Template:descendant tree/documentation (view source)

Revision as of 19:46, 2 June 2024

2,572 bytes added ,  2 June 2024
ਕੋਈ ਸੋਧ ਸਾਰ ਨਹੀਂ
No edit summary
(4 intermediate revisions by the same user not shown)
Line 171: Line 171:
|ryn-pro>rad-pro_rad-o:Pailjews
|ryn-pro>rad-pro_rad-o:Pailjews
|ryn-pro>rad-pro_rad-o_rad:Paijøs
|ryn-pro>rad-pro_rad-o_rad:Paijøs
}}</td></tr></table>
==== Order-based shorthand ====
As a shorthand to the above system, prefacing a language code with <code>>></code> will parse it as a borrowing from the language specified before it. Similarly, using the prefix <code>_</code> without a language code before it will parse it as a descendant of the last defined language code. While useful as a shorthand, this only works with a singular descendant branch.
<table width=100%><tr><td width=50%><pre>{{descendant tree
|hrd-pro:Thwɛ̄́ljeŋjəs
|rad-pro:Θwêljeŋjs
|rad-o:Þø̄ljeŋjs
|rad:Þýljenș
|ryn-pro:Páiljeḡă
|>>rad-pro:Pailjeɣs
|_rad-o:Pailjews
|_rad:Paijøs
|ryn-o:Pailjeŗ
|ryn:Pailiŗ
}}</pre></td><td>→</td><td>{{descendant tree
|hrd-pro:Thwɛ̄́ljeŋjəs
|rad-pro:Θwêljeŋjs
|rad-o:Þø̄ljeŋjs
|rad:Þýljenș
|ryn-pro:Páiljeḡă
|>>rad-pro:Pailjeɣs
|_rad-o:Pailjews
|_rad:Paijøs
|ryn-o:Pailjeŗ
|ryn:Pailiŗ
}}</td></tr></table>
}}</td></tr></table>


Line 181: Line 208:
|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 193: Line 219:
|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>
}}</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.
 
<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-m:lýrus
|rad:lyerdzs<t:gas>
|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-m:lýrdzs
|rad-m:lýrus
|rad:lyerdzs<t:gas>
|rad:lýrus<t:air>
}}</td></tr></table>


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.
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>
Retrieved from ‘https://wiki.laenkea.si/wiki/Special:MobileDiff/12332...12398’