10,731
edits
TheNightAvl (talk | contribs) |
TheNightAvl (talk | contribs) No edit summary |
||
Line 2: | Line 2: | ||
* {{para|1|req=1}}: anchor ID | * {{para|1|req=1}}: anchor ID | ||
* {{para|2}}: anchor content (inline) | * {{para|2}}: anchor content (inline) | ||
'''OR''' | |||
* {{para|1|req=1}}: language code | |||
* {{para|2|req=1}}: anchor ID minus language name | |||
* {{para|3}}: anchor content (inline) | |||
== Anchor naming == | == Anchor naming == | ||
When linking with {{temp|m}}, {{temp|m+}} or {{temp|l}}, anchors will be assumed to begin with the language | When linking with {{temp|m}}, {{temp|m+}} or {{temp|l}}, anchors will be assumed to begin with the language name, followed by the specified anchor parameter. Hence, anchor IDs in Radestrian entries should begin with <code>Radestrian</code>. The following systematic approach is also recommended: | ||
* Etymology sections should be labelled with a number: <code> | * Etymology sections should be labelled with a number: <code>Radestrian1</code> | ||
* Senses should be labelled with a number or description following an underscore: <code> | * Senses should be labelled with a number or description following an underscore: <code>Radestrian_1</code>, <code>Radestrian_vitamin</code> | ||
** Hence, <code> | ** Hence, <code>Radestrian3_vitamin</code> should refer to the vitamin sense of Etymology 3. | ||
Linking can then be done by using {{temp|m|rad|word|'''anchor=3_vitamin'''}}, for example. | Linking can then be done by using {{temp|m|rad|word|'''anchor=3_vitamin'''}}, for example. |