Help:Editing: Difference between revisions

From Xenharmonic Wiki
Jump to navigation Jump to search
No edit summary
m Fix double redirect
 
(101 intermediate revisions by 11 users not shown)
Line 1: Line 1:
__FORCETOC__
Wikis should be easy to edit, so most text you add or change will appear as you expect it. But you can do more if you want.
 
[https://wikiindex.org/Xenharmonic_Wiki This wiki] is currently in [https://wikiindex.org/Category:ConfirmEmail ConfirmEmail mode] after the move from Wikispaces to a MediaWiki-based installation (the edit mode may change again some time). For editing or adding information to the wiki, you have to join it. See [[Help:How to get your Xenharmonic Wiki account]] for more!
 
== Using links ==
: ''Shortcut: [[Help: Links]]''
What you always have dreamed of (for your paper notes)—in a wiki it becomes true: fast links!
 
=== Internal links ===
If you enclose a word in double brackets (like <code><nowiki>[[word]]</nowiki></code>), you get an internal link, hopefully to an already existing page&mdash;if not, it appears red, and you just created the opportunity for your co-authors to add the details. If you want a text differing from the link target, you can place it after a pipe symbol: <code><nowiki>[[word|different text]]</nowiki></code>.
 
=== Linking to sections ===
You may link to sections in the same page by using the section title with the prefix <code>#</code>. MediaWiki automatically converts it into a link with the correct anchor identifier. For example to link to the beginning of this section use <code><nowiki>[[#Using links]]</nowiki></code> (rendered as [[#Using links]]) or with changed text <code><nowiki>[[#Using links|top of this section]]</nowiki></code> (rendered as [[#Using links|top of this section]]).
 
=== Interwiki links ===
Links to some wikis are supported by placing a specific wiki alias and a colon (<code>:</code>) to the common in-wiki link syntax: <code><nowiki>[[otherwiki: name there]]</nowiki></code> as a prefix, for example, <code><nowiki>[[Wikipedia: Microtonal music]]</nowiki></code> gets rendered as [[Wikipedia: Microtonal music]]. Although this features is named "interwiki", is also includes some services that are definitively not wiki-like, for instance a google search can as well be embedded in wiki syntax: <code><nowiki>[[Google: 159edo]]</nowiki></code> (rendered as: [[Google: 159edo]]) The sites currently supported are managed in [[Special:Interwiki]]. A space after the prefix doesn't change the effect but looks better.
 
=== External links ===
For external links, simply place the URL into the text, certain protocols (http, https, mailto) will be automatically transformed into links. For alternate text, use single brackets, start with the URL and after a space enter the title, like so <code><nowiki>[http://acid3.acidtests.org the Acid3 test]</nowiki></code> which renders to [http://acid3.acidtests.org the Acid3 test].
 
=== Link text ===
The link text should ideally relate to the link target, try to avoid "[[help:here-links|here]]" links. There is an interesting extension for Firefox, [https://addons.mozilla.org/de/firefox/addon/url2clipboard/ Copy URL To Clipboard], that does automatic formatting of page URL and page title in MediaWiki syntax into the clipboard.
 
=== Redirects ===
Redirects can be [[#Regular redirect|regular]] or [[#Smart redirect|"smart"]] (definition redirect).
 
==== Regular redirect ====
A regular redirect is performed by <code><nowiki>#REDIRECT [[Page title]]</nowiki></code>.
 
Redirects can be used to join alternative names (titles, ({{w|Headword|"lemmata"}}) for the same thing to reduce duplication.
 
Redirects are also useful to directly link into sections (especially if they have the potential to grow to an article in future).
 
Redirects to redirects should be fixed by skipping intermediate targets. The page [[Special:DoubleRedirects]] can be used to detect them.
 
==== Smart redirect ====
A "smart redirect" is a page that has a small definition of a term with a link to a broader presentation of the corresponding area. Don't forget to categorize such a page by placing <code><nowiki>[[Category:Smart redirect]]</nowiki></code> at its end.
 
A smart redirect should not point to another smart redirect.
 
See [[:Category:Smart redirect]] for a list of pages tagged as smart redirect.
 
==== Soft redirect ====
This kind of redirect has been eliminated and should not be used anymore. It was there for a historical reason: to overcome usability issues on Wikispaces (the former wiki platform): Editing redirects was restricted to administrators, so normal users could not expand a redirect page into a full article. (See also [https://yahootuninggroupsultimatebackup.github.io/tuning/topicId_101227.html Yahoo! Tuning Group] for the discussion on the tuning list)
 
== Text formatting ==
=== Emphasis ===
Some typographic markup can easy be added by including the phrase in doubled <code><nowiki>''</nowiki></code> or tripled <code><nowiki>'''</nowiki></code> (apostrophe chars):
 
* '''Bold''' using <code><nowiki>'''bold'''</nowiki></code>
* ''Italic'' using <code><nowiki>''italic''</nowiki></code>
* '''''Bold italic''''' using <code><nowiki>'''''bold italic'''''</nowiki></code>
 
=== Preformatted text ===
==== Code ====
<code><<nowiki />code></code> can be used to include small snippets of source code, variable names, or {{w|regex}}es within a line of normal text. All Wiki markup within is interpreted as markup except for text in <code>&lt;nowiki&gt;</code> tags.
 
==== Pre ====
<code><<nowiki />pre></code> tags define preformatted text that is displayed in a monospace font and enclosed in a dashed box. It doubles as both a parser tag and an HTML tag, since the parser will escape all HTML-like and wiki markup tags and preserve spaces and line breaks, but HTML elements are parsed.
 
For example:
 
<syntaxhighlight lang="wikitext">
<pre>
<!-- Comment -->
 
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>
</syntaxhighlight>
 
gives
 
<pre>
<!-- Comment -->
 
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>
 
It is also possible to use Wiki markup within <code><<nowiki />pre></code> tags, and have it actually be interpreted as markup instead of being escaped. This can be done by inserting an <code>includeonly</code> directive in the opening tag, as <code style="white-space: nowrap;">&lt;includeonly /&gt;</code> or (as seen on Wikipedia and many other sites) <code style="white-space: nowrap;">&lt;includeonly&gt;&lt;/includeonly&gt;</code>, as follows:
 
<syntaxhighlight lang="wikitext">
<pre<includeonly />>
<!-- Comment -->
 
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>
</syntaxhighlight>
 
gives
 
<pre<includeonly />>
<!-- Comment -->
 
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>


Wikis should be easy to edit, so most text you add or change will appear as you expect it. But you can do more if you want.
The <code><<nowiki />pre></code> tag also accepts styling, just like other HTML elements. Here, if you use the aformentioned <code>includeonly</code> directive, the styling should come after the directive:
<syntaxhighlight lang="wikitext">
<pre<includeonly /> style="color: blue;">
<!-- Comment -->


This wiki is in [http://wikiindex.org/Category:OpenEdit open-edit mode] (except during phases of spam or vandalism). If you want your name (or nick) to appear in the histories, you should create a Xenwiki account and join this wiki. (see [[How_to_Get_Your_Xenwiki_Account|How to Get Your Xenwiki Account]])
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>
</syntaxhighlight>


==Using links==
gives
What you always have dreamed of (for your paper notes) - in a wiki it becomes true: fast links!


If you enclose a word in double brackets (like <code><nowiki>[[word]]</nowiki></code>), you get a link, hopefully to an already existing page - if not, it appears red, and you just created the opportunity for your co-authors to add the details. If you want a text differing from the link target, you can place it after a pipe symbol <tt>[[word|different text]]</tt>. The same syntax can be used for external links like <tt>[http://en.wikipedia.org|English Wikipedia]</tt> for a link to the [http://en.wikipedia.org English Wikipedia].
<pre<includeonly /> style="color: blue;">
<!-- Comment -->


===Link text===
[[Wiki]] markup &amp; '''bold''' ''italic'' text
''tbd''
</pre>


The link text should relate to the link target, don't use "here".
==== Syntax highlighting ====
[[mw:extension:SyntaxHighlight|Syntax highlighting]] is a feature to display source code in different colors and fonts to indicate the structure to readers. Wrap the desired code between <code><<nowiki />syntaxhighlight></code> tags and input the desired programming language using the <code>lang</code> parameter in the opening tag. Unlike in <code><<nowiki />code></code> and <code><<nowiki />pre></code> tags, everything is escaped.


===Redirects===
For example:
There are 3 types of redirects: soft redirect, regular redirect and hard redirect.


A "soft redirect" or "smart redirect" is just an ordinary page with the text "See XYZ.", where XYZ is a link to the target of the smart redirect. A smart redirect should not point to another smart redirect - if you see this you should fix it by shortcutting past the second one and making the first redirect point directly to the ultimate target.
{{#tag: syntaxhighlight
|{{^(}}syntaxhighlight lang="wikitext"{{)^}}
{{^(}}!-- Comment --{{)^}}


A regular redirect is performed by <code><nowiki>#REDIRECT [[Page title]]</nowiki></code>. A double redirect should be fixed by the same method as above, or by replacing it with a hard redirect. Regular redirects did not exist in <code>wikispaces</code>. This kind of redirect displays a small information message when it was used to display the current page.
[[Wiki]] markup &amp; '''bold''' ''italic'' text
{{^(}}/syntaxhighlight{{)^}}
|lang = wikitext
}}


Real or "hard" redirects directly go to the target page without a notice of redirect. Therefore, they should only be used in the case of simple misspellings or alternate spellings. The rule is that if anyone might ever want to flesh the redirect out into its own article, it should not be a hard redirect. Hard redirects can be chained with no problem, which is why they're still appropriate to use for misspellings. The code for a hard redirect in MediaWiki is <code><nowiki>#REDIRECT [[:en:Page title]]</nowiki></code>. Hard redirects worked somewhat differently in <code>wikispaces</code>; only admins could create or change them, and they could not redirect to a section.
gives


see also
<syntaxhighlight lang="wikitext">
<!-- Comment -->


<ul><li>http://groups.yahoo.com/neo/groups/tuning/conversations/topics/101227 - under discussion on the [[tuning_list|tuning list]]</li><li>[[:Category:soft redirect|list of pages tagged as soft redirect]] - pages that contain only see <tt>[[</tt><nowiki>''some other page''</nowiki><tt>]]</tt> (be cautious with other tags on these)</li><li>[[:Category:smart redirect|list of pages tagged as smart redirect]] - pages that have more information (a small definition, classification etc.)</li></ul>
[[Wiki]] markup &amp; '''bold''' ''italic'' text
</syntaxhighlight>


==Page layout==
=== Lists ===
: ''See [[Help: List]] for advanced use cases.''
There are tree basic types of lists in HTML that are supported in MediaWiki markup: [[#unordered|unordered]] (or "bulleted") lists, [[#numbered|numbered]] lists, [[#description|description]] lists. Each type of lists can be created within wiki source code by just indicating the items at the beginning of the line (the list is automatically built around them). Each item has to start on a new line.


===Emphasis===
==== Unordered ====
Some typographic markup can easy be added by including the phrase in doubled '' (apostrophe) or ''' (apostrophe) chars:
Unordered list items are marked by <code>*</code> (asterisk):


<ul><li>''italic'' using <nowiki>''italic''</nowiki></li><li>'''bold''' using <nowiki>'''bold'''</nowiki></li><li>'''''bold italic''''' using <nowiki>'''''bold italic'''''</nowiki></li></ul>
* Coffee
* Wine
* Milk


===Lists===
==== Numbered ====
Numbered list items are marked by <code>#</code> (number sign):


You can create bulleted lists by one or more * (asterisk) chars at the beginning of the line:
# Coffee
# Wine
# Milk


<ul><li>first level<ul><li>second level</li><li>second level</li></ul></li><li>first level</li></ul>
==== Description ====
Description items are marked by <code>;</code> (semicolon) for term and <code>:</code> (colon) for the description, where <code>;</code> bolds the entire line and <code>:</code> indents the line:


You can create numbered lists by one or more # (number sign) at the beginning of the line:
; Coffee
: A brewed drink prepared from roasted coffee beans. (from: ''[[Wikipedia: Coffee]])


<ol><li>first level<ol><li>second level</li><li>second level</li></ol></li><li>first level</li></ol>
; Wine
: An alcoholic beverage made from fermented grapes. (from: ''[[Wikipedia: Wine]]'')


...and you can of course mix both, if you know what you're doing ;)
; Milk
: A white liquid nutrient-rich food produced by the mammary glands of mammals. (from: ''[[Wikipedia: Milk]]'')


<ol><li>first level<ul><li>second level</li></ul><ol><li>second level</li></ol></li></ol><ul><li>first level</li></ul>
==== Combined List Styles ====
# Morning
#* Coffee
#* Milk
# Evening
#* Coffee
#* Wine


===Tables===
=== Tables ===
You can add tables with wikitable:
: ''For advanced examples, see [[Help:Table]]''


You can add tables to wiki pages:
{| class="wikitable"
|-
! You write<br />in [[Help:Wikitext editor|wikitext]]
| style="border-right: none;" |
<pre>
{| class="wikitable"
{| class="wikitable"
|+ Caption text
|-
! Head A
! Head B
! Head C
|-
|-
! | what you want for the cell
| Cell A1
! | what you do to get it
| Cell B1
| Cell C1
|-
|-
| | left aligned text
| Cell A2
| | nothing to do
| Cell B2
| Cell C2
|-
|-
| style="text-align:center;" | centered text
| Cell A3
| | equals sign (=) immediately after the opening double pipe
| Cell B3
| Cell C3
|-
|-
| style="text-align:right;" | right aligned
| Cell A4
| | greater-than sign (&gt;) immediately after the opening double pipe
| Cell B4
| Cell C4
|}
</pre>
| style="border-left: none; border-right: none;" | or
| style="border-left: none;" |
<pre>
{| class="wikitable"
|+ Caption text
|-
! Head A !! Head B !! Head C
|-
| Cell A1 || Cell B1 || Cell C1
|-
| Cell A2 || Cell B2 || Cell C2
|-
| Cell A3 || Cell B3 || Cell C3
|-
| Cell A4 || Cell B4 || Cell C4
|}
</pre>
|-
|-
! | headline style
! You get<br />(rendered)
| | title (~) immediately after the opening double pipe
<!-- Begin result -->
| colspan="3" | {{(!}} class{{=}}"wikitable" style{{=}}"margin: 20px auto 20px auto;"
{{!+}} Caption text
{{!-}}
! Head A !! Head B !! Head C
{{!-}}
{{!}} Cell A1 {{!!}} Cell B1 {{!!}} Cell C1
{{!-}}
{{!}} Cell A2 {{!!}} Cell B2 {{!!}} Cell C2
{{!-}}
{{!}} Cell A3 {{!!}} Cell B3 {{!!}} Cell C3
{{!-}}
{{!}} Cell A4 {{!!}} Cell B4 {{!!}} Cell C4
{{!)}}
<!-- End result -->
|}
|}


===Images===
You can also copy some cells from a spreadsheet and paste them into the [[mw:Extension:VisualEditor|visual editor]], and a table will automatically be created. Though, users should be aware that the resulting Wiki markup generated by the visual editor is often poorly formatted (e.g. without spaces that would otherwise make it easier to read).
Inserting a JPEG or PNG image is pretty straightforward - when using the visual page editor click the "File" button and upload the image. Or in Wikitext, use <tt>[[image:filename]]</tt>. SVG images are possible but require a bit more work; see [[SVG_images_on_wiki_pages|SVG images on wiki pages]] for details.
 
==== Horizontal alignment of column content ====
Text alignment can be an issue. The table default is cell text being left-alignened, but decimal numbers usually are right-aligned and common fractions center-aligned.
 
You may add inline [[CSS]] styling to '''each cell''' of the table (i.e. <code>style="text-align: right;"</code>), but this is a lot of work, makes the wiki markup confusing, and also makes pages really big which slows down loading.
 
It's now (by June 2020) possible to define the column alignment '''once in the table header'''. This can be done by adding further classes to the <code>class="wikitable"</code> statement.
 
For example, write <code>class="wikitable right-1 left-5 center-all"</code> to align the cell text to
* '''right''' in the '''1'''st column,
* '''left''' in the '''5'''th column, and
* '''center''' in '''all''' other columns.
 
=== Images ===
Inserting a JPEG, GIF, or PNG image is pretty straightforward when using the visual page editor, click the "File" button and upload the image. Or in Wikitext, use <code><nowiki>[[image:filename]]</nowiki></code> or <code><nowiki>[[file:filename]]</nowiki></code>. Also SVG images are supported (<code><nowiki>[[file:some.svg]]</nowiki></code>), they are automatically transformed into PNG images by the MediaWiki software, because not all Browsers come with native SVG support. A possible problem can arise when the image uses fonts that are not available on the wiki server. To prevent such errors, you can transform text into graphic objects before uploading the image here.
 
=== Maths formulas ===
… can be used {{w|Help:Displaying a formula|like in Wikipedia}}. For inline math, start it with <code><nowiki><math></nowiki></code> and end it with <code><nowiki></math></nowiki></code>. For example: <math>V =\frac{4}{3} \pi r^3</math>. For display-style math, open and close the formulas with both <code><nowiki>$$</nowiki></code>; this will render it centered in a new line.
 
Here is a browser-based formula editor that may be helpful: [https://editor.codecogs.com/ Equation Editor]
 
=== Table of contents ===
Place <code><nowiki>__TOC__</nowiki></code> where you wish to place the table of contents, mostly this will be at the top of the page.
 
=== Notes and references ===
A reference mark is added by <code><nowiki><ref></nowiki></code> and <code><nowiki></ref></nowiki></code> parenthesising the reference text.
 
The reference texts are shown in the bottom of the article by default; you can optionally insert <code><nowiki><references/></nowiki></code> where you wish to show them.
 
For footnotes, the practice is similar. Insert the text in the note itself between <code><nowiki><ref group="note"></nowiki></code> and <code><nowiki></ref></nowiki></code> and insert <code><nowiki><references group="note" /></nowiki></code> where you wish to show them.
 
Here is an example for a page with footnotes and references:
<pre>
== Notes ==
<references group="note" />
 
== References ==
<references />
</pre>
 
References can be reused throughout an article by giving then names. The first time this reference is used, type the full text of the note or reference between the tags (<code><nowiki><ref name="example1">Note 1</ref></nowiki></code>). If you want to reference <code>example1</code> multiple times in the same page, type <code><nowiki><ref name="example1" /></nowiki></code> on all subsequent instances.
 
== Article structure ==
* Articles should start with an introduction (summary, synopsis) that helps to get a basic understanding what it is about. Don't introduce another heading for the introduction – it's already provided by the h1 heading of the lemma itself.
* After this section (about one to five sentences), subheadings may follow to deepen the concept.
* The end of the article is typically for see-also suggestions and external links.
* After the last section (in wikitext: separated by an empty line) follow [[#categories|categories]] (in wikitext: each on a separate line).


===Maths formulas===
== Subpages ==
...can be used [http://en.wikipedia.org/wiki/Help:Displaying_a_formula like in the Wikipedia] but the enclosing tags (<tt>[[math]]</tt> - the same for begin and end) differ. Take care: using the math tags you'll break paragraphs. 
{{Wikipedia|Wikipedia: Subpages}}


<math>V =\frac{4}{3} \pi r^3</math>
'''Subpages''' are pages whose title contains one or more slashes ("/"). In general, every subpage includes a breadcrumb link at the top, allowing the reader to navigate to the parent page (and further if there are multiple levels of subpages). However, the subpage feature is disabled in the main namespace, mainly to prevent rational interval pages (e.g. [[3/2]]) from incorrectly including a breadcrumb link to a nonexistent page.


Here is a browser-based formula editor that may be helpful: http://www.codecogs.com/latex/eqneditor.php
Subpages can nonetheless be used in the main namespace in certain circumstances, such as:
* Splitting large sections; e.g. [[Color notation/Temperament names]]
* Splitting large tables or lists; e.g. [[17edo/Music]]
* Splitting personal approaches; e.g. [[22edo/Eliora's approach]]


===Table of contents===
In subpages, a link to the main page should be added manually, either in the page's first sentence, in a hatnote using [[Template:Main]], or by putting {{tlx|breadcrumb}} at the top of the page.
Place <tt>[[toc]]</tt> on top of the page, or - if you prefer flat tocs - use <tt>[[toc|flat]]</tt>


''Note: when using flat tocs, a horizontal ruler <tt>----</tt> and an empty line may improve the layout.''
== Categories ==
Categories all serve different purposes: sometimes they say what something is or the context in which it belongs ([[:Category: Temperaments]], [[:Category: Intervals]]). Sometimes they are used for annotation purposes ([[:Category: Todo:add examples]]), etc. All these forms have in common is that they can combine wiki pages in a way that is independent of their authors.


==Social aspects==
A category may have its own content (and category)
In Wikispaces wikis, you can use tags and discussions. In MediaWiki we instead have categories and talk pages.
: ''See [https://en.xen.wiki/w/Special:AllPages?from=&to=&namespace=14 Pages in the namespace '''Category''']''
or not yet (despite being used to categorize other pages):
: ''See [[Special: WantedCategories]]''


If you want to discuss the wiki itself, do it on the page [[wikifuture|wikifuture]].
Some more examples:


===Categories===
* [[:Category: Todo:add definition]] – here a term needs to be defined
Categories all serve different purposes: sometimes they say what something is or the context in which it belongs ([[tag/view/edo|edo]], [[tag/view/interval|interval]]). Sometimes they are used for annotation purposes ([[tag/view/todo:reduce_mathslang|todo:reduce mathslang]]), etc. All these forms have in common is that they can combine wiki pages in a way that is independent of their authors.
* [[:Category: Todo]] – category of categories that flag articles


You can look at the [[tag/list|list of used categories]] or link to particular categories using the prefix <tt>https://en.xen.wiki/w/Category:</tt>
== Social aspects ==
In this wiki, you can use talk pages and [[user talk]] pages.  


Some tag examples:
If you want to discuss the wiki itself, do it on the page [[wikifuture]].


<ul><li><span style="text-decoration: line-through;">[[tag/view/orphan_page|orphan page]]</span> - pages without ingoing links -&gt; [[space/pagelist/orphaned|http://xenharmonic.wikispaces.com/space/pagelist/orphaned]]</li><li>[[tag/view/todo:add_definition|todo:add definition]] - here a term needs to be defined</li></ul>
=== Discussion ===
Discussion pages are provided to each content page. Please keep in mind that the email notification to people who are observing the page cannot be taken back!


===Discussion===
Sometimes you will wait forever for a reply because nobody monitors the page or topic. In this case you should find out who is most familiar with the topic and ask that person directly. You can check the history of pages for its authors. Another approach is to ask questions on further media, examples are listed on the page [[General discussion]].
Discussion pages are provided to each content page. Sadly there is no preview function on this wiki, but if you create something entirely wrong, you can delete your post. Please keep in mind that the email notification to people who are monitoring the topic or wiki cannot be taken back!


Sometimes you will wait forever for a reply because nobody monitors the page or topic. In this case you should find out who is most familiar with the topic and ask that person directly. You can check the history of pages for its authors. Another approach is to ask questions on further media, examples are listed on the page [[GeneralDiscussion|GeneralDiscussion]].
Sign your contributions to a Talk page by using two hyphens (<code>--</code>) (or an em dash (<code>—</code>), if you like) and four tildes (<code><nowiki>~~~~</nowiki></code>); the latter will be converted to your username and a time/date stamp upon submission.


==Links==
== See also ==
<ul><li>[http://help.wikispaces.com/home http://help.wikispaces.com]</li><li>http://help.wikispaces.com/Wikitext</li><li>[http://help.wikispaces.com/Editing_a_Page http://help.wikispaces.com/Editing+a+Page]</li><li>[http://help.wikispaces.com/Wikitext-Contents_of_Another_Wiki_Page-Supported_includes http://help.wikispaces.com/Wikitext#Contents%20of%20Another%20Wiki%20Page-Supported%20includes] - page contents can also be included into pages</li><li>[http://helpcenter.wikispaces.com/customer/en/portal/topics/768797-miscellaneous/articles Wikispaces | Miscellaneous]</li></ul>
* [[Xenharmonic Wiki: Conventions]]
* [[Xenharmonic Wiki: Article guidelines]]
* [[Help: Help]]
* [[Help: Visual editor]] – especially helpful for new users, that's why it's enabled by default


==See also==
[[Category:Help]]
<ul><li>[[WebDAV_Help|WebDAV Help]]</li></ul>     
[[Category:help]]
[[Category:syntax]]
[[Category:wiki_help]]

Latest revision as of 15:49, 6 December 2025

Wikis should be easy to edit, so most text you add or change will appear as you expect it. But you can do more if you want.

This wiki is currently in ConfirmEmail mode after the move from Wikispaces to a MediaWiki-based installation (the edit mode may change again some time). For editing or adding information to the wiki, you have to join it. See Help:How to get your Xenharmonic Wiki account for more!

Using links

Shortcut: Help: Links

What you always have dreamed of (for your paper notes)—in a wiki it becomes true: fast links!

Internal links

If you enclose a word in double brackets (like [[word]]), you get an internal link, hopefully to an already existing page—if not, it appears red, and you just created the opportunity for your co-authors to add the details. If you want a text differing from the link target, you can place it after a pipe symbol: [[word|different text]].

Linking to sections

You may link to sections in the same page by using the section title with the prefix #. MediaWiki automatically converts it into a link with the correct anchor identifier. For example to link to the beginning of this section use [[#Using links]] (rendered as #Using links) or with changed text [[#Using links|top of this section]] (rendered as top of this section).

Interwiki links

Links to some wikis are supported by placing a specific wiki alias and a colon (:) to the common in-wiki link syntax: [[otherwiki: name there]] as a prefix, for example, [[Wikipedia: Microtonal music]] gets rendered as Wikipedia: Microtonal music. Although this features is named "interwiki", is also includes some services that are definitively not wiki-like, for instance a google search can as well be embedded in wiki syntax: [[Google: 159edo]] (rendered as: Google: 159edo) The sites currently supported are managed in Special:Interwiki. A space after the prefix doesn't change the effect but looks better.

External links

For external links, simply place the URL into the text, certain protocols (http, https, mailto) will be automatically transformed into links. For alternate text, use single brackets, start with the URL and after a space enter the title, like so [http://acid3.acidtests.org the Acid3 test] which renders to the Acid3 test.

Link text

The link text should ideally relate to the link target, try to avoid "here" links. There is an interesting extension for Firefox, Copy URL To Clipboard, that does automatic formatting of page URL and page title in MediaWiki syntax into the clipboard.

Redirects

Redirects can be regular or "smart" (definition redirect).

Regular redirect

A regular redirect is performed by #REDIRECT [[Page title]].

Redirects can be used to join alternative names (titles, ("lemmata") for the same thing to reduce duplication.

Redirects are also useful to directly link into sections (especially if they have the potential to grow to an article in future).

Redirects to redirects should be fixed by skipping intermediate targets. The page Special:DoubleRedirects can be used to detect them.

Smart redirect

A "smart redirect" is a page that has a small definition of a term with a link to a broader presentation of the corresponding area. Don't forget to categorize such a page by placing [[Category:Smart redirect]] at its end.

A smart redirect should not point to another smart redirect.

See Category:Smart redirect for a list of pages tagged as smart redirect.

Soft redirect

This kind of redirect has been eliminated and should not be used anymore. It was there for a historical reason: to overcome usability issues on Wikispaces (the former wiki platform): Editing redirects was restricted to administrators, so normal users could not expand a redirect page into a full article. (See also Yahoo! Tuning Group for the discussion on the tuning list)

Text formatting

Emphasis

Some typographic markup can easy be added by including the phrase in doubled '' or tripled ''' (apostrophe chars):

  • Bold using '''bold'''
  • Italic using ''italic''
  • Bold italic using '''''bold italic'''''

Preformatted text

Code

<code> can be used to include small snippets of source code, variable names, or regexes within a line of normal text. All Wiki markup within is interpreted as markup except for text in <nowiki> tags.

Pre

<pre> tags define preformatted text that is displayed in a monospace font and enclosed in a dashed box. It doubles as both a parser tag and an HTML tag, since the parser will escape all HTML-like and wiki markup tags and preserve spaces and line breaks, but HTML elements are parsed.

For example:

<pre>
<!-- Comment -->

[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>

gives

<!-- Comment -->

[[Wiki]] markup & '''bold''' ''italic'' text

It is also possible to use Wiki markup within <pre> tags, and have it actually be interpreted as markup instead of being escaped. This can be done by inserting an includeonly directive in the opening tag, as <includeonly /> or (as seen on Wikipedia and many other sites) <includeonly></includeonly>, as follows:

<pre<includeonly />>
<!-- Comment -->

[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>

gives


Wiki markup & bold italic text

The <pre> tag also accepts styling, just like other HTML elements. Here, if you use the aformentioned includeonly directive, the styling should come after the directive:

<pre<includeonly /> style="color: blue;">
<!-- Comment -->

[[Wiki]] markup &amp; '''bold''' ''italic'' text
</pre>

gives


Wiki markup & bold italic text

Syntax highlighting

Syntax highlighting is a feature to display source code in different colors and fonts to indicate the structure to readers. Wrap the desired code between <syntaxhighlight> tags and input the desired programming language using the lang parameter in the opening tag. Unlike in <code> and <pre> tags, everything is escaped.

For example:

<syntaxhighlight lang="wikitext">
<!-- Comment -->

[[Wiki]] markup &amp; '''bold''' ''italic'' text
</syntaxhighlight>

gives

<!-- Comment -->

[[Wiki]] markup &amp; '''bold''' ''italic'' text

Lists

See Help: List for advanced use cases.

There are tree basic types of lists in HTML that are supported in MediaWiki markup: unordered (or "bulleted") lists, numbered lists, description lists. Each type of lists can be created within wiki source code by just indicating the items at the beginning of the line (the list is automatically built around them). Each item has to start on a new line.

Unordered

Unordered list items are marked by * (asterisk):

  • Coffee
  • Wine
  • Milk

Numbered

Numbered list items are marked by # (number sign):

  1. Coffee
  2. Wine
  3. Milk

Description

Description items are marked by ; (semicolon) for term and : (colon) for the description, where ; bolds the entire line and : indents the line:

Coffee
A brewed drink prepared from roasted coffee beans. (from: Wikipedia: Coffee)
Wine
An alcoholic beverage made from fermented grapes. (from: Wikipedia: Wine)
Milk
A white liquid nutrient-rich food produced by the mammary glands of mammals. (from: Wikipedia: Milk)

Combined List Styles

  1. Morning
    • Coffee
    • Milk
  2. Evening
    • Coffee
    • Wine

Tables

For advanced examples, see Help:Table

You can add tables to wiki pages:

You write
in wikitext
{| class="wikitable"
|+ Caption text
|-
! Head A
! Head B
! Head C
|-
| Cell A1
| Cell B1
| Cell C1
|-
| Cell A2
| Cell B2
| Cell C2
|-
| Cell A3
| Cell B3
| Cell C3
|-
| Cell A4
| Cell B4
| Cell C4
|}
or
{| class="wikitable"
|+ Caption text
|-
! Head A !! Head B !! Head C
|-
| Cell A1 || Cell B1 || Cell C1
|-
| Cell A2 || Cell B2 || Cell C2
|-
| Cell A3 || Cell B3 || Cell C3
|-
| Cell A4 || Cell B4 || Cell C4
|}
You get
(rendered)
Caption text
Head A Head B Head C
Cell A1 Cell B1 Cell C1
Cell A2 Cell B2 Cell C2
Cell A3 Cell B3 Cell C3
Cell A4 Cell B4 Cell C4

You can also copy some cells from a spreadsheet and paste them into the visual editor, and a table will automatically be created. Though, users should be aware that the resulting Wiki markup generated by the visual editor is often poorly formatted (e.g. without spaces that would otherwise make it easier to read).

Horizontal alignment of column content

Text alignment can be an issue. The table default is cell text being left-alignened, but decimal numbers usually are right-aligned and common fractions center-aligned.

You may add inline CSS styling to each cell of the table (i.e. style="text-align: right;"), but this is a lot of work, makes the wiki markup confusing, and also makes pages really big which slows down loading.

It's now (by June 2020) possible to define the column alignment once in the table header. This can be done by adding further classes to the class="wikitable" statement.

For example, write class="wikitable right-1 left-5 center-all" to align the cell text to

  • right in the 1st column,
  • left in the 5th column, and
  • center in all other columns.

Images

Inserting a JPEG, GIF, or PNG image is pretty straightforward – when using the visual page editor, click the "File" button and upload the image. Or in Wikitext, use [[image:filename]] or [[file:filename]]. Also SVG images are supported ([[file:some.svg]]), they are automatically transformed into PNG images by the MediaWiki software, because not all Browsers come with native SVG support. A possible problem can arise when the image uses fonts that are not available on the wiki server. To prevent such errors, you can transform text into graphic objects before uploading the image here.

Maths formulas

… can be used like in Wikipedia. For inline math, start it with <math> and end it with </math>. For example: [math]\displaystyle{ V =\frac{4}{3} \pi r^3 }[/math]. For display-style math, open and close the formulas with both $$; this will render it centered in a new line.

Here is a browser-based formula editor that may be helpful: Equation Editor

Table of contents

Place __TOC__ where you wish to place the table of contents, mostly this will be at the top of the page.

Notes and references

A reference mark is added by <ref> and </ref> parenthesising the reference text.

The reference texts are shown in the bottom of the article by default; you can optionally insert <references/> where you wish to show them.

For footnotes, the practice is similar. Insert the text in the note itself between <ref group="note"> and </ref> and insert <references group="note" /> where you wish to show them.

Here is an example for a page with footnotes and references:

== Notes ==
<references group="note" />

== References ==
<references />

References can be reused throughout an article by giving then names. The first time this reference is used, type the full text of the note or reference between the tags (<ref name="example1">Note 1</ref>). If you want to reference example1 multiple times in the same page, type <ref name="example1" /> on all subsequent instances.

Article structure

  • Articles should start with an introduction (summary, synopsis) that helps to get a basic understanding what it is about. Don't introduce another heading for the introduction – it's already provided by the h1 heading of the lemma itself.
  • After this section (about one to five sentences), subheadings may follow to deepen the concept.
  • The end of the article is typically for see-also suggestions and external links.
  • After the last section (in wikitext: separated by an empty line) follow categories (in wikitext: each on a separate line).

Subpages

English Wikipedia has an article on:

Subpages are pages whose title contains one or more slashes ("/"). In general, every subpage includes a breadcrumb link at the top, allowing the reader to navigate to the parent page (and further if there are multiple levels of subpages). However, the subpage feature is disabled in the main namespace, mainly to prevent rational interval pages (e.g. 3/2) from incorrectly including a breadcrumb link to a nonexistent page.

Subpages can nonetheless be used in the main namespace in certain circumstances, such as:

In subpages, a link to the main page should be added manually, either in the page's first sentence, in a hatnote using Template:Main, or by putting {{breadcrumb}} at the top of the page.

Categories

Categories all serve different purposes: sometimes they say what something is or the context in which it belongs (Category: Temperaments, Category: Intervals). Sometimes they are used for annotation purposes (Category: Todo:add examples), etc. All these forms have in common is that they can combine wiki pages in a way that is independent of their authors.

A category may have its own content (and category)

See Pages in the namespace Category

or not yet (despite being used to categorize other pages):

See Special: WantedCategories

Some more examples:

Social aspects

In this wiki, you can use talk pages and user talk pages.

If you want to discuss the wiki itself, do it on the page wikifuture.

Discussion

Discussion pages are provided to each content page. Please keep in mind that the email notification to people who are observing the page cannot be taken back!

Sometimes you will wait forever for a reply because nobody monitors the page or topic. In this case you should find out who is most familiar with the topic and ask that person directly. You can check the history of pages for its authors. Another approach is to ask questions on further media, examples are listed on the page General discussion.

Sign your contributions to a Talk page by using two hyphens (--) (or an em dash (), if you like) and four tildes (~~~~); the latter will be converted to your username and a time/date stamp upon submission.

See also