Template talk:Glossary

This template was considered for deletion on 2014 October 22. The result of the discussion was "keep".

Where to place glossend template

Resolved

– Answered.

In List of rugby league terms I put "glossend" at the end of each section of the list, so e.g.

==A== 
{{gloss}} 
''some terms listed'' 
{{glossend}} 

==B== 
{{gloss}} 
''some terms listed'' 
{{glossend}}

Is this right or should "glossend" only come as the end of "Z"? LunarLander // talk // 13:28, 10 August 2009 (UTC)[reply]

You got it right. Each {{gloss}} opens a <dl>, and each {{glossend}} closes it with </dl>. — SMcCandlish Talk⇒〈°⌊°〉 Contribs. 09:05, 16 February 2012 (UTC)[reply]

You should use {{defn}} for your defenition; nesting : inside {gloss} and {glossend} results in incorrect markup due to double nesting. — Edokter (talk) — 11:25, 16 February 2012 (UTC)[reply]

Sub-terms

I have a need to use sub-terms of a term in a glossary. I have created {{subterm}}and {{subdefn}} for this purpose. I have also created {{glosslink}} and {{glossback}} for the purpose of inserting reference-style backlinks so that readers can easily navigate back to the place in hte article they came from. I would appreciate someone who knows template code to check what I have done for sanity. Spinning Spark 16:12, 26 April 2013 (UTC)[reply]

Glossary_of_cue_sports_terms not working (December 2016)

For some reason this template isn't displaying correctly after the Glossary_of_cue_sports_terms ~646th entry on the page. 24.246.23.7 (talk) 20:56, 21 December 2016 (UTC)[reply]

Seems to be okay now. It was too many parser calls on the page. This was resolved by replacing simpler definition entries with non-templated markup. — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ< 16:37, 13 December 2017 (UTC)[reply]

Semi-protected edit request on 1 August 2023

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please replace all instances of "glycosylated hemoglobin" with "glycated hemoglobin", to use the current standard nomenclature. Thank you! AldoPioManuzio (talk) 21:17, 1 August 2023 (UTC)[reply]

Not done: please provide reliable sources that support the change you want to be made. Xan747 (talk) 22:25, 1 August 2023 (UTC)[reply]

Convert to TemplateStyles: save 6% on PEIS!

I just ran a test by removing inline styles from {{Term}} (in {{Term/sandbox}}, removing class="glossary" from {{Term}} and {{Defn}} (in their respective sandboxes) (letting the CSS cascade work from having it defined in {{Glossary/sandbox}}, and using some simple CSS in Template:Glossary/sandbox/styles.css:

.glossary dt { margin-top: 4em; }
.glossary dt + dt {margin-top: -0.2em; }

Copying Glossary of cue sports terms and Glossary of video game terms into my user space, editing them to use the sandboxed templates, and comparing the PEIS reports, I shaved 6.6% and 6.5%, respectively from the PEIS. Just removing class="glossary" didn't seem to make any difference; I suspect that the gains were from basically eliminating the inline styling in {{Term}} due to processing |multi=.

I'd like to move forward with these simple changes. Normally I wouldn't bother even checking; we should already be using TemplateStyles. But the side effect of this change is that it completely deprecates the need (and ability) of |multi= in {{Term}}. All {{Term}}s that are next to each other will be "closed up", assuming they are multiple terms for the next {{Defn}}. And I think this makes sense: why have a Term without a Defn?

Thoughts? Any compelling reason to keep the behavior of multiple {{Term}}s if |multi=y isn't specified? — sbb (talk) 18:26, 25 May 2024 (UTC)[reply]

Moved from Template talk:Term § Intend to obsolete...

– no need to have convo scattered in multiple templates

Implemented: Not hearing any objections. — sbb (talk) 02:33, 10 June 2024 (UTC)[reply]