[[Wikipedia:Featured picture candidates/Glossary#{{{1}}}|{{{1}}}]]
The {{FPCgloss}}
template is used to easily create a link from a word or phrase in any article to a corresponding entry in the Wikipedia:Featured picture candidates/Glossary, a stand-alone glossary list article. Example: focus stacking.
Using {{FPCgloss|focus stacking}}
is a more concise way of doing [[Wikipedia:Featured picture candidates/Glossary#focus stacking|focus stacking]]
. and provides a mouse-hover tooltip indicating that the link goes to a glossary entry (this does not interfere with page previews or navigation popups). The template takes one or two parameters, as detail below.
The template makes proper use of the <dfn>
HTML element (as documented at the parent meta-template, {{glossary link}}
). For linking between entries inside the glossary itself, use {{gli}}
({{glossary link internal}}
), which does not use that element (it is reserved for term entries in the glossary). It can also be used in other articles where the same term is linked twice because of article length (<dfn>
should only be used once per term per page, as it means "this is the defining instance of this term on this page").
Usage
editSyntax: From an article to the glossary:
{{FPCgloss|glossary term|article text}}
If the text being linked matches the name of (or an anchor present at) the glossary entry, regardless of upper or lower case, you can simply do:
{{FPCgloss|article text that is a glossary term}}
It will also handle suffixes like plurals, etc., added onto it:
{{FPCgloss|article text that is a glossary term}}ized
From inside Wikipedia:Featured picture candidates/Glossary itself, to link from one entry to another:
{{gli|glossary term|article text}}
Parameters
editThe first parameter is the name of the term to be linked to in Wikipedia:Featured picture candidates/Glossary (or any alias of the term as defined in the glossary with {{anchor}}
or {{vanchor}}
). {{FPCgloss|glossary term}}
displays as glossary term. This will be automatically converted to all-lowercase (as is done by the {{Term}}
template being linked to in the glossary); thus {{FPCgloss|glossary term|article text}}
and {{FPCgloss|Glossary term|article text}}
and {{FPCgloss|Glossary Term|article text}}
are functionally equivalent. For cases where this might not be desirable, see |lc=no
, below.
The second parameter is the visible text string to be wikilinked from in the article ({{FPCgloss|glossary term|article text}}
displays as: article text). This parameter is optional, used when this displayed text needs to be different from what is put in the first parmeter (which is displayed by default if the second parameter is absent): {{FPCgloss|glossary term|glossary term}}
and {{FPCgloss|glossary term}}
are functionally equivalent, so prefer the shorter version. Using a capitalized {{FPCgloss|Glossary term}}
will display as: Glossary term. But its link goes to the same lowercase "glossary term" target as {{FPCgloss|glossary term}}
.
The parameter |lc=no
(or any other value like |lc=n
, |lc=false
) can be used to turn off the automatic lower-casing of the link target, for a case in which the glossary entry is upper-case and someone doesn't want to link to a lower-cased anchor for it (e.g. for a proper name). The upper case anchor must exist in the glossary's code.
Limitations
editThe first parameter cannot contain wikimarkup, link code, or anything else other than plain text; it is part of a URL.
The second parameter may contain wikimarkup, but cannot contain link code; it is the second half of a piped wikilink.
Examples
edit- One parameter:
The only technical flaw I can see is some {{FPCgloss|blown}} highlights, but that's not too serious.
- The only technical flaw I can see is some blown highlights, but that's not too serious.
- Two parameters:
The only technical flaw I can see is some {{FPCgloss|blown|highlight blow}}, but that's not too serious.
- The only technical flaw I can see is some highlight blow, but that's not too serious.
- Add a suffix (works exactly the same as with a regular wilklink like
[[dog]]s
): The only technical flaw I can see is some {{FPCgloss|blown}}out highlights, but that's not too serious.
- The only technical flaw I can see is some blownout highlights, but that's not too serious.
- Capitalize displayed term:
{{FPCgloss|Blown}} highlights are the only technical flaw I can see, but that's not too serious.
- Blown highlights are the only technical flaw I can see, but that's not too serious.
- Link to uppercase glossary term explicitly:
This might be fixable in {{FPCgloss|GIMP|lc=no}}.
- This might be fixable in GIMP.
- (This is not necessary, but can be done if you prefer it. The glossary will require an uppercase term anchor at that entry if you do so.)