Difference between revisions of "Template:Code/doc"
m (→Included templates) |
m |
||
Line 53: | Line 53: | ||
Templates used inside {{tlc|code}} expose the rendered HTML - this can be useful. | Templates used inside {{tlc|code}} expose the rendered HTML - this can be useful. | ||
− | [[Category:Templates]] | + | [[Category:Templates]][[Category:Semantic markup templates]][[Category:Templates documentation]] |
− | [[Category:Templates documentation]] |
Revision as of 14:38, 11 July 2020
Usage
Wraps a short span of text in <syntaxhighlight>
tags (see Extension SyntaxHighlight). This template should be used for short samples; longer content should use <pre>…</pre>
or <syntaxhighlight>…</syntaxhighlight>
. See Help:Wiki markup for an explanation of what the various tags do.
If the content includes an equals sign “=”, you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}
.
The template uses the <syntaxhighlight>
tag with the attribute inline=1
. This works like the combination of the <code>
and <nowiki>
tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}}
will not render the word “wiki” in bold, and will render the tripled‐single quotes:
some '''wiki''' text
However, {{code|a {{template}} call}}
will still invoke the template:
a {{[[Template:Code/doc|Template:Code/doc]]}} call
Use <nowiki>…</nowiki>
around the template name to avoid this problem:
a '"`UNIQ--nowiki-00000009-QINU`"' call
When used inline with regular text, Template:Tnull generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:
foo '"`UNIQ--nowiki-0000000B-QINU`"' quux.
is well spaced:
- foo
bar baz
quux.
versus:
foo '"`UNIQ--nowiki-0000000E-QINU`"' quux.
which is going to be visually confusing for many:
- foo
bar baz
quux.
because “foo” and “bar
” will seem more closely associated than “bar
” and “baz
”; the width of the space character in a monospaced font is almost always larger than in a proportional font.
Use parameter {{{2}}} (unnamed, as |2=
, or more explicitly as |lang=
) to specify a language for Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though html4strict
and html5
are valid values, as are php
, perl
, css
, javascript
, mysql
and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.
This template does not need to be substituted.
Examples
Markup | Renders as |
---|---|
Lorem {{code|ipsum '''dolor'''}} sit amet
|
Lorem ipsum '''dolor''' sit amet
|
The declaration {{code |lang=cpp |int foo(const std::string& bar, const std::vector<long double*>& baz);}} is the prototype for a function defined later.
|
The declaration int foo(const std::string& bar, const std::vector<long double*>& baz); is the prototype for a function defined later.
|
If the code contains an equals sign, such as {{code |lang=javascript |code=var img = document.getElementsByTagName("img");}}, you must identify the first parameter explicitly as {{{1}}} or {{{code}}}.
|
If the code contains an equals sign, such as var img = document.getElementsByTagName("img"); , you must identify the first parameter explicitly as {{{1}}} or {{{code}}}.
|
Included templates
Embedded templates do not function as expected inside Template:Tlc; for longer, free‐form blocks of code, which can contain templates such as Template:Tlx and Template:Tlx, use <code>…</code>
as a wrapper instead of this template.
Templates used inside Template:Tlc expose the rendered HTML - this can be useful.