Should be empty: <{{ifz|x|y}}{{ifz|x}}{{ifz|}}{{ifz}}>
Should be yy: <{{ifz||y}}{{ifz|2=y}}>
Should be empty: <{{ifdef||y}}{{ifdef|x}}{{ifdef|}}{{ifdef}}>
Should be yy: <{{ifdef|x|y}}{{ifdef|2=y}}>
Should be empty: <{{if|x||z}}{{if|x||}}{{if||y|}}{{if|||}}{{if|1=x|3=z}}{{if||y}}{{if|2=y|3=}}{{if|1=x|3=}}{{if|x|}}{{if|2=|3=}}{{if|1=|3=}}{{if||}}{{if|x}}{{if|}}{{if|2=}}{{if|3=}}{{if}}>
Should be yyyy: <{{if|x|y|z}}{{if|x|y|}}{{if|x|y}}{{if|2=y}}>
Should be zzz: <{{if||y|z}}{{if|||z}}{{if|2=y|3=z}}>
Should be zzz: <{{if|2=|3=z}}{{if|1=|3=z}}{{if|3=z}}>
<div style="display:none;">
<div style="display:none;">
{{ifdef|value|result}} yields result if value isn't blank.
One limitation: {{ifdef|2=results}} ~~> result (but works properly if value is defined and empty).
{{ifndef|value|result}} yields result if value is blank.
{{if|value|THEN|ELSE}} yields THEN if value isn't blank; otherwise it yields ELSE.
One limitation: {{if|2=then}} ~~> then (but works properly if value is defined and empty).
Line 693:
Line 674:
{{
{{
}}
}}
The parameter default feature was introduced before Extension:ParserFunctions. This led to the development of branching methods through the parameter default mechanism.
If no value is passed for the parameter test, then {{{test{{{test|}}}|{{{then}}}}}} resolves to {{{test|{{{then}}}}}} and returns a blank entry (since test is defined as blank). If the parameter "test" is assigned the value "boo", however, {{{test{{{test|}}}|{{{then}}}}}} resolves to {{{testboo|{{{then}}}}}}, and so long as no parameter "testboo" exists, then this will return the value of the parameter "then".
An even older branching technique dates from before the introduction of the parameter default mechanism. It is based on the fact that if in a template call a parameter is assigned a value more than once, the last one counts. This is used in combination with specifying the value of a parameter in a template call, where the name of that parameter depends on a parameter of an outer template. In a call {{a|b=c|{{{d}}}=e}}, template:a uses b=c if b≠{{{d}}} and b=e if b={{{d}}}. See Template:T pdc.
{{ifdef|value|result}} yields result if value isn't blank.
One limitation: {{ifdef|2=results}} ~~> result (but works properly if value is defined and empty).
{{ifndef|value|result}} yields result if value is blank.
{{if|value|THEN|ELSE}} yields THEN if value isn't blank; otherwise it yields ELSE.
One limitation: {{if|2=then}} ~~> then (but works properly if value is defined and empty).
ParserFunctions extension
{{ #if: {{{1}}} | parm1 has content or is undefined | parm1 is defined and empty }}
{{ #if: {{{1|}}} | parm1 has content | parm1 is empty or undefined }}
#ifeq
#expr
#ifexpr
...
Line 730:
Line 680:
<div align="center">{{{1}}}</div>
<div align="center">{{{1}}}</div>
Revision as of 18:50, 7 March 2012
== Start with Heading 2 ==
Inline elements
'''bold'''; or use b or strong or {font-weight:bold}
''italic''; or use i or em or {font-style:italic}
small or {font-size:smaller}
big or {font-size:larger} (invalid in 5)
sup or {vertical-align:super}
sub or {vertical-align:sub}
<font> deprecated, use {font-size:10pt; color:red; font-family:"Courier"}
<span style="color:gray">
<span style="color:white; background:red">
u or ins or {text-decoration:underline} (<u> valid in 5 but not 4 strict; <ins> can also be a block element)
s or del or {text-decoration:line-through} (<s> valid in 5 but not 4 strict; <del> can also be a block element)
code uses {font-family:monospace;} (<tt> invalid in 5)
markup and → entities are still honored
and and and are ignored
var
cite
{{Hint|term|explanation}}
{{Path|/a/path/name}}
Here is [[Internal pagetitle|an internal pagetitle]]: an internal pagetitle. Text immediately suffixing the link will be incorporated into the link text, preface with <nowiki /> to suppress.
Here is [http://www.example.org/ an external link]: an external link. If no link text is supplied: [1]. Omit brackets for http://www.example.org/ (use <nowiki> to suppress). Same server can be specified using {{SERVERNAME}}.
-- ~~~~ gives a signature and timestamp: -- Dubiousjim 10:00, 4 March 2012 (UTC)
Here is one line, followed by <br />
and another line.
Here is <!-- a comment -->.
HR like this
----
Block elements
{{Cmd|a command to try}}
Contents of /path/to/file
{{Cat|/path/to/file|body}}
<nowiki> converts → entities and collapses whitespace,
but ignores all '''wiki''' and <span style="color:green">HTML</span> [[markup]].
HTML's <pre> uses {white-space:pre; font-family:monospace;}
To wrap to screen width, use <pre style="white-space:pre-wrap">
In wiki, one leading space displays as block element, in monospace, doesn't collapse whitespace.
Converts → entities and honors wiki and HTMLmarkup.
? Can contain any inline element except: IMG OBJECT BIG SMALL SUP SUB
In wiki, <pre> displays as block element, in monospace, doesn't collapse whitespace.
Otherwise like <nowiki>: it converts → entities, but ignores '''wiki''' and <span style="color:green">HTML</span> [[markup]].
One leading space plus <nowiki> is same as <pre> (in this case, subsequent lines should not be space-prefixed)
: Simply indented text (on left side only).
This is <blockquote>.
Collapses whitespace, and indents on both sides.
Here is a numbered list item.
Doubly-numbered
Here is a bulleted list item.
Doubly-bulleted
Blank lines, or non-bulleted/numbered lines, end the lists.
In general when pointing to Alpine Linux downloads stick with the Downloads Page, but if you for any reason need to include direct download information, do so by using one of below.
{{Download|alpine}}
For standard
{{Download|alpine-mini}}
For mini
{{DownloadDev|alpine}}
For standard
Download Stable Version Alpine 3.20.3
Download Stable Version Alpine 3.20.3
Download Stable Version Alpine 3.20.3
Links
{{#latestalp:alpine|url}} will give you latest download url for Alpine Linux Standard:
{{#latestalp:alpine|url}}
{{#latestalp:alpine-mini|url}} will give you latest download url for Alpine Linux mini:
{{#latestalp:alpine|url}}
Example:
Start from [{{#latestalp:alpine|url}} Downloading latest Alpine Linux Standard], than continue ...
produces:
Start from [{{#latestalp:alpine|url}} Downloading latest Alpine Linux Standard], than continue ...
explicitly named/numbered args are trimmed, to preserve whitespace have to use implicitly numbered args
will need to escape
= =
| |
[[
]]
{{
}}
Border
{{{1}}}
{{{1}}}
text{{{1}}}
How do I use a template as a signature?
When you look at your preferences, you see a check box for "raw signature." But the field will only take a certain number of characters. What if you want more?
You will need to create two pages, possibly in your userspace.
Create the first page (FIRST PAGE)
Go to your preferences, check "raw signature" and put Template:FIRST PAGE in the signature. Save
Create a second page (SECOND PAGE) (possibly a sub-page of the first)
Go back to the first page (FIRST PAGE) and do Template:SECOND PAGE
Go to the second page (SECOND PAGE) and place the code you wish to have for your signature.
If you don't have this structure, you will still be inserting all your signature code into the raw code wherever your signature is used, because the software will insert "SUBST" in your preferences. You may not mind this, in which case you only need one page. If you want the raw code to only display Template:FIRST PAGE, which looks a lot cleaner, then you need to use the two-page structure.
How to move a page (Wikipedia)
A common example: moving a userspace draft into place. The intended article name is entered without any prefixes.
A move will fail if a page already exists at the target name, unless it is simply a redirect to the present name that has never been modified (check the edit history). The steps for moving a page are as follows:
With the page to be moved displayed, choose the "move" option near the top of the page. In the default Vector skin, this is in a drop-down menu to the right of the screen, after "History" and the "Watchlist" star (see picture). In the Monobook skin, it is a tab at the top. You'll be asked for a new name for the page, and given the option to also move the page's talk page (this box should usually be left checked). Complete the "Reason for move" field (which is like an edit summary). Although filling out the "Reason" field isn't required, you should state a reason for the page move.
When ready, click the move button and, if successful, the page will be renamed to the new title. The old title will become a redirect page, so any links to the old title will still go to the new page. However, note that double redirects (pages that redirect to the original page), will not automatically follow to the new page, so you will have to refer them manually (as explained at How to fix a double redirect and Checking for double redirects). However, if you're an administrator, you can move pages without leaving a redirect behind.
Open the what-links-here for that page (there may be a shortcut link on the page-moved summary screen to let you do this, but the what-links-here link will in any case be in the toolbox, which is near the bottom of the sidebar unless you've customized your skin away from the default Vector).
In the section of that page marked filters, click on the button labeled "Hide links". This will result in the page only showing redirects to the prior name. Open each of the redirect pages (best to do so in new tabs), click edit this page for each one, and change their target to the name of the page to which you have moved the page. Though this is an important cleanup step, if you miss some, they will normally be fixed by a bot shortly afterwards.
If there are more than 50 redirects listed (rare) on the "what links here" page, don't forget to navigate to all parts of the list using the "next 50" or other links available.
Since the article name is reflected in the lead section, that section may need to be updated to be consistent with the new name.
If you moved an article which contains any non-free content (such as images or sound clips), you will need to edit the files' own Wikipedia page, changing the non-free use rationale to refer to the new article title. This is to ensure continued compliance with the non-free content criteria (part 10c), which if not followed, may result in the file's speedy deletion.
Once the page has been moved, this will be recorded in the Move Log and a "move has succeeded" message will be displayed.
Console and Text browsers
Warning: Many console browsers will convert text in edit boxes to the encoding in use by your terminal (or what the browser thinks is your terminal's encoding which may not be the same thing) either at page load time (links and lynx) or when editing a field (w3m). If your terminal encoding is UTF-8 this is not a problem but if your terminal is using a legacy encoding (or is using UTF-8 but your browser thinks it's using a legacy encoding) then this is likely to destroy characters that are not present in the encoding your terminal is using when you save the page after editing.
ELinks
Text only, but renders tables and frames.
Supports HTTP authentication.
Users can use their text editor of choice to edit textarea fields.
Problems with editing UTF-8; set "User-agent identification" (in setup->option manager->protocols->http) to something like "Lynx/elinks/%v (textmode; %s; %t-%b)" to get non-ascii characters as hex codes.
View is enhanced (especially of diffs) by using the following user.css and lua hook file (place in ${HOME}/.elinks and enable via option manager)
user.css:
/*
1. place in ~/.elinks
2. set user css to be "user.css" (no path, relative to ~/.elinks)
3. use document colors: use 1 or 2
/
.diffchange {
color: red;
font-weight: bold;
}
.diff-deletedline {
color: green;
}
.diff-addedline {
color: cyan;
}
a.new {
color: cyan;
font-weight: bold;
}
hooks.lua:
--[[
lua preformatting function
1. lua has to be installed before compiling elinks; if this
is the case, it is used by default
2. place this file in ~/.elinks
this file does:
show and element, make more evident
preformatting for wikipedia pages: since elinks ignores the
class attribute of tags, we move it into the inner
element
]]
testing=false
function pre_format_html_hook (url, html)
-- formatting for
html = string.gsub(html, '<[sS]>', '[S:')
html = string.gsub(html, '</[sS]>', ':S]')
html = string.gsub(html, '<[dD][eE][lL]>', '[DEL:')
html = string.gsub(html, '</[dD][eE][lL]>', ':DEL]')
html = string.gsub(html, '<[iI][nN][sS]>', '[INS:')
html = string.gsub(html, '</[iI][nN][sS]>', ':INS]')
-- diff-addedline and diff-deletedline classes
if string.find(url, "diff=", 1, 1) or testing then
html = string.gsub(html, '
',
'
')
html = string.gsub(html, '
',
'
')
end
return html
end
Links
In old versions the login may be broken. (Try to check referrer sending and cookie handling. If everything fails try to use ELinks, and check the same settings.)
Lynx
Users can use their text editor of choice to edit textarea fields (this feature needs to be enabled at compile time)
Forces wrapping of very long lines in a textarea, which is a problem in editing some articles.
Display options for non-ASCII characters affect editing.
Most tables are rendered as simple text.
Viewing of diffs and redlinks can be improved by adding the following to the lynx.lss configuration file:
