Xenharmonic Wiki - User contributions [en]

Category:Hidden categories

2026-06-08T03:31:44Z

Fredg999: This page should itself be a hidden category

__HIDDENCAT__
Hidden categories are not visible for normal readers of the wiki; editors can control the visibility of hidden categories in their preferences.

The idea behind hidden categories is to separate normal content and housekeeping ([[:category:todo|todo]]) informations.

: ''See also [https://www.mediawiki.org/wiki/Help:Categories#Hidden_categories Help:Categories - MediaWiki] section Hidden categories''

[[category:todo]]

Category:All redirect categories

2026-06-08T03:30:06Z

Fredg999: Categories

__HIDDENCAT__

[[Category:Contents]]

Category:Redirect

2026-06-08T03:29:32Z

Fredg999: Fredg999 moved page Category:Redirect to Category:All redirect categories: Merge history from existing page

#REDIRECT [[:Category:All redirect categories]]

Category:All redirect categories

2026-06-08T03:29:32Z

Fredg999: Fredg999 moved page Category:Redirect to Category:All redirect categories: Merge history from existing page

__HIDDENCAT__

Category:Redirects from sort names

2026-06-08T03:28:01Z

Fredg999: Categories

__HIDDENCAT__

[[Category:All redirect categories]]

Category:Redirects to project namespace

2026-06-08T03:26:37Z

Fredg999: Hidden category

__HIDDENCAT__

[[Category:All redirect categories]]

Category:Redirects from shortcuts

2026-06-08T03:26:20Z

Fredg999: Hidden category

__HIDDENCAT__

[[Category:All redirect categories]]

Category:Redirects to project namespace

2026-06-08T03:23:52Z

Fredg999: Created page with "Category:Redirects"

[[Category:Redirects]]

Category:Redirects from shortcuts

2026-06-08T03:23:42Z

Fredg999: Categories

[[Category:Redirects]]

XW:IntTodo

2026-06-08T03:23:04Z

Fredg999: Categories

#REDIRECT [[Xenharmonic Wiki:Manual of Style/Interval pages]]

[[Category:Redirects to project namespace]]
[[Category:Redirects from shortcuts]]

XW:MOS

2026-06-08T03:22:36Z

Fredg999: Recycle redirect to the broader Manual of Style

#redirect [[Xenharmonic Wiki: Manual of Style]]

[[Category:Redirects to project namespace]]
[[Category:Redirects from shortcuts]]

Xenharmonic Wiki:Manual of Style/Interval pages

2026-06-08T03:21:38Z

Fredg999: Increase scope

This is a '''style guide for interval pages'''.

For guidance on how to expand or improve existing pages, this page's sections provide on what to include, and how to name each section. Sections should be added ''as needed''. Sections in ''italics'' do not denote actual sections, but rather items to add in addition to existing sections or outside of any section.

{{Note| As this guide cannot account for every possible use case, editors are advised to use their best judgment on what to add or not. Additionally, nothing about this guide is set in stone; this guide can (and should!) be updated to fit current developments regarding interval pages. }}

== ''Introduction'' ==
{{todo|inline=1|expand|comment=Work in progress}}

== Todo categories ==
: ''Shortcut: '''XW:IntTodo'''''
An interval page belongs in Stubs if it belongs to any of the following groups:
# Pages with 1 sentence or less of human-written text.
# Pages with ''less than'' 1 paragraph of human-written text, about intervals with at least moderately far-reaching impacts on xenharmonic theory and practice, with an [[odd-limit]] of 25 or less.

An interval page belongs in Todo:expand if it belongs to any of the following groups:
# Pages with a total of 1 paragraph of human-written text, about intervals with large, far-reaching impacts on xenharmonic theory and practice, with an odd-limit of 25 or less.
# Pages with 1 paragraph or less of human-written text, about [[comma]]s with large, far-reaching impacts on xenharmonic theory and practice.

All interval pages that do not belong to one of the above groups, should not be in Stubs nor Todo:expand.

The history of this guideline can be found in [[Xenharmonic Wiki:Manual of Style/Interval pages/History]].

[[Category:Xenharmonic Wiki guidelines]]

Xenharmonic Wiki:Manual of Style/Interval pages/History

2026-06-08T03:18:59Z

Fredg999: Created page with "== History == Following a discussion in Xenharmonic Wiki talk:Things to do, a Google Forms survey was run by Budjarn Lambeth from Jan 1 to Jan 3 2025 (Sydney time). The survey was posted on the Wiki's Facebook, its Discord, and the aforementioned talk page. 4 wiki editors voted. Lambeth himself did not vote. The survey asked in which circumstances an interval page should be in Category:Stubs, in Category:Todo:expand, or in neither of those. Based on the results..."

== History ==
Following a discussion in [[Xenharmonic Wiki talk:Things to do]], a Google Forms survey was run by [[Budjarn Lambeth]] from Jan 1 to Jan 3 2025 (Sydney time). The survey was posted on the Wiki's Facebook, its Discord, and the aforementioned talk page. 4 wiki editors voted. Lambeth himself did not vote.

The survey asked in which circumstances an interval page should be in Category:Stubs, in Category:Todo:expand, or in neither of those.

Based on the results, Lambeth created the guidelines.

=== Survey results ===
==== Key ====
(^^) Indicates the winning option.

(??) Indicates an unresolvable tied winner.

==== Winner determination method ====
# If any option has >50% of the votes, it wins.
# If every option has 50% or less, then eliminate the last placed option and reallocate its votes as follows:
## "EXPAND" --> "STUBS"
## "STUBS" --> "EXPAND"
## "NEITHER" --> "STUBS"
# Whichever option has the most votes afterwards wins; if it's a tie, then the result is indeterminate
# If there is a tie for last place between "neither" and another option, then treat "neither" as last and the other option as second last (eliminate "neither") - this is because neither wouldn't have a chance to win if it were second last given how preferences are allocated.
# If there is a tie between "stubs" and "expand" for last place, then treat "expand" as last and "stubs" as second last (eliminate "expand") - this is because "expand" is a much smaller category on the wiki, more easily overloaded by too many new pages at once, so it's better for controversial edge cases to go to "stubs" instead.

==== Results by factor ====
Factors sorted from apparent strongest to weakest.

<pre>All 2+ paragraph pages
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

All 0.1-paragraph pages
STUBS 75% (^^)
NEITHER 25%
EXPAND 0%

All high integer limit pages
NEITHER 67% (^^)
STUBS 25%
EXPAND 8%

All 1-paragraph pages
NEITHER 59% (^^)
EXPAND 28%
STUBS 13%

All narrow application pages <2 paragraph
NEITHER 58% (^^)
STUBS 42%
EXPAND 0%

All medium application pages <2 paragraph
NEITHER 54% (^^)
STUBS 25%
EXPAND 21%

All low integer limit pages
STUB 42% (^^)
NEITHER 42%
EXPAND 16%

All comma pages
EXPAND 50% (??)
NEITHER 50% (??)
STUB 0%

All 0.5-paragraph pages
NEITHER 50% (??)
STUBS 44% (??)
EXPAND 6%

All wide application pages <2 paragraph
NEITHER 50% (??)
EXPAND 31% (??)
STUBS 19%</pre>

==== Raw results ====
<pre>Wide application, low numerals, 0.5 paragraph
STUBS 50% (^^)
EXPAND 25%
NEITHER 25%

Wide application, low nums, 1 paragraph
NEITHER 50% (??)
STUBS 25% (??)
EXPAND 25%

Wide application, comma, 1 paragraph
NEITHER 50% (??)
EXPAND 50% (??)
STUBS 0%

Wide application, high nums, 1 paragraph
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

Wide application, 2-3 paragraph
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

Moderate application, low numerals, 0.5 paragraph
STUBS 50% (??)
NEITHER 50% (??)
EXPAND 0%

Moderate application, high numerals, 0.5 paragraph
STUBS 50% (??)
NEITHER 50% (??)
EXPAND 0%

Moderate application, simple comma, 1 paragraph
EXPAND 50% (??)
NEITHER 50% (??)
STUBS 0%

Moderate application, low nums, 1 paragraph
NEITHER 50% (??)
STUBS 25% (??)
EXPAND 25%

Moderate application, complex comma, 1 paragraph
EXPAND 50% (??)
NEITHER 50% (??)
STUBS 0%

Moderate application, high nums, 1 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%

Narrow application, 0.1 paragraph
STUBS 75% (^^)
NEITHER 25%
EXPAND 0%

Narrow application, 0.5 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%

Narrow application, 1 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%</pre>

Category:Redirects from shortcuts

2026-06-08T03:15:33Z

Fredg999: Created page with "Category:Contents"

[[Category:Contents]]

XW:IntTodo

2026-06-08T03:15:00Z

Fredg999: Fix copy-paste error

#REDIRECT [[Xenharmonic Wiki:Manual of Style/Interval pages]]

[[Category:Redirects from shortcuts]]

XW:IntTodo

2026-06-08T03:14:50Z

Fredg999: Redirected page to ✎ Xenharmonic Wiki:Manual of Style/Interval pages

#REDIRECT [[✎ Xenharmonic Wiki:Manual of Style/Interval pages]]

[[Category:Redirects from shortcuts]]

Xenharmonic Wiki:Manual of Style

2026-06-08T03:10:59Z

Fredg999: Update list of subpages

This is the style guide for the Xenharmonic Wiki. This primary page is supported by further detailed subpages:
* [[Xenharmonic Wiki:Manual of Style/Interval pages]]
* [[Xenharmonic Wiki:Manual of Style/MOS pages]]
* [[Xenharmonic Wiki:Manual of Style/Temperament cataloging]]
* [[Xenharmonic Wiki:Manual of Style/Temperament pages]]

If any contradiction arises, this page has precedence.

These guidelines will hopefully make life easier in this wiki, not only for authors but also for readers. Some of them are adopted from {{w|Wikipedia:Manual of Style|Wikipedia}}, but we will keep it short and trust into good communication.

== Naming articles ==
We follow {{w|WP:THE}}, {{w|WP:PLURAL}}, and {{w|WP:NCCAPS}}. In summary:

=== Case ===
The title or '''lemma''' should be in English sentence case (e.g. ''Sentence case'') as opposed to title case (e.g. ''Title Case''), in other words, only the first letter is capitalized if there is not an abbreviation or name in it. The reason behind this guideline is that it is much easier to remember how a lemma is spelled and it can be easily embedded into sentences without changing anything. The first letter of an in-wiki link is automatically capitalized, exactly as article names are.

=== Plurals ===
The title should also be in ''singular form'' unless it is a collection for different types of things. To link to <code>[[<nowiki />interval]]</code> or <code>[[<nowiki />interval]]s</code> is much easier than to link to <code><nowiki>[[intervals|interval]]</nowiki></code>, because the link text automatically incorporates the letters following closing double brackets.

=== Articles ===
We save articles at the initial of the title, unless it is an integral part of the title.

=== Examples ===
* {{Preferred|Val}} (correct)
* {{Avoid|<s>The val</s>}} (avoid)
* {{Avoid|<s>Vals</s>}} (avoid)
* {{Preferred|Normal forms}} (correct)
* {{Preferred|Online platforms}} (correct)

=== Naming concepts/objects ===
We have outlined a generic rule for naming temperaments and commas. See: [[Temperament naming #Temperament and comma naming conventions]].

== Inline styling ==
If you want to add custom visual styling, don't try to hard-code the intended style in the article namespace by adding lots of <code>{{nowrap|<<nowiki/>span style{{=}}"…">}}</code> elements. If everybody uses their own personal style, pages can easily appear messy and become hard to read and edit in the source editor. It is also hard to edit a page if you don't understand how it is constructed. If you find something that doesn't look right, try to find the responsible CSS clause for it or ask an organizer or administrator to do so. If bugs in the CSS style get fixed, this will make more than one user happy.

Another way to get a special layout into articles or article sections is to use templates. If the requested [[Help:template|template]] isn't available, ask an experienced user to build one for you.

== Heading levels ==
Within articles, use from H2 (<code><nowiki>== Title ==</nowiki></code>) for the highest level down to H6 (<code><nowiki>====== sub sub sub sub heading ======</nowiki></code>), but try to avoid too many levels of sub sections. To go down to H4 will often be enough, most articles will only use H2 levels.

== Escape templates and HTML codes ==
Certain characters and character sequences have special meanings in Wiki markup, and sometimes need to be escaped using escape templates or {{w|character encodings in HTML|HTML codes}}. However, this should generally be done only as a last resort since they often make the wiki text difficult to read and edit.

Additionally, using escape templates is not necessarily effective when rendering templates with arguments, as in many cases the result may be interpreted as markup anyways. This is because escape templates merely delay the interpretation of the character sequences they represent as Wiki markup, but they assume that the character sequences themselves are ultimately to be interpreted as markup.

; Avoid (generally)
<pre<includeonly/>>
{{avoid|<nowiki>{{((}}Example template|argument{{))}}</nowiki>}}
</pre>

; Use this instead
<pre<includeonly/>>
{{preferred|<nowiki><nowiki>{{Example template|argument}}</nowiki></nowiki>}}
</pre>

Whitespaces (except for the ordinary space) are encouraged to be written in HTML codes because it is otherwise hard to know what they are. In general (this applies to both whitespaces and other characters) if HTML codes are used, names are preferred to Unicode code points. In general, if you do use code points, {{w|hexadecimal}} (base-16) is preferred to decimal (e.g. <code>&#x200A;</code> is preferred over <code>&#8202;</code>) for any code point with more than three decimal digits (i.e. <code>&#1000;</code> and above) because code points are usually shown in hexadecimal.

== Stub template and other templates ==
When placing [[Template: Stub]] on a page: always place the Stub template at the very end of a page's source, separated by two blank lines from whatever comes before (usually categories).

When placing or using any template, read that template's documentation before placing it. All templates and their documentation can be found in [[:Category: Templates]].

== Decimal numbers ==
Use the English convention with decimal point. (Exception: quotes or entire articles in another language)

{| class="wikitable"
|-
! Correct
! Avoid (example)
|-
| style="background-color: #afa;" | 701.995
| style="background-color: #faa;" | <s>701,995</s>
|}

== Logarithmic interval measures ==
Logarithmic interval measures should generally be given in [[cent]]s since it is the most standard unit for that purpose: it is more easily understood by musicians already familiar with [[12edo]] and by many software programs, such as the [[Scala]] file format. Alternative [[interval size measure]]s are acceptable if they better reflect the idea behind an interval system, scale, etc., but "competing" columns with logarithmic sizes in the same table should usually be avoided. Simple cases like [[degree]]s alongside cents in an interval chain are acceptable.

[[Cent]] values should be written up to 3 decimal places in most contexts where precision matters, such as [[Technical data guide for regular temperaments|temperament data pages]] and other technical tables. Very small intervals may be written up to 3 significant figures, and in scientific notation if needed. In contexts where high precision does not matter as much, it is generally sufficient to round to 1 decimal place or to the nearest cent.

== Quotation marks and apostrophes ==
{{w|Wikipedia:Manual of Style#Quotation marks|As on Wikipedia}}, please:
# Use {{preferred|<big>"</big>straight quotes<big>"</big>}}, instead of {{avoid|<big>“</big>curly quotes<big>”</big>}} (the same applies for single quotes: {{preferred|<big>'</big>straight<big>'</big>}} instead of {{avoid|<big>‘</big>curly<big>’</big>}}), and straight apostrophes ({{preferred|<big>'</big>}}) instead of curly apostrophes ({{avoid|<big>’</big>}}). Straight quotes and straight apostrophes are much easier to type on most keyboards than their curly (typographic) counterparts and produce fewer encoding problems.
# Avoid using {{avoid|<big>`</big>accent marks<big>´</big>}} (e.g. backticks) and {{avoid|<big>′</big>prime symbols<big>′</big>}} (including, e.g. {{avoid|<big>″</big>double primes<big>″</big>}}) as quotation marks or apostrophes.
# Avoid using {{avoid|<big>&bdquo;</big>low-high quotes<big>“</big>}}, {{avoid|<big>「</big>corner brackets<big>」</big>}}, or {{avoid|<big>«</big>guillemets<big>»</big>}} as quotation marks, except in special cases or for non-English text that uses these marks.

The templates {{tlx|'}} and {{tlx|'s}} are helpful when an apostrophe or single quote appears at the beginning or end of text in '''bold''' or ''italics'', because bold and italic text are themselves indicated by sequences of single quotes. When an apostrophe follows italicized text, {{tlx|`}} and {{tlx|`s}} can be used to additionally prevent the apostrophe from intersecting the last letter.

== Links ==
Links—both wiki-internal and external ones—should have meaningful text; something like "[[Conventions|here]]" is not very useful for understanding and orientation, often the page title is a good starting point.

: ''For more info see [[Help: Here-links]]''

Internal links should be as precise as possible. So, for example, if you follow a link that promises a definition of a term you don't know, it's not helpful if it brings you to an article full of new information and the expected definition hidden in a massive amount of text. (there is still a lot to be done in this area)

== See also ==
* [[Help: Introduction]]
* [[Help: Editing]]

[[Category:Xenharmonic Wiki guidelines]]

Xenharmonic Wiki:Optional guidelines for interval page todo categories

2026-06-08T03:10:36Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Optional guidelines for interval page todo categories to Xenharmonic Wiki:Manual of Style/Interval pages: Increase scope, move into Manual of Style

#REDIRECT [[Xenharmonic Wiki:Manual of Style/Interval pages]]

Xenharmonic Wiki:Manual of Style/Interval pages

2026-06-08T03:10:36Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Optional guidelines for interval page todo categories to Xenharmonic Wiki:Manual of Style/Interval pages: Increase scope, move into Manual of Style

This page details optional guidelines to help wiki editors decide whether or not to put an [[interval]] page in [[:Category:Stubs]], in [[:Category:Todo:expand]], or in neither.

When this page needs to be referred to in shorthand, e.g. in an edit summary, feel free to call it '''XW:IntTodo'''.

== Guidelines ==
An interval page belongs in Stubs if it belongs to any of the following groups:
# Pages with 1 sentence or less of human-written text.
# Pages with ''less than'' 1 paragraph of human-written text, about intervals with at least moderately far-reaching impacts on xenharmonic theory and practice, with an [[odd-limit]] of 25 or less.

An interval page belongs in Todo:expand if it belongs to any of the following groups:
# Pages with a total of 1 paragraph of human-written text, about intervals with large, far-reaching impacts on xenharmonic theory and practice, with an odd-limit of 25 or less.
# Pages with 1 paragraph or less of human-written text, about [[comma]]s with large, far-reaching impacts on xenharmonic theory and practice.

All interval pages that do not belong to one of the above groups, should not be in Stubs nor Todo:expand.

== History ==
Following a discussion in [[Xenharmonic Wiki talk:Things to do]], a Google Forms survey was run by [[Budjarn Lambeth]] from Jan 1 to Jan 3 2025 (Sydney time). The survey was posted on the Wiki's Facebook, its Discord, and the aforementioned talk page. 4 wiki editors voted. Lambeth himself did not vote.

The survey asked in which circumstances an interval page should be in Category:Stubs, in Category:Todo:expand, or in neither of those.

Based on the results, Lambeth created the guidelines.

=== Survey results ===
==== Key ====
(^^) Indicates the winning option.

(??) Indicates an unresolvable tied winner.

==== Winner determination method ====
# If any option has >50% of the votes, it wins.
# If every option has 50% or less, then eliminate the last placed option and reallocate its votes as follows:
## "EXPAND" --> "STUBS"
## "STUBS" --> "EXPAND"
## "NEITHER" --> "STUBS"
# Whichever option has the most votes afterwards wins; if it's a tie, then the result is indeterminate
# If there is a tie for last place between "neither" and another option, then treat "neither" as last and the other option as second last (eliminate "neither") - this is because neither wouldn't have a chance to win if it were second last given how preferences are allocated.
# If there is a tie between "stubs" and "expand" for last place, then treat "expand" as last and "stubs" as second last (eliminate "expand") - this is because "expand" is a much smaller category on the wiki, more easily overloaded by too many new pages at once, so it's better for controversial edge cases to go to "stubs" instead.

==== Results by factor ====
Factors sorted from apparent strongest to weakest.

<pre>All 2+ paragraph pages
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

All 0.1-paragraph pages
STUBS 75% (^^)
NEITHER 25%
EXPAND 0%

All high integer limit pages
NEITHER 67% (^^)
STUBS 25%
EXPAND 8%

All 1-paragraph pages
NEITHER 59% (^^)
EXPAND 28%
STUBS 13%

All narrow application pages <2 paragraph
NEITHER 58% (^^)
STUBS 42%
EXPAND 0%

All medium application pages <2 paragraph
NEITHER 54% (^^)
STUBS 25%
EXPAND 21%

All low integer limit pages
STUB 42% (^^)
NEITHER 42%
EXPAND 16%

All comma pages
EXPAND 50% (??)
NEITHER 50% (??)
STUB 0%

All 0.5-paragraph pages
NEITHER 50% (??)
STUBS 44% (??)
EXPAND 6%

All wide application pages <2 paragraph
NEITHER 50% (??)
EXPAND 31% (??)
STUBS 19%</pre>

==== Raw results ====
<pre>Wide application, low numerals, 0.5 paragraph
STUBS 50% (^^)
EXPAND 25%
NEITHER 25%

Wide application, low nums, 1 paragraph
NEITHER 50% (??)
STUBS 25% (??)
EXPAND 25%

Wide application, comma, 1 paragraph
NEITHER 50% (??)
EXPAND 50% (??)
STUBS 0%

Wide application, high nums, 1 paragraph
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

Wide application, 2-3 paragraph
NEITHER 75% (^^)
EXPAND 25%
STUBS 0%

Moderate application, low numerals, 0.5 paragraph
STUBS 50% (??)
NEITHER 50% (??)
EXPAND 0%

Moderate application, high numerals, 0.5 paragraph
STUBS 50% (??)
NEITHER 50% (??)
EXPAND 0%

Moderate application, simple comma, 1 paragraph
EXPAND 50% (??)
NEITHER 50% (??)
STUBS 0%

Moderate application, low nums, 1 paragraph
NEITHER 50% (??)
STUBS 25% (??)
EXPAND 25%

Moderate application, complex comma, 1 paragraph
EXPAND 50% (??)
NEITHER 50% (??)
STUBS 0%

Moderate application, high nums, 1 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%

Narrow application, 0.1 paragraph
STUBS 75% (^^)
NEITHER 25%
EXPAND 0%

Narrow application, 0.5 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%

Narrow application, 1 paragraph
NEITHER 75% (^^)
STUBS 25%
EXPAND 0%</pre>

[[Category:Xenharmonic Wiki]]

Xenharmonic Wiki:Policies and guidelines

2026-06-08T03:01:14Z

Fredg999: Remove Conventions (merged into Manual of Style)

All users of the Xenharmonic Wiki are expected to follow the wiki's fundamental principles: '''[[Xenharmonic Wiki:Five pillars]]'''.

In addition, a number of policies and guidelines exist to specify how to handle certain situations.

== Policies ==
* [[Xenharmonic Wiki:Conduct policy]]
* [[Xenharmonic Wiki:License]]
* [[Xenharmonic Wiki:Privacy policy]]
* [[Xenharmonic Wiki:Protection policy]]

== Guidelines ==
* [[Xenharmonic Wiki:Disambiguation]]
* [[Xenharmonic Wiki:Manual of Style]]
* [[Xenharmonic Wiki:Notability guidelines]]

== See also ==
* [[Xenharmonic Wiki:Introduction]]
* [[Xenharmonic Wiki:Terms of Service]]

[[Category:Xenharmonic Wiki policies and guidelines| ]]

Xenharmonic Wiki:Manual of Style

2026-06-08T03:00:52Z

Fredg999: Move links to subpages to the top, merge relevant sections from Xenharmonic Wiki:Conventions

This is the style guide for the Xenharmonic Wiki. This primary page is supported by further detailed subpages:
* [[Xenharmonic Wiki:Manual of Style/MOS pages]]
* [[Xenharmonic Wiki:Manual of Style/Temperament cataloging]]
* [[Xenharmonic Wiki:Manual of Style/Temperament pages]]

If any contradiction arises, this page has precedence.

These guidelines will hopefully make life easier in this wiki, not only for authors but also for readers. Some of them are adopted from {{w|Wikipedia:Manual of Style|Wikipedia}}, but we will keep it short and trust into good communication.

== Naming articles ==
We follow {{w|WP:THE}}, {{w|WP:PLURAL}}, and {{w|WP:NCCAPS}}. In summary:

=== Case ===
The title or '''lemma''' should be in English sentence case (e.g. ''Sentence case'') as opposed to title case (e.g. ''Title Case''), in other words, only the first letter is capitalized if there is not an abbreviation or name in it. The reason behind this guideline is that it is much easier to remember how a lemma is spelled and it can be easily embedded into sentences without changing anything. The first letter of an in-wiki link is automatically capitalized, exactly as article names are.

=== Plurals ===
The title should also be in ''singular form'' unless it is a collection for different types of things. To link to <code>[[<nowiki />interval]]</code> or <code>[[<nowiki />interval]]s</code> is much easier than to link to <code><nowiki>[[intervals|interval]]</nowiki></code>, because the link text automatically incorporates the letters following closing double brackets.

=== Articles ===
We save articles at the initial of the title, unless it is an integral part of the title.

=== Examples ===
* {{Preferred|Val}} (correct)
* {{Avoid|<s>The val</s>}} (avoid)
* {{Avoid|<s>Vals</s>}} (avoid)
* {{Preferred|Normal forms}} (correct)
* {{Preferred|Online platforms}} (correct)

=== Naming concepts/objects ===
We have outlined a generic rule for naming temperaments and commas. See: [[Temperament naming #Temperament and comma naming conventions]].

== Inline styling ==
If you want to add custom visual styling, don't try to hard-code the intended style in the article namespace by adding lots of <code>{{nowrap|<<nowiki/>span style{{=}}"…">}}</code> elements. If everybody uses their own personal style, pages can easily appear messy and become hard to read and edit in the source editor. It is also hard to edit a page if you don't understand how it is constructed. If you find something that doesn't look right, try to find the responsible CSS clause for it or ask an organizer or administrator to do so. If bugs in the CSS style get fixed, this will make more than one user happy.

Another way to get a special layout into articles or article sections is to use templates. If the requested [[Help:template|template]] isn't available, ask an experienced user to build one for you.

== Heading levels ==
Within articles, use from H2 (<code><nowiki>== Title ==</nowiki></code>) for the highest level down to H6 (<code><nowiki>====== sub sub sub sub heading ======</nowiki></code>), but try to avoid too many levels of sub sections. To go down to H4 will often be enough, most articles will only use H2 levels.

== Escape templates and HTML codes ==
Certain characters and character sequences have special meanings in Wiki markup, and sometimes need to be escaped using escape templates or {{w|character encodings in HTML|HTML codes}}. However, this should generally be done only as a last resort since they often make the wiki text difficult to read and edit.

Additionally, using escape templates is not necessarily effective when rendering templates with arguments, as in many cases the result may be interpreted as markup anyways. This is because escape templates merely delay the interpretation of the character sequences they represent as Wiki markup, but they assume that the character sequences themselves are ultimately to be interpreted as markup.

; Avoid (generally)
<pre<includeonly/>>
{{avoid|<nowiki>{{((}}Example template|argument{{))}}</nowiki>}}
</pre>

; Use this instead
<pre<includeonly/>>
{{preferred|<nowiki><nowiki>{{Example template|argument}}</nowiki></nowiki>}}
</pre>

Whitespaces (except for the ordinary space) are encouraged to be written in HTML codes because it is otherwise hard to know what they are. In general (this applies to both whitespaces and other characters) if HTML codes are used, names are preferred to Unicode code points. In general, if you do use code points, {{w|hexadecimal}} (base-16) is preferred to decimal (e.g. <code>&#x200A;</code> is preferred over <code>&#8202;</code>) for any code point with more than three decimal digits (i.e. <code>&#1000;</code> and above) because code points are usually shown in hexadecimal.

== Stub template and other templates ==
When placing [[Template: Stub]] on a page: always place the Stub template at the very end of a page's source, separated by two blank lines from whatever comes before (usually categories).

When placing or using any template, read that template's documentation before placing it. All templates and their documentation can be found in [[:Category: Templates]].

== Decimal numbers ==
Use the English convention with decimal point. (Exception: quotes or entire articles in another language)

{| class="wikitable"
|-
! Correct
! Avoid (example)
|-
| style="background-color: #afa;" | 701.995
| style="background-color: #faa;" | <s>701,995</s>
|}

== Logarithmic interval measures ==
Logarithmic interval measures should generally be given in [[cent]]s since it is the most standard unit for that purpose: it is more easily understood by musicians already familiar with [[12edo]] and by many software programs, such as the [[Scala]] file format. Alternative [[interval size measure]]s are acceptable if they better reflect the idea behind an interval system, scale, etc., but "competing" columns with logarithmic sizes in the same table should usually be avoided. Simple cases like [[degree]]s alongside cents in an interval chain are acceptable.

[[Cent]] values should be written up to 3 decimal places in most contexts where precision matters, such as [[Technical data guide for regular temperaments|temperament data pages]] and other technical tables. Very small intervals may be written up to 3 significant figures, and in scientific notation if needed. In contexts where high precision does not matter as much, it is generally sufficient to round to 1 decimal place or to the nearest cent.

== Quotation marks and apostrophes ==
{{w|Wikipedia:Manual of Style#Quotation marks|As on Wikipedia}}, please:
# Use {{preferred|<big>"</big>straight quotes<big>"</big>}}, instead of {{avoid|<big>“</big>curly quotes<big>”</big>}} (the same applies for single quotes: {{preferred|<big>'</big>straight<big>'</big>}} instead of {{avoid|<big>‘</big>curly<big>’</big>}}), and straight apostrophes ({{preferred|<big>'</big>}}) instead of curly apostrophes ({{avoid|<big>’</big>}}). Straight quotes and straight apostrophes are much easier to type on most keyboards than their curly (typographic) counterparts and produce fewer encoding problems.
# Avoid using {{avoid|<big>`</big>accent marks<big>´</big>}} (e.g. backticks) and {{avoid|<big>′</big>prime symbols<big>′</big>}} (including, e.g. {{avoid|<big>″</big>double primes<big>″</big>}}) as quotation marks or apostrophes.
# Avoid using {{avoid|<big>&bdquo;</big>low-high quotes<big>“</big>}}, {{avoid|<big>「</big>corner brackets<big>」</big>}}, or {{avoid|<big>«</big>guillemets<big>»</big>}} as quotation marks, except in special cases or for non-English text that uses these marks.

The templates {{tlx|'}} and {{tlx|'s}} are helpful when an apostrophe or single quote appears at the beginning or end of text in '''bold''' or ''italics'', because bold and italic text are themselves indicated by sequences of single quotes. When an apostrophe follows italicized text, {{tlx|`}} and {{tlx|`s}} can be used to additionally prevent the apostrophe from intersecting the last letter.

== Links ==
Links—both wiki-internal and external ones—should have meaningful text; something like "[[Conventions|here]]" is not very useful for understanding and orientation, often the page title is a good starting point.

: ''For more info see [[Help: Here-links]]''

Internal links should be as precise as possible. So, for example, if you follow a link that promises a definition of a term you don't know, it's not helpful if it brings you to an article full of new information and the expected definition hidden in a massive amount of text. (there is still a lot to be done in this area)

== See also ==
* [[Help: Introduction]]
* [[Help: Editing]]

[[Category:Xenharmonic Wiki guidelines]]

Help:Conventions

2026-06-08T02:56:19Z

Fredg999: Fix double redirect

#REDIRECT [[Xenharmonic Wiki:Manual of Style]]

Naming conventions

2026-06-08T02:56:13Z

Fredg999: Fix double redirect, link to section

#redirect [[Xenharmonic Wiki: Manual of Style#Naming articles]]

Conventions

2026-06-08T02:55:34Z

Fredg999: Fix double redirect

#REDIRECT [[Xenharmonic Wiki:Manual of Style]]

Xenharmonic Wiki:Conventions

2026-06-08T02:55:14Z

Fredg999: Merged into Xenharmonic Wiki:Manual of Style (except the "Original research" section which was moved to Xenharmonic Wiki:Notability guidelines, and the Wanted pages which was scrapped)

#REDIRECT [[Xenharmonic Wiki:Manual of Style]]

Xenharmonic Wiki:Notability guidelines

2026-06-08T02:50:45Z

Fredg999: Move "Original research" sections from Xenharmonic Wiki:Conventions

These guidelines define what content is considered appropriate for inclusion in the Xenharmonic Wiki's main space. Unlike {{w|Wikipedia:Notability|Wikipedia}}, we embrace original research and novel ideas while maintaining standards that ensure all content provides value to the xenharmonic community.

These are ''guidelines'', not strict rules. They should be followed in spirit, not literally. They may be updated based on community feedback.

== General principles ==
* '''Musical relevance''': All content must demonstrate clear musical relevance or potential application.
* '''Substantial description''': Entries must include comprehensible prose that explains the system's musical characteristics, not just technical specifications.
* '''Conceptual significance''': Contributions should represent meaningful conceptual approaches to xenharmonic music, not merely arbitrary numbers.

== Notability ==
A page meets our notability threshold if it satisfies ''at least one'' of these criteria:
* '''Verifiable content''': Relevant content that can ''potentially'' be verified through citations is automatically notable.
* '''Documented usage''': Content with documented use in musical traditions or by noted composers/theorists.
* '''Practical application''': Systems, scales, etc. that have been implemented in compositions, instruments, or software.
* '''Theoretical value''': Theoretical systems that solve specific problems, or demonstrate a clear theoretical or conceptual benefit.
* '''Historical relevance''': Tuning systems or intervals with documented historical use, even if impractical.
* '''Community content''': Systems or concepts that have gained recognition within the xenharmonic community.

== Generally not notable ==
The following types of content generally fail to meet our notability threshold:
* '''Arbitrary numbers''': Isolated intervals or commas without demonstrated context or purpose.
* '''High complexity''': Temperaments of high complexity or edos with extremely high divisions (e.g. 31132edo), unless accompanied by a clear explanation of its utility or theoretical significance. This also includes temperaments and commas in impractical subgroups (e.g. 2.43.83).
* '''Technical data without context''': Interval tables, temperaments, commas, or other technical data without accompanying musical explanation. ''This is the most serious issue that pages need to avoid.''

Non-notable topics with closely related notable articles can often be merged into those pages. We strongly recommend marking articles on non-notable topics with {{tlx|novelty}} or {{tlx|mathematical interest}}, as appropriate.

== Improving borderline entries ==
Entries that do not initially meet notability standards can be improved by:
* Explaining how the concept solves specific problems
* Describing the system's unique harmonic, melodic or timbral characteristics
* Adding comparisons to related approaches and highlighting meaningful differences
* Providing historical, cultural, or theoretical context
* Adding examples or compositional ideas on how to approach the interval or tuning system

== Main space vs. user space ==
The Xenharmonic Wiki maintains two distinct content areas.

'''Main space''' pages are pages without any prefix. For example: <code>Major scale</code>. Main space pages are subject to all notability guidelines in this document. They should represent content broadly accepted by the community.

[[Help: User pages|'''User space''']] pages are pages titled <code>User:YourUsername/Topic</code>. For example <code>User:JohnDoe/Major scale</code>. User pages are not subject to the same notability guidelines as main space, but user space content should still be related to xenharmonic theory or practice. User pages should be coherent and free from spam, vandalism, or completely unrelated material. User pages can "graduate" from user space to main space if they become accepted within the xenharmonic community.

User pages are appropriate for:
* Personal theories and explorations
* Idiosyncratic approaches to xenharmonic music
* Essays and opinion pieces
* Experimental systems still under development
* Content that shows potential but does not yet meet main space standards
* Drafts or work-in-progress content

=== Relocation vs. deletion ===
Content that shows potential but does not meet main space notability may be moved to user space. Content that is incoherent or is completely unrelated to xenharmonic music should be deleted rather than relocated. Entries consisting solely of automatically generated content (e.g. interval tables, infoboxes) without context or explanation can be deleted without relocation.

== Original research ==
{{todo|inline=1|cleanup|This section was moved from [[Xenharmonic Wiki:Conventions]] (which was merged into [[Xenharmonic Wiki:Manual of Style]]). It has a lot in common with the preceding section about main and user space, so these sections should probably be merged or otherwise reorganized together.}}
'''Original research is allowed on the Xenharmonic Wiki.''' There are a number of conventions in place to help readers distinguish between established ideas or terms and emergent ones.

Below, ''standard framework'' means the set of established ideas, and ''standard terminology'' means the set of established terms.

# By default, a page in the {{w|WP:MAINSPACE|main namespace}} should be written using the standard framework and terminology whenever possible.
#* References should be provided to support the established ideas and terms, whenever possible, and people who developed ideas and/or coined terms should be credited accordingly.
#* A page in the main namespace may contain original research if it is presented using the standard framework and terminology as much as possible; e.g. [[Generator sequence]].
#* If multiple conflicting terms coexist for a given concept, the most widespread term should be given priority; e.g. [[Superparticular ratio]] (over "epimoric ratio" or "delta-1 ratio"), but [[Delta-N ratio]] (over "superpartient ratio" and "epimeric ratio").
# A page presenting established ideas that contains a few [[:Category:Pages with idiosyncratic terms|idiosyncratic terms]] (i.e. terms used only by a single person or a small group) should have any idiosyncratic term marked as such using [[Template: Idiosyncratic]]; e.g. [[Musical cells]].
#* It is especially important to give proper credit to people who coined idiosyncratic terms, because that helps readers understand that a term is not widely used.
# A page presenting established or original ideas that uses a nonstandard framework or terminology should be placed as a [[subpage]] in the {{w|WP:USERSPACE|user namespace}}, under the editor's [[Help:User pages|user page]]; e.g. [[User:Moremajorthanmajor/8L 3s (perfect twelfth equivalent)]].
#* Alternatively, it maybe be placed as a [[Help: Editing #Subpages|subpage]] in the main namespace, under the topic's main page; e.g. [[22edo/Eliora's approach]]. This option is mainly useful for pages with more than one main contributor.
# A page presenting original ideas in a non-neutral way (e.g. an {{w|WP:Essays|essay}}, presenting its author's own argument on a given topic) should be placed as a [[subpage]] in the user namespace, under the author's user page; e.g. [[User:FloraC/There is not a third side of the river]].
#* Exceptions may be made for pages like [[:Category:Guides|guides]] written with a wide target audience, for which the main namespace offers the best visibility; e.g. [[D&D's guide]].
# A page that contains established or original ideas which are less likely to find practical applications in xenharmonic music should be marked as a [[:Category:Novelties|novelty topic]] using [[Template: Novelty]]; e.g. [[1/0]].
#* Pages about the musical application of established mathematical concepts may be marked as novelties if their relevance to xenharmonic music is too tenuous.
#* Topics which are not sufficiently related to xenharmonic music may be moved to the user namespace or deleted.

What is considered "established" may change over time and should be discussed between editors as needed. In particular, ideas built on established ideas may be considered established even if they are not as widely known as the ideas they are built on; e.g. [[SN scale]].

In addition, editors should keep in mind that other editors are more likely to edit pages in the main namespace than ones in the user namespace. In short, if you don't want other users interfering too much with your work, stay in the user namespace; and if you don't want other users interfering at all with your work, publish outside the wiki and provide a link to it on an appropriate wiki page.

== See also ==
* [[Xenharmonic Wiki: Five pillars]]
* [[Xenharmonic Wiki: Conventions]]

[[Category:Xenharmonic Wiki guidelines]]

Xenharmonic Wiki:Temperament catalog guide

2026-06-08T02:29:34Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Temperament catalog guide to Xenharmonic Wiki:Manual of Style/Temperament cataloging: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki:Manual of Style/Temperament cataloging]]

Xenharmonic Wiki:Manual of Style/Temperament cataloging

2026-06-08T02:29:34Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Temperament catalog guide to Xenharmonic Wiki:Manual of Style/Temperament cataloging: Follow Wikipedia-like structure

This is a '''guide for where to put and/or find temperament data'''.

{{Note| As this guide cannot account for all edge cases, editors are advised to use their best judgement on where to put and/or find temperament data. Additionally, nothing about this guide is set in stone; this guide can (and should!) be updated to fit current developments regarding temperament pages. }}

== General rules ==
Avoid duplication. A temperament should be catalogued exactly once on the wiki.

== Families, clans, and collections ==
{{Main| Temperament families and clans }}

A family has a head that is a full-prime-limit temperament. A clan has a head that is a subgroup temperament. Family and clan pages should both be titled after the full-prime-limit temperament. Rarely, a clan may be referred to by the name of the subgroup temperament + family. For example:
* Archytas family is the rank-3 family of 2.3.5.7 {64/63};
* Archytas clan is the rank-2 clan of 2.3.7 {64/63}.
** ''Archy family'' is an alias of ''archytas clan''.

Temperament families and clans should only be created when the head temperament is notable by itself, has multiple branches to higher limits, and for the sake of navigability, is within rank-2 to rank-4. The head temperament should be one of the 7-limit tri-prime subgroups (2.3.5, 2.3.7, 2.5.7, and 3.5.7) for rank-2, the 11-limit analog for rank-3, or the 13-limit analog for rank-4.

Besides families and clans, there are pages that collect temperaments of a certain comma on this wiki. These pages are for temperaments one rank lower than its corresponding family, and are used because some temperaments are more closely associated with the comma than any other or otherwise do not belong to any notable family or clan.

Temperament families, clans, and collections are the bread and butter for documenting individual temperaments on this wiki. Temperament data should be placed there whenever applicable. The specific hierarchy of priority is explained as follows.

If a temperament belongs to an existing family or clan, or one that is supposed to exist according to the rules above, consider putting it there. If a temperament belongs to multiple families or clans, determine if it is a [[strong extension]] of the head of each and put it where it is a strong extension of the head. A strong extension is an extension where the generators are not split; it is generally the preferred place for the temperament since the relation between the temperament in question and the head is most clear. And if a temperament is zero or multiple strong extensions at the same time, it may be placed in the family or clan of the simpler subgroup or the simpler head, depending on which is more relevant.

Otherwise, it should be placed in a collection page of the simplest comma tempered out in the temperament.

For example:
* Hemiwürschmidt is found in Hemimean clan, ''not'' Würschmidt family, since it is a strong extension of didacus, the head of the hemimean clan, and only a weak extension of würschmidt;
* Dominant is found in Meantone family, since 2.3.5 is simpler than 2.3.7, but schism is found in Archytas clan, since the archytas comma is more "structural" to the temperament.

However, no-2 or no-3 clans should be treated just like collections, since the relation between the members and the head is often not obvious there.

For example:
* Sensi is found in Sensipent family, ''not'' Sensamagic clan;
* Miracle is found in Gamelismic clan, ''not'' Quince clan.

== Other pages ==
=== Very high/low accuracy temperaments ===
The criteria of inclusion for these pages are given in the introductions. Currently no [[badness]] constraint is in effect but in future there might be. The head of each entry should only be temperaments of the 7-limit tri-prime subgroups for rank-2, the 11-limit analog for rank-3, or the 13-limit analog for rank-4. Extensions may be put there if they meet the criteria above.

=== Equivalence continua ===
Equivalence continua only hold temperament data of the particular subgroup they are defined in. An equivalence continuum for an equal temperament should only be created if the equal temperament is special in some way, e.g., it is a record 5-limit temperament. Any rank-2 temperament of a 7-limit tri-prime subgroup which does not fit in a family or clan should be placed in an equivalence continuum, when applicable.

=== Miscellaneous 5-limit/7-limit temperaments and catalog of rank-4 temperaments ===
The pages Miscellaneous 5-limit temperaments and Miscellaneous 7-limit temperaments hold temperament data of the particular limit given in the title, for rank-2 and rank-3 temperaments, respectively.

Any 5-limit rank-2 temperament which does not fit in a family, nor an equivalence continuum, should go to Miscellaneous 5-limit temperaments. Any 7-limit rank-3 temperament which does not fit in a family should go to Miscellaneous 7-limit temperaments. Any 11-limit rank-4 temperament as well as their extensions which does not fit in a family should go to Catalog of rank-4 temperaments.

=== Subgroup temperaments ===
Subgroup temperament pages include Subgroup temperaments and the various No-''p'''s subgroup temperaments. Any subgroup temperament should go here unless they fit any of the above categories.

=== Fractional-octave temperaments and comma pages ===
Unless necessary, putting temperament data in these pages should generally be avoided. Fractional-octave temperament pages have poor discoverability, whereas temperament data in comma pages tend to be intrusive for average readers.

[[Category:Xenharmonic Wiki]]

Xenharmonic Wiki:Temperament page style guide

2026-06-08T02:28:01Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Temperament page style guide to Xenharmonic Wiki:Manual of Style/Temperament pages: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki:Manual of Style/Temperament pages]]

Xenharmonic Wiki:Manual of Style/Temperament pages

2026-06-08T02:28:00Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Temperament page style guide to Xenharmonic Wiki:Manual of Style/Temperament pages: Follow Wikipedia-like structure

This is a '''style guide for temperament pages'''.

For guidance on how to expand or improve existing pages, this page's sections provide on what to include, and how to name each section. Sections should be added ''as needed''. Sections in ''italics'' do not denote actual sections, but rather items to add in addition to existing sections or outside of any section.

{{Note| As this guide cannot account for every possible use case, editors are advised to use their best judgment on what to add or not. Additionally, nothing about this guide is set in stone; this guide can (and should!) be updated to fit current developments regarding temperament pages. }}

== ''Introduction'' ==
This precedes the first section. It should open with [[Template: Infobox regtemp]]. It should include a verbal description that uniquely identifies the temperament in question, preferably in the first paragraph. It must end with a link to the corresponding technical data page for the temperament, as well as a link to the dedicated page for extensions if there is one.

== Theory ==
=== Interval chain ''or'' interval lattice ===
An interval chain table should be used for rank-2 temperaments. An interval lattice diagram should be used for rank-3 temperaments.

=== As a detemperament of ''n''-et ===
If there is a small equal temperament fit for detempering, this subsection may be added.

=== Notation ===
Discussion on the notations for the temperament may be added here.

=== Chords and harmony ===
Discussion on the chords and harmony available in the temperament may be added here.

== Scales ==
Discussion on the scales available in the temperament as well as links to scala file pages may be added here

== Tunings ==
This section admits the following subsections:
* Norm-based tunings: tables for ''p''-limit norm-based tunings may be added here.
* Target tunings: tables for ''q''-odd-limit minimax, least squares, and minimean tunings, and for DR and equal beating tunings may be added here.
* Tuning spectrum: a table that list edo tunings and eigenmonzo tunings by generator size may be added here.

== Instruments ==
A gallery of instrument designs may be added here.

== Music ==
Links to music may be added here.

== See also ==
Links to other pages may be added here.

== External links ==
Links to outside-wiki resources regarding the temperament and/or its tunings may be added here.

== References ==
If any works are cited, add them here.

== ''Categories'' ==
This succeeds the last section. The following categories should be added here:
* The eponymous category
* Category: rank-''r'' temperaments, where ''r'' is the rank of the temperament

The following categories should be added here if applicable:
* Category: Exotemperaments or Category: Microtemperaments
* Category: Subgroup temperaments
* Categories for the temperament families, clans, or collections the temperament belongs to.

== ''Other sections'' ==
* Extensions
* Rank-(''r'' + 1) temperaments
* Non-octave settings
* History, terminology or etymology
* Diagrams

[[Category:Xenharmonic Wiki]]

Xenharmonic Wiki talk:MOS page style guide

2026-06-08T02:27:42Z

Fredg999: Fredg999 moved page Xenharmonic Wiki talk:MOS page style guide to Xenharmonic Wiki talk:Manual of Style/MOS pages: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki talk:Manual of Style/MOS pages]]

Xenharmonic Wiki talk:Manual of Style/MOS pages

2026-06-08T02:27:42Z

Fredg999: Fredg999 moved page Xenharmonic Wiki talk:MOS page style guide to Xenharmonic Wiki talk:Manual of Style/MOS pages: Follow Wikipedia-like structure

== Lua error in Scale Tree section ==

The Scale Tree section of this guide reports: "Lua error in Module:MOS at line 69: attempt to index local 'equave' (a nil value)". But I don't know how to fix this. [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 06:02, 4 March 2025 (UTC)
: Looks like one of last night's changes fixed it? [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 19:29, 4 March 2025 (UTC)

Xenharmonic Wiki:MOS page style guide

2026-06-08T02:27:42Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:MOS page style guide to Xenharmonic Wiki:Manual of Style/MOS pages: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki:Manual of Style/MOS pages]]

Xenharmonic Wiki:Manual of Style/MOS pages

2026-06-08T02:27:42Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:MOS page style guide to Xenharmonic Wiki:Manual of Style/MOS pages: Follow Wikipedia-like structure

{{mbox|text=This page is maintained by [[Xenharmonic Wiki:WikiProject Mospage|Project Mospage]].}}

{{Infobox MOS|Tuning=5L 2s|debug=1}}
This is a '''style guide for mos pages'''.

The minimum templates for a mos page, for a page that can be considered a stub or otherwise has very little information, is the following:

* [[Template:Infobox MOS|Infobox MOS]]; required, as it categorizes the page
* [[Template:MOS intro|MOS intro]]; recommended
* [[Template:MOS intervals|MOS intervals]]; optional, but recommended for small mosses (no more than around 10 notes)
* [[Template:MOS modes|MOS modes]]; optional, but recommended for small mosses (no more than around 10 notes)
* [[Template:MOS tuning spectrum|MOS tuning spectrum]]; recommended

For guidance on how to expand or improve existing pages, this page's sections provide on what to include, and how to name each section. Sections should be added ''as needed''. Sections in ''italics'' do not denote actual sections, but rather items to add in addition to existing sections or outside of any section. This page uses 5L 2s as its running example.

Scale name is included in the lead section rather than its own section, since the main focus of a mos page is ''what it is'', not ''what it's called''. For TAMNAMS-named scales, this is accomplished using the [[Template:TAMNAMS name|TAMNAMS name]] template; in most cases, this is enough information. A name section ''may'' be added if there are contentious names (EG, misnomers), or an in-depth explanation is needed, but for TAMNAMS-named scales, the template already includes either further reasoning or a link to said reasoning.

'''Disclaimer''': as this guide cannot account for every possible use case, editors are advised to use their best judgment on what to add or not. Additionally, nothing about this guide is set in stone; this guide can (and should!) be updated to fit current developments regarding mos pages.

== ''Lead section'' (precedes the first section) ==
<pre>
{{Infobox MOS}}
{{MOS intro}}
</pre>
The lead section should, at the minimum, consist of [[Template:Infobox MOS]] and the [[Template:MOS intro]]. To ensure proper order of templates when viewed on mobile devices, the infobox should be placed before the intro. Hatnotes should be placed before the infobox. The mos intro is as follows:

{{MOS intro|Scale Signature=5L 2s}}
Other important info can include the following:

* Whether the mos can be thought of a warping of another, more familiar mos or edo. Examples:
** 4L 3s can be seen as a warped diatonic scale (5L 2s), where one large step is replaced with a small step.
** 5L 1s can be seen as the equal-tempered whole-tone scale (6edo) but with one step that is larger than the others.
* Usage, discovery, and noteworthy temperaments the mos corresponds to.
* Under what conditions is the mos proper. This is only recommended for mosses with notable near-mos forms, as this information is included in the intro already.
Sections that would be otherwise too short, such as temperament-related information, can be added in the lead section instead.

What the mos is referred to may also be included here. Names that see common use should be added here; proposed names are assumed to be idiosyncratic until proven otherwise.

Subsections for this follow the format for TAMNAMS, in which the following are described in their own subsections:

== Scale properties ==
=== Intervals ===
The use of TAMNAMS is advised for describing the names of its intervals and scale degrees. The mos intervals template gives ranges for each of the intervals present in the mos.
<pre>
{{MOS intervals}}
</pre>{{MOS intervals|Scale Signature=5L 2s}}

=== Modes ===
Listings of the scale's modes, or rotations of its step patterns, are added here. This can include mode names in use by the general community. Names that have not received use by the broader community use should be treated as idiosyncratic, and if applicable, the person who had proposed the names should be stated. Example: ''person-name'' has proposed/advocated for the following names...

Listing mode names ''specific'' to a tuning or temperament is not advised. Linking to such mode names is allowed.<pre>
{{MOS modes}}
</pre>{{MOS modes|Scale Signature=5L 2s}}

Scale degree qualities (major, minor, etc) can be show using the template shown.<pre>
{{MOS mode degrees}}
</pre>{{MOS mode degrees|Scale Signature=5L 2s}}

== Theory ==
Subsections include:

* Low harmonic entropy scales
* Temperament interpretations
Other subsections include:

* Any theory described by musicians/theorists
* Tetrachordal analysis or similar

== Tuning ranges ==
Discussions about specific tuning ranges, and what JI ratios are approximated, can be given. Hatnotes to appropriate temperament pages are also advised.

Tuning ranges include:

* '''Simple tunings''' - Step ratios 2:1, 3:1, and 3:2
* '''Soft-of-basic''' '''tunings''' - Step ratios softer than 2:1
* '''Hard-of-basic''' '''tunings''' - Step ratios harder than 2:1

Sections for smaller ranges can be used instead. Such ranges include:
* '''Ultrasoft tunings''' - Step ratio tunings between 1:1 to 4:3
* '''Parasoft tunings''' - Step ratio tunings between 4:3 to 3:2
* '''Hyposoft tunings''' - Step ratio tunings between 3:2 to 2:1, which can be split even further if needed:
** '''Quasisoft tunings''' - Step ratio tunings between 3:2 to 5:3
** '''Minisoft tunings''' - Step ratio tunings between 5:3 to 2:1
* '''Hypohard tunings''' - Step ratio tunings between 2:1 to 3:1, which can be split even further if needed:
** '''Minihard tunings''' - Step ratio tunings between 2:1 to 5:2
** '''Quasihard tunings''' - Step ratio tunings between 5:2 to 3:1
* '''Parahard tunings''' - Step ratio tunings between 3:1 to 4:1
* '''Ultrahard tunings''' - Step ratio tunings between 4:1 to 1:0

The mos tunings template shows cent values for varying step ratios.
<pre>
{{MOS tunings|Step Ratio=2/1; 3/1; 3/2}}
</pre>
{{MOS tunings|Step Ratio=2/1; 3/1; 3/2|Scale Signature=5L 2s}}

== Scales ==
Links to scala file pages can be added here, as well as links to pages regarding step variations (typically modmos scales) of the mos.

== Scale tree ==
The tuning spectrum template (or scale tree) can be provided using the corresponding template. A handmade table can also be used if the template is found too limiting, such as by substituting the template.
<pre>
{{MOS tuning spectrum}}
</pre>{{MOS tuning spectrum|Scale Signature=5L 2s}}

== Music ==
Links to music can be added here.

== See also ==
Links to other pages can be added here.

== External links ==
Links to outside-wiki resources regarding the mos and/or its tunings can be added here.

== References ==
If any works are cited, add them here.

== ''Categories'' (succeeds the last section) ==
The mos infobox automatically categorizes the mos by note count and under the category of abstract mos patterns. Any other categories can be added here.

== ''Other sections not discussed here'' ==
* Gallery - recommended location is before Music
* Notation - recommended location is after Intervals. Notation schemes shouldn't be added unless it has notable use by multiple composers or its use is ubiquitous, as with 5L 2s. If there are multiple notation schemes, this section may be made into a subpage, though this should be a last resort.
* Approaches
* Genchain
* Trivia

[[Category:Xenharmonic Wiki]]

Help:Editing

2026-06-08T02:23:28Z

Fredg999: Update internal link

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—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><nowiki></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>


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

gives

<pre>


[[Wiki]] markup & '''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;"><includeonly /></code> or (as seen on Wikipedia and many other sites) <code style="white-space: nowrap;"><includeonly></includeonly></code>, as follows:

<syntaxhighlight lang="wikitext">
<pre<includeonly />>


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

gives

<pre<includeonly />>


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

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;">


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

gives

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


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

==== 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.

For example:

{{#tag: syntaxhighlight
|{{^(}}syntaxhighlight lang="wikitext"{{)^}}
{{^(}}!-- Comment --{{)^}}

[[Wiki]] markup & '''bold''' ''italic'' text
{{^(}}/syntaxhighlight{{)^}}
|lang = wikitext
}}

gives

<syntaxhighlight lang="wikitext">


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

=== 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.

==== Unordered ====
Unordered list items are marked by <code>*</code> (asterisk):

* Coffee
* Wine
* Milk

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

# Coffee
# Wine
# Milk

==== 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:

; 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 ====
# Morning
#* Coffee
#* Milk
# Evening
#* Coffee
#* Wine

=== Tables ===
: ''For advanced examples, see [[Help:Table]]''

You can add tables to wiki pages:
{| class="wikitable"
|-
! You write in [[Help:Wikitext editor|wikitext]]
| style="border-right: 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>
| 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>
|-
! You get (rendered)

| 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
{{!)}}

|}

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).

==== 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).

== Subpages ==
{{Wikipedia|Wikipedia: Subpages}}

'''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:
* 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]]

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.

== 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 [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]]''

Some more examples:

* [[:Category: Todo:add definition]] – here a term needs to be defined
* [[:Category: Todo]] – category of categories that flag articles

== 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 (<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.

== See also ==
* [[Xenharmonic Wiki: Conventions]]
* [[Xenharmonic Wiki: Manual of Style]]
* [[Help: Help]]
* [[Help: Visual editor]] – especially helpful for new users, that's why it's enabled by default

[[Category:Help]]

Xenharmonic Wiki:Protection policy

2026-06-08T02:22:20Z

Fredg999: /* See also */ Update internal link

In some circumstances, pages may need to be '''protected''' from modification by certain groups of editors. Pages are protected when there is disruption that cannot be prevented through other means, such as blocks. The [[Xenharmonic Wiki]] is built on the principle that anyone can edit, and therefore aims to have as many pages open for public editing as possible so that anyone can add material and correct issues. This policy states the protection types and procedures for page protection and unprotection, and when each protection should and should not be applied.

Protection is a technical restriction applied only by [[administrators]], although any user may request protection. Protection can be indefinite or expire after a specified time. The various levels of protection can be applied to the page edit, page move, page create, and file upload actions. Even when a page is protected from editing, the source wikitext of the page can still be viewed and copied by anyone.

== Levels of page protection ==
* '''Semi-protection''' prevents a page from being edited or moved by users whose accounts are not confirmed
* '''Full protection''' prevents a page from being edited or moved by everyone except administrators.

=== Semi-protection ===
Semi-protection is useful when there is a significant amount of disruption or vandalism from new users, or to prevent sockpuppets of blocked or banned users from editing, especially when it occurs on biographies of living persons who have had a recent high level of media interest.

New users can request edits to a semi-protected page by proposing them on its talk page, using <code><nowiki>[[Category:Todo:feedback request]]</nowiki></code> if necessary to gain attention. If the page in question and its talk page are both protected, the edit request should be made at [[Xenharmonic Wiki:Cross-platform dialogue]] instead.

Administrators may apply temporary semi-protection on pages that are:
* Subject to significant but temporary vandalism or disruption (for example, due to media attention) if blocking individual users is not a feasible option.
* Subject to edit warring if all parties involved are new editors. This does not apply when autoconfirmed users are involved.
* Subject to vandalism or edit warring where editors are engaging in IP hopping by using different computers, obtaining new addresses by using dynamic IP allocation, or other address-changing schemes.
* Article discussion pages, if they have been subject to persistent disruption. Such protection should be used sparingly because it prevents newly registered users from participating in discussions.
* Protection should be used sparingly on the talk pages of blocked users, including IP addresses. Instead the user should be re-blocked with talk page editing disallowed. When required, or when re-blocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period not exceeding the duration of the block.
In addition, administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, [[Xenharmonic Wiki:Five pillars|neutral point of view]]).

A page and its talk page should not normally be protected at the same time. In exceptional cases, if a page and its talk page are both protected, the talk page should direct affected editors to [[Xenharmonic Wiki:Cross-platform dialogue]], to ensure that no editor is entirely prevented from contributing.

Semi-protection should not be used as a preemptive measure against vandalism that has not yet occurred or to privilege confirmed users over new users in (valid) content disputes.

The following pages and templates are usually semi-protected for an indefinite period of time:
* Highly visible pages related to the Main Page.
* Pages that should not be modified for legal reasons, such as the general disclaimer or the local copy of the site copyright license.
* Pages that are transcluded very frequently, to prevent vandalism or denial of service attacks. This includes images or templates used in other highly visible or frequently transcluded pages. See {{w|Wikipedia:High-risk templates}} for more information.

A protected highly visible page should display [[:Template:High priority]] at the top of its talk page.

=== Full protection ===
Modifications to a fully protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus. Placing <code><nowiki>[[Category:Todo:feedback request]]</nowiki></code> on the talk page will draw the attention of administrators for implementing uncontroversial changes.

While content disputes and edit warring can be addressed with user blocks issued by uninvolved administrators, allowing normal page editing by other editors at the same time, the protection policy provides an alternative approach as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page consensus a requirement for implementation of requested edits.

When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as vandalism, copyright violations, defamation, or poor-quality coverage of living people. Administrators are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older, stable, or pre-edit-war version.

Fully protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains policy-violating content, or that protection has rewarded edit warring or disruption by establishing a contentious revision, may identify a stable version prior to the edit war and request reversion to that version. Before making such a request, editors should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked.

Administrators who have made substantive content changes to an article are considered involved and must not use their advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policies that bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally.

The following pages and templates are usually fully protected for an indefinite period of time:
* The [[Main Page]].

== Protection by namespace ==
=== Article talk pages ===
Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of disruption.

=== Templates ===
Highly visible templates – those used on a large number of pages or frequently substituted – are often protected based on the degree of visibility, type of use, content, and other considerations.

Protected templates should normally have the {{((}}[[Template:Documentation|Documentation]]{{))}} template. It loads the unprotected /doc page, so that non-admins can edit the documentation, categories and interwiki links.

=== Sandboxes ===
Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. Those who use sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, or copyrights, should instead be warned and/or blocked.

=== User pages ===
User pages and subpages within their own user space can be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or preemptively protected without good reason or cause. Requests for protection specifically at uncommon levels (such as full protection) can be granted if the user has expressed a genuine and realistic need.

In the event of the confirmed death of a user, the user's user page (but not the user talk page) should be fully protected.

=== User talk pages ===
User talk pages are rarely protected. However, protection can be applied if there is severe vandalism or abuse. Users whose talk pages are protected may wish to have an unprotected user talk subpage linked conspicuously from their main talk page to allow good-faith comments from users that the protection restricts editing from.

A user's request to have their own talk page protected is not a sufficient rationale by itself to protect the page, although requests can be considered if a reason is provided.

Blocked users' user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. It also prevents others from being able to use the talk page to communicate with the blocked editor.

In extreme cases of abuse by the blocked user, re-blocking the user with talk page access removed should be preferred over applying protection to the page. If the user has been blocked and with the ability to edit their user talk page disabled, they should be informed of this in a block notice, subsequent notice, or message, and it should include information and instructions for appealing their block off-wiki.

When required, protection should be implemented for only a brief period, not exceeding the duration of the block.

Confirmed socks of registered users should be dealt with in accordance with {{w|Wikipedia:Sockpuppetry}}; their pages are not normally protected.

== See also ==
* [[Xenharmonic Wiki:Five pillars]]
* [[Xenharmonic Wiki:Notability guidelines]]
* [[Xenharmonic Wiki:Conventions]]
* [[Xenharmonic Wiki:Manual of Style]]
* [[Help:Editing]]
* [[FAQ]]

[[Category:Xenharmonic Wiki policies]]

Xenharmonic Wiki:What are this wiki's strengths and weaknesses?

2026-06-08T02:22:03Z

Fredg999: /* Low barrier to editor entry */ Update internal link

The Xenharmonic Wiki has a somewhat unique model among scholarly and educational resources, which gives it unique '''strengths and weaknesses'''.

It inherits many features from Wikipedia:
* A [[Xenharmonic Wiki:Five pillars|neutral point of view]]
* The ability for [[Xenharmonic Wiki:Five pillars|anyone to contribute]]
* The use of hyperlinks and categories whenever possible (ease of navigation)
* Only [[Special:ListGroupRights|admins]] can delete pages or edit the main page
* [[Xenharmonic Wiki:Five pillars|Accessible without charge]]
* [[Xenharmonic Wiki:Five pillars|Free to modify and redistribute]]

However it has some key differences:
* Narrower focus ("[[Xenharmonic Wiki:Five pillars|musical tuning]]" instead of "the entirety of human knowledge")
* [[Xenharmonic Wiki:Five pillars|Original research]] is allowed
* Evidence standards, while they do still exist, are much less strict than Wikipedia
* More flexible [[Xenharmonic Wiki:notability guidelines|notability guidelines]], you can write about any tuning-related topic no matter how obscure, but it may or may not qualify for the main namespace
* An [[Help:How to get your Xenharmonic Wiki account|account]] is required to edit pages

These differences have softened a little since 2023. Since then, any [[term]]s coined in original research are to be marked with the "[[Template:Idiosyncratic|idiosyncratic]]" tag, and any pages with non-notable subject matters are to be marked with the "[[Template:Novelty|novelty]]" box.

Even still, Xen Wiki is a lot more lenient than Wikipedia. Wikipedia doesn't have disclaimer tags, it just fully deletes most original research and non-notable pages.

These differences may seem strange, but the "background" section will shed light on why they are this way.

== Background ==
Because musical tuning is a niche field, there isn't much money or fame in it, and as a result, no publishing infrastructure has been attracted to it or built up around it.

So, most [[:Category:Musicians|musicians]] and [[:Category:Theorists|theorists]] in the field only have the means to publish their works on personal websites, as video essays, or on Bandcamp/Soundcloud/YouTube, rather than in formal academic journals, printed books or labelled albums. This makes it impossible to run Xenharmonic Wiki the same way as Wikipedia, because when it comes to musical tuning, especially [[regular temperament|modern developments]] from the 1980s onwards, there simply are no resources that exist that meet Wikipedia’s guidelines for what is an acceptable source.

In addition, because the music tuning theory world is so small, it is often the case that the same people who are making new works of music or theory, are also the same people maintaining educational resources like the Xenharmonic Wiki. So Xenharmonic Wiki is unable to exclude original research the way Wikipedia does—if we did, there would be nothing on here, and all our music and our theories would never be shared with the world.

== Strengths of Xen Wiki ==
=== Niche topics, new discoveries ===
Xenharmonic Wiki's greatest strength is its ability to document the absolute bleeding edge of music and theory. The newest and the most niche [[Listen|music]], [[:Category:Composers|composers]], scales and theories all make it on to the Xen Wiki, and most them will never make it onto any other similar resource like Wikipedia.

Xen Wiki documents scales that have only been used once or twice. It documents composers who get 20 listens per piece playing the [[Lumatone]] in their bedroom. It documents the pet theories of everyday people who have never been a professor. There is simply no other place that documents all this stuff.

=== Mathematical and technical records ===
Another strength of Xenharmonic Wiki is its huge repositories of technical tuning data:
* The huge [[:Category:Pages with Scala files|repository]] of [[Scala]] files (.scl) for tuning electronic and [[software]] instruments to different scales
* The huge [[Tour of Regular Temperaments|repository]] of [[regular temperament]]s with information on their [[mapping]], [[extension]]s and how to [[generator|generate]] them
* The huge [[:Category:Equal-step tuning|repository]] of pages about every [[equal-step tuning]] from 4 or 5 notes per equave all the way up to hundreds per [[equave]], detailing which [[harmonic]]s they approximate best, what their [[interval]]s are, and what [[MOS scale]]s exist within them
* The huge [[Gallery of Just Intervals|repository]] of pages about intervals, especially [[commas]], detailing their size in [[cents]], their interval ratios, their [[prime limit|prime factorization]] and their [[Temperament naming|etymology]]

Not to mention the [[Mathematical theory|big long pages]] of full mathematical proofs and rigorous definitions, defining tuning concepts in a degree of immense precision not seen anywhere else.

Xen Wiki is really the only place where you can find all that technical stuff. It's very useful for [[Scalesmith|tinkering]] around with scales, to be able to have Xen Wiki open in another window with all the technical data of the tuning you're using just right there in front of you. If you're into the mathematical side of tuning, it's indispensible.

=== Category system ===
Xenharmonic Wiki's secret superpower is its category system. Start at [[:Category:Contents]] and browse the nested subcategories to find absolutely anything. The categorization of pages is meticulous and makes exploring the wiki significantly easier.

Also, at the bottom of any page, you can see what categories that page belongs to. Click on one of the categories, and you can see all the other pages in that category. This is a great way to find relevant related pages when you are trying to [[pedagogy|research]] something.

=== Free as in speech ===
All content on the Xenharmonic Wiki, unless explicitly marked otherwise, is [[Xenharmonic Wiki:License|completely free]] to redistribute and modify.

This is particularly helpful, because it means that all those technical and mathematical repositories mentioned above are completely open to be copied and pasted in any other work, be it a piece of software, an academic paper, anything. This facilitates the free sharing of information and the collaborative development of ideas.

=== Free as in beer ===
Unlike a lot of academic journals or video essay channels with Patreon pages, Xenharmonic Wiki is completely free to access.

Anyone in the world on any device with internet access can view and download any and all content from the Xenharmonic Wiki at no financial cost.

This makes Xenharmonic Wiki accessible to readers from underprivileged backgrounds, readers who are young (high schoolers, college students) and readers who have other financial priorities (eg parenting, hobbies). It allows Xenharmonic Wiki to reach and help more people.

=== Backup copies ===
Frequent backups are made of the Xenharmonic Wiki—one full backup every single day, in multiple locations. If you're reading this, and you have hard disk storage to spare, we encourage you to download one of the backup copies and just stash it away on a couple hard drives at home, or on a cloud drive somewhere. Because, the more people who keep copies of the backups, the longer they will live on. Get your copy at: [[Xenharmonic Wiki:Backups]].

Because of the extensive backup regime, the Xenharmonic Wiki is likely to be preserved for many years longer than any other online resource. All online resources are fleeting, but this wiki is one of the least fleeting. It is effective at preserving information for a long time, by internet standards.

=== Compatibility ===
Xenharmonic Wiki is built on [[Help:Editing|MediaWiki]], the industry standard format for wiki websites, used by Wikipedia, Fandom.com and most others. It uses the same back-end software and the same [[Help:Editing|WikiText]] syntax as all those sites.

This has two big benefits:
# This makes it easy for maintainers of other sites to use content (both [[:Category:Lua modules|Lua modules]] and text content) from Xen Wiki, as importing it is relatively painless.
# This makes it comparatively easy for the Xen Wiki itself to migrate from one hosting provider to another, which it has [[Help:Migration FAQ|already done]] successfully once in its history.

=== Low barrier to editor entry ===
As a wiki, anyone can edit the Xenharmonic Wiki. But as a ''small'' wiki, it has another advantage: there aren't many rules. A huge, sprawling wiki like Wikipedia has pages and pages of intimidating-looking rules, but Xen Wiki doesn't have that. It's pretty easy to jump in and start making major additions straight away.

In terms of rules, compared to Wikipedia's hundreds of pages, Xen Wiki has only three:
* [[Xenharmonic Wiki:Five pillars]]
* [[Xenharmonic Wiki:Conventions]]
* [[Xenharmonic Wiki:Manual of Style]]

Xenharmonic Wiki also has fewer [[Special:ProtectedPages|protected pages]] than Wikipedia. It has a few, but very much not many. Almost all of Xen Wiki's most prominent, critical pages are completely unrestricted and open to editing. This creates a sense of the wiki being very alive, a living breathing thing that can visibly change from month to month. This makes it exciting to a part of as a reader or editor, being able to watch it grow so much, so fast.

== Weaknesses of Xen Wiki ==
Each one of these is something the Wiki is trying to improve upon, but is struggling due to a lack of volunteers with both the necessary expertise, and the necessary free time on their hands.

So, if you have the time, please [[Help:How to Get Your Xenwiki Account|sign up]] and contribute to helping us resolve one or more of these weaknesses.

=== Too many trees, not enough forest ===
The Xenharmonic Wiki has a general tendency where pages about advanced, [[:Category:Novelties|esoteric]] concepts are written in impressive and helpful detail, while pages about the [[General theory|fundamental]] core figures or concepts in musical tuning are barebones stubs with just a sentence or two.

This makes the Xen Wiki a great resource for readers who are already familiar with those core concepts and are looking to explore the many facets and details of musical tuning. However it makes the Xen Wiki an often-frustrating resource for those trying to begin learning tuning theory in the first place.

=== Underrepresentation of traditional and folk tuning ===
It is likely that a big majority of microtonalists in the world today live in North [[African music|Africa]], the [[Arabic, Turkish, Persian|Middle East]], [[Indian|South Asia]] and [[Indonesian|Indonesia]]. Despite this, of the over 18,000 pages on this wiki, the pages covering all those traditions combined number just 30. That makes ''most'' of the microtonal musicians in the world look like barely an afterthought.

One example of this shortcoming is that Arabic, Turkish, and Iranian music are all smushed into the one page: [[Arabic, Turkish, Persian music]]. These are actually each their own very distinct musical traditions. Yes, they share common ancestry. But [[Pythagorean tuning]], [[meantone]], most [[well temperament]]s, and [[12edo]] all share common ancestry, and are tuned much more similar to each other than Arabic, Turkish or Iranian music are to each other. So if each of those tunings mentioned above gets its own individual page, there's no reason why each of these regions of the world shouldn't have ''its'' own page.

Another example is the page "[[African music]]". That would be like having a page called "Eurasian music" which tries to cover the entirety of all European, Turkish, Arabic, Iranian, Indian, Chinese and Indonesian music in a few paragraphs. That's how diverse Africa is, and how insufficient it is for the whole continent to be compressed into one page.

=== Underrepresentation of historical theory ===
Musical tuning has been explored for as long as music itself has been around. Despite this, almost all of the Xen Wiki talks about music tunings of the past 50 years.

There are a few pages about [[Historical temperaments|early modern European]] tuning, from about 1500 onwards, though even those are mostly in need of expansion.

There are almost no pages at all though, about:
* [[Medieval]] European tuning
* [[Ancient Roman]] tuning
* [[Ancient Greek]] tuning
* Historical [[Arabic, Turkish, Persian]] tuning
* [[Ancient Egyptian]] tuning
* [[Ancient Persian]] tuning
* Historical [[Indian]] tuning
* Ancient, medieval and early modern [[Chinese]] tuning
* Ancient, medieval and early modern [[Japanese]] tuning
* [[Pre-Columbian South American music|Pre-Columbian South American]] tuning
* [[Pre-Columbian South American music|Pre-Columbian Mesoamerican]] tuning
* [[Pre-Columbian North American music|Pre-Columbian North American]] tuning
* Historical sub-Saharan [[African]] tuning

As you can see, that is most of history! This is a very big blind spot for the Wiki.

=== Lack of biographical and historical context ===
The Xenharmonic Wiki tends to be biased in favour of [[Mathematical theory|mathematics]] and [[practice]], with little attention paid to the surrounding culture or [[people]].

The Wiki documents thousands of tunings and scales with complete mathematical descriptions, complete enough for anybody to recreate the tuning or scale exactly.

However for almost every one of those tunings and scales, it says nothing about who described the tuning, when they described it, or why they described it. There were human beings behind all of these musical and mathematical structures, but the Wiki often does not tell the story of those human beings.

=== Lack of audio and visual aids ===
The Xenharmonic Wiki has a serious lack of illustrations and [[Listen|audio examples]].

Given how complicated and dense musical tuning can sometimes be, illustrations could go a long way to helping readers understand. So the shortage of them is sorely felt.

It goes without saying that more audio examples would be useful on a wiki about ''music''. The lack of them is sorely felt too.

=== Idiosyncratic terms ===
Because the Xenharmonic Wiki allows original research, and a huge portion of the Wiki ''is'' original research, many authors will casually use their own invented terminology for things, and mix and match it with widely-used terminology, making it unclear to the reader which is which. The reader may then go try to talk to someone using this invented term, or try to Google it, only to realise that nobody else understands or recognises the term.

The Wiki's editors are trying to improve this situation by seeking out any instances of idiosyncratic terms like these being used, and marking them with the <pre>{{idiosyncratic}}</pre> tag. However, we haven't yet found and flagged every instance, many are still out there. Double check whether any new terms you see on the wiki are actually used outside of the wiki or not.

=== Unsourced claims ===
The 'citation needed' tag is not used often enough on the Xenharmonic Wiki. The tag doesn't always have to be used—it doesn't have to be used for original research, for example. But there are many pages on the wiki where authors make fact claims about things that are ''not'' their own original work, and yet they still provide no citations.

This is something to be careful with. If you read a fact claim on the wiki that you want to use, just double check it first to make sure the author didn't just make it up. (And if you see an unsourced claim on the wiki, don't be afraid to add the little <pre>{{Citation needed}}</pre> to alert editors that it needs to be double checked).

=== Other languages (lack thereof) ===
The Xenharmonic Wiki is available in a few other languages, however these each contain only 5 to 50ish pages, which pales in comparison to the over 18,000 English pages.

None of the foreign-language versions of Xenharmonic Wiki are complete enough yet to be serious resources for learning about musical tuning. The wiki is in need of speakers of other languages to help improve this.

== What other resources can supplement Xen Wiki? ==
These are resources that may lack some of the Xen Wiki's strengths, but have equally impressive and distinct strengths of their own.

They work great in combination with the Wiki, helping to cover its weak spots.

=== Tonalsoft ===
Accessible at [http://www.tonalsoft.com/ tonalsoft.com], this site is highly extensive, including software, a blog, a journal, an archive of recordings, scores and similar resources, and an extensive, thorough encyclopedia penned by musical tuning legend [[Joseph Monzo]].

The encylopedia is the highlight, with its intuitive navigation bar, extensive use of hypertext, enlightening visual aids and extensive coverage of every era of tuning theory.

Like Xenharmonic Wiki, it is completely free to access.

=== Huygens–Fokker Foundation ===
Accessible at [https://www.huygens-fokker.org/index_en.html huygens-fokker.org], this site is elegantly laid out and easy to navigate.

It does not cover the same niche topics as the Xen Wiki, but it does a better job of covering foundational topics compared to the Xen Wiki.

It specialises particularly in European and American musical tuning from the period 1600 to 1980.

Along with English, it includes a version of the site in Dutch (Nederlands). It also includes audio examples and an online radio station to listen to.

Like Xenharmonic Wiki, it is completely free to access.

=== Wikipedia ===
Access its page on {{w|Musical tuning}}, from which you can then navigate to the many other pages on musical tuning topics.

Wikipedia does not cover European or North American tuning theory—past or present—very well compared to Xen Wiki, Tonalsoft or Huygens–Fokker. It falls far short of all of them, in that area.

Wikipedia does, however, cover ''non-Western'' musical tuning much more extensively than any of the above sites. As a source for ethnomusicologists or musicians interested in non-Western musical tuning, Wikipedia is leagues above the others. The bibliography sections at the bottom of Wikipedia's musical tuning pages are particularly useful for studying the tuning systems of non-Western traditions.

Like Xenharmonic Wiki, it is completely free to access.

=== MaqamWorld ===
Accessible at [https://www.maqamworld.com/en/index.php maqamworld.com].

"''MaqamWorld is an online resource dedicated to teaching the Arabic [[Maqam]] modal system, which is the foundation of traditional Arabic music. This website mainly covers music from the Eastern Mediterranean part of the Arab World (Egypt, Palestine, Jordan, Lebanon and Syria), with a focus on the early to mid-twentieth century period.''"

Full site is available in English, Arabic, French, Italian, German, Greek, Spanish and Portuguese. Includes images and audio samples.

Like Xenharmonic Wiki, it is completely free to access.

=== Xenharmonic Alliance community ===
A community where you can ask questions about musical tuning:
* [[Links#Discord server|Discord server]]
* [[Links#Facebook groups|Facebook groups]]

=== More supplementary resources ===
* Everything in the [[Links#Educational websites]] section
* Everything in [[The Library]]

; Free
* [https://www.tallkite.com/AlternativeTunings.html ''Alternative Tunings: Theory, Notation and Practice, including the alt-tuner manual'']: an encyclopedia of music tuning theory by [[Kite Giedraitis]]. In particular, modern day tuning systems, and historical European tuning systems.
* [https://www.medieval.org/emfaq/harmony/pyth.html ''Pythagorean Tuning and Medieval Polyphony'']: an encyclopedia of Medieval European music theory by [[Margo Schulter]]
* [https://www.huygens-fokker.org/bpsite/index.html ''The Bohlen-Pierce Site'']: extensive coverage of the theory and practice of the [[Bohlen-Pierce]] tuning
* [https://www.youtube.com/live/KKxXdD-lkwI?si=2xbZJ7SD80bF6nWI ''Theory of Primodality'']: free educational livestream by [[Zhea Erose]] about her theory of [[primodality]] (a theory that the Xen Wiki sometimes struggles to get right as many editors don’t have a background in it)
** [https://sites.google.com/view/budjarnsarchive/home Google Sites archive including a transcript of the livestream]
** [https://web.archive.org/web/20240218055951/https://sites.google.com/view/budjarnsarchive/home Archive.org backup of the Google Site]
* [https://microtonal-guitar.com/tutorial/microtonal-guitar-tutorial-overview/ ''Microtonal-Guitar.com'']: features a series of educational video lessons about music tuning, aimed at [[:Category:Guitar|guitar]] players specifically
* [https://anaphoria.com/wilson.html ''Wilson Archives'']: the official, and largest, archive of the works of [[Erv Wilson]], a pioneer who built much of modern music tuning theory

; Paid
* [https://www.classicalarabicmusic.com/Learning%20Arabic%20Music.htm ''ClassicalArabicMusic''.com]: deep and thorough educational video course about Arabic maqam
* [http://ericederer.com/book/book.html#pdf ''Makam And Beyond: A Progressive Approach To Near Eastern Music Theory'']: a deep and thorough, and affordable, educational book about Turkish makam by [[Eric Ederer]]

== See also ==
* The Xen Wiki page about [[Pedagogy]]

[[Category:Xenharmonic Wiki]]

Xenharmonic Wiki:Things to do

2026-06-08T02:21:46Z

Fredg999: /* Moderator tasks */ Update internal link

<div style="border: 1px green solid; background-color: #efe; padding: 0.5em 1em; margin-bottom: 1em">
__NEWSECTIONLINK__ [[Category:Todo| ]]
'''Hello there! This page is a place for various projects and minute things to do on this wiki. Please be welcome to help with any of them you like!'''

If you have a proposal to improve the basic fundamentals of the wiki, post it on this page.

If you have an experimental proposal for changing or adding to the wiki in a new way, post it at: [[Wikifuture]].

For bugs, please report them at: [[Bugs]].

''See also: [[Xenharmonic Wiki:Conventions|Conventions]], [[Projects#WikiProjects]], [[Help:Migration FAQ]], as well as [[:Category:Todo]] and its subcategories.''
</div>

{{Archives}}

If you think something essential was forgotten and should be here, don’t be shy to add a new section here! If you don’t know if a project would be interesting to others, [[Xenharmonic Wiki talk:Things to do|write at the talk page]] and let’s decide it together.

When the technical help is needed, please aid volunteers with a tool or two for being sure the details are easy to make right. For example, a template, a converter etc.

== Individual tasks ==
These are tasks that one or more individual editors can chip away at, without requiring much oversight from others.

=== Transfer from riters.com ===
There are still a couple of pages at [https://web.archive.org/web/20050503032508/http://riters.com:80/microtonal/ http://riters.com/microtonal] that could be copied over if we want this to be the one true wiki. [[User:Xenjacob|zenjacob]] ([[User talk:Xenjacob|talk]] 21:12, 7 August 2006 (UTC)
: Warning: That site is very old! [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 07:44, 19 September 2018 (UTC)

=== Fill out the scale catalogue ===
Sources for this: all the Yahoo! lists, the Scala archive, original reflection on new and old scales, pages of X.J. Scott, David Finnamore, Tonalsoft...? Have at least one sound example (midi, mp3, ogg...) for each scale, and keep in mind that this wiki allows you to upload files up to 5 MB each.

Ever since learning about the [[MOSScales|MOS scales]] I have desired but not seen a good, thorough introduction to them, or to the two-dimensional method of creating scales. [[User:Xenjacob|zenjacob]] ([[User talk:Xenjacob|talk]] 21:12, 7 August 2006 (UTC)

=== An FAQ: everyone posts questions, answers ===
This could be sufficiently primed by mining the lists. But more importantly it would need to be linked to by a high-search-engine-ranking page. [[User:Xenjacob|zenjacob]] ([[User talk:Xenjacob|talk]] 21:12, 7 August 2006 (UTC)

: '''Update!''' This has now existed for some time, it is at: [[FAQ]].

: There are many unanswered questions there though, so please post your answers.

: And if you have questions, please ask them there because I bet others have the same question too but are shy and hoping someone will ask.

: --[[Budjarn Lambeth]] 05:46, 15 December 2024 (UTC)

=== Add more languages ===
This wiki could benefit from [[What languages do various users know?|wiki translators]] to add new languages to this wiki. [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 18:05, 4 October 2018 (UTC)

=== Create table of interval pages for large edos you’re familiar with ===
If you are familiar with a large edo (100edo or higher), please create a “Table of #edo intervals” page for it, along the lines of [[Table of 99edo intervals]] or [[Table of 198edo intervals]].

Please only do this if you are familiar with the edo, though: i.e. you have made music with the edo, or the edo falls within your sphere of expertise as a theorist.

[[User:FloraC|FloraC]] and [[User:BudjarnLambeth|Budjarn Lambeth]], 21 January 2024.

=== More sound examples ===

We should really add some sound examples - it makes regular wikipedia and other xen websites much more comprehensible/easily digestable.

RobFast on XA Discord, 23 January 2024.

=== Comma pump examples ===

Add audio comma pump examples for commas.

A lot of comma pages have no examples demonstrating how commas can be used to build chord progressions, scales, etc., so '''please add comma pump examples!''' A good example is [[frameshift comma]].

[[User:Akselai|Akselai]], 2024.

=== Add no-twos consistency to Infobox ET ===
The no-twos consistency limit should be added to [[Template:Infobox ET]] for EDTs.

[[User:Lériendil|Lériendil]] on XA Discord, 2024.

: After 30 hours, this received 7 positive reacts and no negative reacts, so we should make it a priority.

: [[User:BudjarnLambeth|BudjarnLambeth]] ([[User talk:BudjarnLambeth|talk]]) 06:22, 26 September 2024 (UTC)

=== Create a "comma names explained" page ===

Create a page explaining how to interpet the following types of comma names:
* "31-comma", "63-comma", "241-comma", etc.
* "11-3/5-comma", "300-3/5-comma", "45-7/5-comma" etc.
* "87-15-comma", "21-23-comma", "59-5 comma", etc.
* "35-cycle", "21-cycle", "19-cycle", etc.
* "5/7-kleisma", "35/11 kleisma", etc.
* "19th partial chroma", "29th partial chroma", etc.
* "34-jubilismic", "23 semitone", "19-minor mediant", etc.
* "87-fold starling comma" (what does 87-fold mean?)
* "prima", "secunda", any other related words
* "trientone", "trienstonic", any other related words
* "hexadecatone", "hendecatonic", any other related words

[[User:BudjarnLambeth|BudjarnLambeth]] ([[User talk:BudjarnLambeth|talk]]) 24 October 2024 (Sydney time)

::: '''Update:''' Work on this has begun, but is still ongoing. Contribute at: [[Systematic comma names explained]]

=== Write full-detail "scales" sections for each of the temperament pages ===
The temperament page "[[slendric]]" has a high-quality section under the subheading "scales". Please write some "scales" sections in this same style for other similar temperament pages.

[[Lériendil]] ([[User talk:Lériendil|talk]]) 03:27, 13 January 2025 (Sydney time) (on [[Discord]])

''Reposted here by [[User:BudjarnLambeth|BudjarnLambeth]] ([[User talk:BudjarnLambeth|talk]]) 10:30, 13 January 2024 (Sydney time)''

== Team tasks ==
These are tasks that will require active cooperation by an organized team of editors in order to complete.

Work on forming a team, or see if one already exists, at: [[Xenharmonic Wiki talk:Things to do|this page's talk page]]. You may also try making a thread in the #wiki channel of the [https://discord.com/invite/FSF5JFT XA Discord], or you may try making a post on the [https://www.facebook.com/groups/xenwiki/ Xenwiki Work Group] on Facebook.

Some of these may become, or have already become [[Projects#WikiProjects|WikiProjects]]. Check that WikiProjects page to see if the task you’re interested in already has a project - and if it does, get involved in it!

=== Get rid of "alternative pages" ===

There are some pages that were mostly started out of frustration of on particular user not any more active in this wiki. The problem with diverging pages about the same topic is that linking to it tends to break or at least dissipate the consistency of the entire wiki. As normally would be the case with pages targeting the same topic but created by chance, the content should be merged into the (mostly obvious) main page. If there is noting valuable on it, the pages should be deleted. The pages are currently in the [[:Category:Alternative pages]]. For discussing deletion etc, we should refrain from doing that on the respective discussion pages, because deletion will remove these as well. We'd better open an own page for discussion deletion. [[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 14:55, 22 November 2020 (UTC)

: I took a look at these. The edo pages are a relic of a discussion on facebook about the proper format for edo pages. Sort of useful. I suggest deleting all but the 15edo-a page and Gareth's page. The 94-edo page might have some good stuff, but since it's 94edo and 15edo jumbled together, it's also really confusing. This is what I suggest, but I don't feel I have the authority to actually delete someone's page. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 03:05, 12 January 2021 (UTC)

: Mostly done, only [[User:Lhearne/15edo]] left, and since it's in the user namespace, it's not as problematic. Still waiting for a reply from Lillian, I might give a poke on Discord. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:51, 26 July 2023 (UTC)

=== Place to discuss deletion requests ===

Sometimes it's not easy to decide if a page should be deleted or not, it has to be discussed first. The problem with discussing deletion requests on the discussion page of the page being questioned is that they both have the same future. If the deletion happens, normal users have no access to the reasoning any more. Most wikis use an extra page for this purpose.

The so-called project namespace (in this wiki it's indicated by the prefix <code>Xenharmonic Wiki:</code>) is dedicated to that purpose, see [https://en.xen.wiki/w/Special:AllPages?from=&to=&namespace=4 pages currently in the project namespace]. [[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 15:08, 22 November 2020 (UTC)

: Wikipedia needs to handle a lot of page deletions, and in particular a lot of page deletion discussions. For more modest needs like ours, maybe we could create the talk page of [[:Category:Pages nominated for deletion]] (therefore [[:Category talk:Pages nominated for deletion]]) and create a topic per request on that page. If the page has a long backlog over time, we can create archive pages to avoid cluttering the active page too much. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:51, 26 July 2023 (UTC)

=== Disambiguation project ===

There is a project [[Xenharmonic Wiki:Disambiguation]] that aims to build the tools we need. Please join the work and [[Xenharmonic Wiki talk:Disambiguation|discuss]] related issues. [[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 11:38, 26 November 2020 (UTC)

: I created [[Template:About]] a while ago for disambiguation hatnotes. I'll try to work on a simple help page soon. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:51, 26 July 2023 (UTC)

=== 13-Limit, 17-Limit and 19-Limit Comma Pages ===

:''todo''

A project to reorganize 11-limit and 13-limit temperaments. That is still discussed.

Join the discussion [[Xenharmonic Wiki talk:Things to do#13-Limit, 17-Limit and 19-Limit Comma Pages]]!

=== Comma tables in EDO pages ===

We found (on [[User talk:FloraC #Fractions vs. names in interval lemmas]]) that the comma tables on EDO pages are overloaded with information already given elsewhere. This self-evolving "convention" makes it hard to provide consistent and correct information about, (alternative) names, corrections etc. The original information should eventually find place in a dedicated page for each comma; the overview pages about [[comma]]s ([[Large comma]], [[Medium comma]], [[Small comma]], [[Unnoticeable comma]]) should be seen as secondary source then. Currently we tend to reduce the comma tables on EDO pages to at most three columns:
* p-Limit
* linked name or fraction (depending) on the lemma of the link target
* ''Comments'' ← only if there really are useful comments

This can be discussed in [[Xenharmonic Wiki talk:Things to do#Comma tables in EDO pages]]

=== Improve accessibility of wiki and present info in a non-technical way ===

: ''(shortcut(s): [[Xenwiki:Accessibility]], [[XenWiki:Accessibility]])''

Many newcomers to xen are daunted by the math-heavy presentation of tunings and basic MOS/temperament ideas on this wiki. Therefore we propose the following:
* Unfamiliar terms should be linked when they are first used in an article.
* Section off or subpage all the math-heavy parts of articles (for example to move [[Fokker block#Mathematical description]] to [[Fokker block/Math]]).
* Introductory articles and sections should assume at most high school algebra and should focus on practical knowledge for musicians and composers, such as musical examples, how to build a scale in Scala, or what intervals and chords [[17edo]] has.
*EDO pages should follow the above rule too. They should present general information in a standardized format, like an encyclopedia article (Not making any particular suggestion on the format now).
** Subpage more theoretical data such as RTT data (such as the comma table) and [[primodality|Zheanist]] data (such as [[neji]]s and higher harmonic series chords approximated)?
* Explanations of abstract concepts should use visualizations and examples where possible (They help even in more mathy contexts).
* Scales of size 5 to 10 should be given extra attention on the wiki.
* <s>Collaborative work on the [[User:IlL/Introduction to RTT|Practical RTT]] series for teaching regular temperament theory (RTT) while using linear algebra terms as little as possible. While [[Mike's Lectures On Regular Temperament Theory|Mike's lectures]] were no doubt valuable to some people, they would have effectively involved teaching a whole course on theoretical linear algebra.</s>
** Maybe there's no need to even teach people to use x31eq or read mapping matrices; see newer proposals above.

Further proposals coming.

Please join the discussion in ''[[Xenharmonic Wiki talk:Things to do#Improve accessibility of wiki and present info in a non-technical way]]''!

: [[Template:Inaccessible]] can now be used to warn readers of pages that may be difficult to understand, while also reminding wiki editors that these pages need work by placing these pages in [[:Category:Inaccessible pages]]. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:51, 26 July 2023 (UTC)

==== Reorganize temperament pages ====
How should temperament pages be reorganized?

[[User:IlL|Inthar]]'s take: IMO there are too many rank-2 temperaments on this wiki that are just variants of each other (have similar optimal tunings) and only differ in some high complexity interpretation for an extra harmonic. Ideally the most important (low-complexity) approximations and subgroups should be given first, and one way we can pin those down is look at what intervals are approximated in small EDO tunings (<=36edo) for the rank 2 temperament.

This suggests a scale-tree based format for temperament pages; each page would focus on a fixed MOS structure and possible temperaments for the generator chain that generates that MOS. The temperaments are ordered in increasing generator size, and more complex temperaments (i.e. approximating additional JI intervals with intervals further out in the generator chain) would be children of simpler temperaments. The new scale tree temperament pages need not replace current temperament pages (they could even be integrated into current MOS structure pages like [[5L 2s]]), but I believe that this is the most intuitive format and should be what newcomers to RTT-based tunings should be directed to. See [[User:IlL/Temp_page_example|example of this format]].

:'''Proposal''': This organization for temperament pages should be integrated into current MOS structure pages.

Please join the discussion in ''[[Xenharmonic Wiki talk:Things to do#Reorganize temperament pages]]''!

==== <s>New format for temperament entries</s> ====
<s>Present regular temperament tunings on temperament pages in a new concrete, easy-to-read format. </s>

We are canceling it because it turns out suboptimal.

Please join the discussion in ''[[Xenharmonic Wiki talk:Things to do#New format for temperament entries]]''!

==== General-audience temperament pages ====

== Moderator tasks ==
Only Xenharmonic Wiki staff have the permissions to complete these tasks.

Please do not harass staff about these tasks, they have a lot to do and will get to this once more urgent day to day maintenance is done. Remember that all Xen Wiki editors, including staff, are unpaid volunteers maintaining this site for free.

You can reduce the workload on staff by ensuring your edits and conduct follow [[Xenharmonic Wiki:Conventions]], [[Xenharmonic Wiki:Manual of Style]] and [[Xenharmonic Wiki:Five pillars]].

=== Add image annotations ===
Could you install this https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator/Installation so we can add annotations to diagrams, like labeling chords in [[:File:Consonance map, triads, sawtooth waves.png]] ? [[User:ResonantFrequencies|ResonantFrequencies]] ([[User talk:ResonantFrequencies|talk]]) 17:51, 26 January 2019 (UTC)

: Process for importing templates and all their dependencies: https://webmasters.stackexchange.com/questions/117429/how-to-use-wikipedia-templates-on-an-outside-mediawiki/117436#117436 [[User:ResonantFrequencies|ResonantFrequencies]] ([[User talk:ResonantFrequencies|talk]]) 02:38, 2 July 2019 (UTC)

=== Interwiki for xen-calc ===
Requesting interwiki for <code>https://www.yacavone.net/xen-calc/?q=$1</code>. These links are used by [[Template:Infobox Interval]] and captchas are annoying.

[[User:Plumtree|Plumtree]] ([[User talk:Plumtree|talk]]) 15:02, 10 October 2022 (UTC)

[[Category:Xenharmonic Wiki]]

Xenharmonic Wiki:Policies and guidelines

2026-06-08T02:21:13Z

Fredg999: Update internal link

All users of the Xenharmonic Wiki are expected to follow the wiki's fundamental principles: '''[[Xenharmonic Wiki:Five pillars]]'''.

In addition, a number of policies and guidelines exist to specify how to handle certain situations.

== Policies ==
* [[Xenharmonic Wiki:Conduct policy]]
* [[Xenharmonic Wiki:License]]
* [[Xenharmonic Wiki:Privacy policy]]
* [[Xenharmonic Wiki:Protection policy]]

== Guidelines ==
* [[Xenharmonic Wiki:Conventions]]
* [[Xenharmonic Wiki:Disambiguation]]
* [[Xenharmonic Wiki:Manual of Style]]
* [[Xenharmonic Wiki:Notability guidelines]]

== See also ==
* [[Xenharmonic Wiki:Introduction]]
* [[Xenharmonic Wiki:Terms of Service]]

[[Category:Xenharmonic Wiki policies and guidelines| ]]

Guides

2026-06-08T02:20:45Z

Fredg999: Update internal link

{{About|guides to learning microtonal music|the Xen Wiki style guide|Xenharmonic Wiki: Manual of Style}}

There are many ways to learn about [[microtonal music]], and luckily there are many resources available! In this page, we will explore a small portion of them…

== How to learn ==
=== 1. Read, read, read ===
Not much to say in general since you are already on the xenharmonic wiki. There's a lot of math out there related to tunings; it's up to you how deep you want to go into it. Just keep clicking links!

==== 1a. Remain skeptical ====
A critical element to your approach to learning about tunings in the internet is skepticism. The internet has a tendency to allow misinformation to prevail so, especially in this niche of relatively new theory, be sure to keep in mind what interest is advanced by someone else's writings, and what it is they may be leaving out.

==== 1b. Tools, not rules ====
Regardless of the objective veracity of someone else's claims, they usually provide (and are often motivated by) some new or different approach to music making. If one approach is musically useful to you, feel free to use it, and if it is not, feel free not to, regardless of how many other people say it is the "right way".

=== 2. Listen and play ===
It's easy to spend a disproportionate amount of time on #1, but two of the best ways to learn about xenharmonics are to listen to and to play them yourself. Check out the [[Listen|Microtonal listening list]] for the former, and the [[Software]] and [[Instruments]] page for the latter. Most of these scales and tunings are brand new, so it's almost a given that you'll learn things that no one else has figured out by playing and writing yourself. That means you won't read about it anywhere until you write it yourself!

=== 3. Network ===
Naturally, some find it encouraging to interact with others working in the same area of study. Here are a few relevant online communities:

'''[[Links #Maps|Maps]]''' | '''Forums''' ([[Links #Discord server|Discord]] [[Links #Facebook groups|Facebook]]) | '''[[Links #Educational websites|Educational websites]]'''

== Overviews ==
Overviews contain general discussions about microtonal music, including [[:Category:Essays|essays]], questions and answers, etc. This is a good place if you don't know where to start!
* [[Making Microtonal Music is Easier Than You’d Think]]: Comprehensive 9000-word tutorial with many images. The article explains xen; from what it even ''is'', to linking resources (including ones on this wiki), to explaining how to make microtonal music in five methods of increasing complexity and cost. Goes from free and easy to more complicated and costing hundreds (or thousands) of dollars/pounds/euros:
** Using a free browser-based synth
** Using free VST plug-ins
** Changing the settings in the program Kontakt / Micro-tuning synths in Reaktor
** Removing the frets on a guitar
** Buying a microtonal-fretted guitar.
* [[List of approaches to musical tuning]]: Musical [[tuning]] can be approached in many different ways, and this article gives a good overview of these approaches.
* … and many more in [[:Category: Overview]].

== Articles ==
Guides that provide basic (and sometimes advanced) information on various topics, aimed at readers who are not yet familiar with these topics.
* [[Dave Keenan & Douglas Blumeyer's guide to RTT]] (D&D's guide): An extensive 9-part guide to [[regular temperament theory]] with many examples and visuals by [[Dave Keenan]] and [[Douglas Blumeyer]].
* [[Mike's lectures on regular temperament theory]]: A series of lessons on regular temperament theory by [[Mike Battaglia]].
* [[Creating Scala scl files for rank two temperaments]]: A tutorial for musicians not yet familiar with the [[Scala]] software who wish to create tuning files for use with [[Instruments#Electronic instruments|electronic instruments]] or [[DAWs]].
* [[Finale Microtonal Accidentals and Playback]]: How to easily start writing microtonal music today! Customize Finale for microtonal display and output.
* ''[https://hackmd.io/@euwbah/extending-harmonic-principles-1 Extending harmonic principles in 12edo to 31edo (external link)]'': A course by @euwbah on HackMD, aimed at musicians familiar with common practice music theory but unfamiliar with microtones. It uses [[31edo]] as a bridge to generalize [[12edo]] concepts to a purer more abstract form, which can then be applied to any [[tuning]].
* [[Nick Vuci's Fundamentals of Xen]], edited by Leo Coogan.
* … and many more in [[:Category: Guides]].

== Videos ==
* [[Video introductions to microtonality]]
* [https://www.youtube.com/playlist?list=PL65EDA7FBA5F8A3CF Learn about Microtonal Music]: A YouTube playlist curated by [[Sevish]] with over 400 videos from various content creators.

== Podcasts ==
* [[MMMday06]]: A single-day podcast project hosted by [[Prent Rodgers]] in 2006.
* [[Now and Xen]]: A podcast about xenharmonic and microtonal music and discussion created by [[Stephen Weigel]] and [[Sevish]] in 2018, currently hosted by [[Stephen Weigel]] as of 2023.
* [[Xendergarten]]: A comedy podcast hosted by [[Userminusone]] since 2023.

== See also ==
* [[MicroPedagogyCollective]] – pedagogy-related projects
* [[Pedagogy questions]]
* [[The Library]] – a list of periodicals, papers, dissertations and books about microtonal music
* [[Corollaries]] – little thought-provoking tidbits about tuning
* [[Composing Powerstart]]

[[Category:Pedagogy]]

Frequently asked questions

2026-06-08T02:20:30Z

Fredg999: Update internal link

{{See also|Pedagogy questions}}

Whether they are frequent or one-of-a-kind, all questions are welcome here. When listing questions, list broad, general questions higher and niche, more specific questions lower. Answer each question on a separate page, linked to by the question.

== About musical tuning ==
 

'''[[Microtonal music|What is microtonal music?]]'''

'''[[Glossary|Where can I find a glossary of musical tuning terms and jargon?]]'''

'''[[Why Microtonality?|Why use microtonality?]]'''

'''[[Approaches to Musical Tuning|What are some different kinds of tuning systems that exist?]]'''

'''[[Systematic comma names explained|How do I decode those strange looking comma names?]]'''

'''What does “golden” refer to in “golden meantone”, “golden flattone”, etc?'''
* [[Rank-2 temperament]]s (of which meantone and flattone are two among many) generate [[MOS scale]]s with two step sizes, large and small.
* Depending on what [[generator]] you use for the temperament, you can make the ratio between large:small different. For example you can have 3:1 meantone, 2:1 meantone, 3:2 meantone, etc. and the same goes for any other rank-2 temperament.
* If the ratio between the step sizes is the [[golden ratio]], then the tuning is a golden tuning, such as “golden meantone”, “golden flattone” or similar.
* Golden tunings are one type of [[metallic MOS]], along with silver tunings, bronze tunings and others.
 

== About the wiki ==
 

'''There's so much to read. Where do I start?'''
* The page [[Xen concepts for beginners]] is the best place to start.
* After that, check out [[General Theory]] for a list of foundational pages about musical tuning.

'''[[Xenharmonic Wiki:What are this wiki's strengths and weaknesses?|What are this wiki's strengths and weaknesses?]]''' (How does it compare to other resources?)

'''[[Xenharmonic Wiki:License|What is this wiki's copyright/intellectual property policy?]]'''

'''I am more interested in the way [[regular temperament theory]] looked before the 2010s, rather than the direction it has taken since then. Is there a wiki that preserves that?'''
* Yes. You can find that at the [https://legacy.xen.wiki/w/Main_Page Legacy Xenharmonic Wiki].
 

'''How do I change my visual theme for the wiki?'''
# While logged in, go to https://en.xen.wiki/w/Special:Preferences
# Then click the "Appearance" tab near the top
# Then choose the skin you want
# Then click "Save" near the bottom left
 

== About editing the wiki ==
 

'''[[Xenharmonic Wiki:I'm a new editor, what is everything I can do to help?|I'm a new editor, what is everything I can do to help?]]'''

'''[[Xenharmonic Wiki:Manual of Style|Where can I find this wiki's style guide?]]'''

'''[[Xenharmonic Wiki:Notability guidelines|Where can I find this wiki's notability guidelines?]]'''

'''[[Xenharmonic Wiki:Recent changes is too crowded, how do I see what's actually important?|Recent changes is too crowded, how do I see what's actually important?]]'''

'''What are user space pages and main space pages?'''
* User space pages are pages titled "User:YourUsername/Topic". For example "User:JohnDoe/Major scale".
* Main space pages are pages without any prefix. For example "Major scale".

'''How do I create a user page?'''
* Search "User:YourUsername/ThePageTitleYouWant" in the search bar (e.g. "User:JohnDoe/The arrowroot biscuit scale").
* It will then say "There is currently no text in this page. You can search for this page title in other pages, search the related logs, or create this page."
* Click "create this page" and then you will be taken to an editing window to create the user page.

'''[[Xenharmonic Wiki:How can I sign my name on a talk page? How can I make my replies indented to the right?|How can I sign my name on a talk page? How can I make my replies indented to the right?]]'''

'''How can I add an inline citation or note?'''
* Put <code><nowiki><ref>The contents of the note</ref></nowiki></code> at the place you want the little superscript number to appear.
* Place <code><<nowiki />references /></code> at the place you want the list of references to appear. (If you do not specify this, it will default to the very bottom of the page.)
* If you want to cite the same reference multiple times, give it a name e.g. <code><nowiki><ref name="Bob et al.">The contents of the note</ref></nowiki></code> the first time you use it.
* Then every subsequent time you can just use <code><<nowiki />ref name="Bob et al." /></code> without all the rest.

'''[[Temperament naming|I discovered a new temperament, how should I name it?]]'''

'''I have a question about formatting or wikitext that isn't answered here. Is there an instruction manual somewhere where I can find it?'''
* The answer is probably contained within the page [[Help:Editing]].

 

== Unanswered questions ==
{{todo|answer questions|inline=1}}

'''[[How do I actually use a rank-3 temperament?]]''' (Please make a step-by-step guide of how to go from the 3 generators at the start, to a [[Scala]] file that works with [[software|Scale Workshop]] at the end? Every step of the way, explain like I’m five?)
* A good way of generating scales for rank-3 temperament's is [[hobbit]] scales, which are sort of like MOS scales except for higher-rank temperaments. I don't think this will answer the full question, though.
* ''in the mean time until this question is answered, see: [[Rank-3 temperament]]''

'''[[Who is who in microtonality?]]'''
* ''in the mean time until this question is answered, see: [[:Category:People]]''

'''[[Why do microtonal musicians argue so much?]]''' (And do they argue more than people in other fields of research?)

'''[[What is all this new terminology good for anyway?]]'''

''(You are encouraged to add more questions here)''

[[Category:Overview]]

Xenharmonic Wiki talk:Article guidelines

2026-06-08T02:19:11Z

Fredg999: Fredg999 moved page Xenharmonic Wiki talk:Article guidelines to Xenharmonic Wiki talk:Manual of Style: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki talk:Manual of Style]]

Xenharmonic Wiki talk:Manual of Style

2026-06-08T02:19:11Z

Fredg999: Fredg999 moved page Xenharmonic Wiki talk:Article guidelines to Xenharmonic Wiki talk:Manual of Style: Follow Wikipedia-like structure

Xenharmonic Wiki:Article guidelines

2026-06-08T02:19:11Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Article guidelines to Xenharmonic Wiki:Manual of Style: Follow Wikipedia-like structure

#REDIRECT [[Xenharmonic Wiki:Manual of Style]]

Xenharmonic Wiki:Manual of Style

2026-06-08T02:19:11Z

Fredg999: Fredg999 moved page Xenharmonic Wiki:Article guidelines to Xenharmonic Wiki:Manual of Style: Follow Wikipedia-like structure

These article guidelines will hopefully make life easier in this wiki, not only for authors but also for readers. Some of them are adopted from Wikipedia, but we will keep it short and trust into good communication.

Don't forget to follow the [[Xenharmonic Wiki: Conventions]] and [[Xenharmonic Wiki: Notability guidelines]].

== Naming articles ==
We follow {{w|WP:THE}}, {{w|WP:PLURAL}}, and {{w|WP:NCCAPS}}. In summary:

=== Case ===
The title or '''lemma''' should be in English sentence case (e.g. ''Sentence case'') as opposed to title case (e.g. ''Title Case''), in other words, only the first letter is capitalized if there is not an abbreviation or name in it. The reason behind this guideline is that it is much easier to remember how a lemma is spelled and it can be easily embedded into sentences without changing anything. The first letter of an in-wiki link is automatically capitalized, exactly as article names are.

=== Plurals ===
The title should also be in ''singular form'' unless it is a collection for different types of things. To link to <code>[[<nowiki />interval]]</code> or <code>[[<nowiki />interval]]s</code> is much easier than to link to <code><nowiki>[[intervals|interval]]</nowiki></code>, because the link text automatically incorporates the letters following closing double brackets.

=== Articles ===
We save articles at the initial of the title, unless it is an integral part of the title.

=== Examples ===
* {{Preferred|Val}} (correct)
* {{Avoid|<s>The val</s>}} (avoid)
* {{Avoid|<s>Vals</s>}} (avoid)
* {{Preferred|Normal forms}} (correct)
* {{Preferred|Online platforms}} (correct)

== Inline styling ==
If you want to add custom visual styling, don't try to hard-code the intended style in the article namespace by adding lots of <code>{{nowrap|<<nowiki/>span style{{=}}"…">}}</code> elements. If everybody uses their own personal style, pages can easily appear messy and become hard to read and edit in the source editor. It is also hard to edit a page if you don't understand how it is constructed. If you find something that doesn't look right, try to find the responsible CSS clause for it or ask an organizer or administrator to do so. If bugs in the CSS style get fixed, this will make more than one user happy.

Another way to get a special layout into articles or article sections is to use templates. If the requested [[Help:template|template]] isn't available, ask an experienced user to build one for you.

== Heading levels ==
Within articles, use from H2 (<code><nowiki>== Title ==</nowiki></code>) for the highest level down to H6 (<code><nowiki>====== sub sub sub sub heading ======</nowiki></code>), but try to avoid too many levels of sub sections. To go down to H4 will often be enough, most articles will only use H2 levels.

== Escape templates and HTML codes ==
Certain characters and character sequences have special meanings in Wiki markup, and sometimes need to be escaped using escape templates or {{w|character encodings in HTML|HTML codes}}. However, this should generally be done only as a last resort since they often make the wiki text difficult to read and edit.

Additionally, using escape templates is not necessarily effective when rendering templates with arguments, as in many cases the result may be interpreted as markup anyways. This is because escape templates merely delay the interpretation of the character sequences they represent as Wiki markup, but they assume that the character sequences themselves are ultimately to be interpreted as markup.

; Avoid (generally)
<pre<includeonly/>>
{{avoid|<nowiki>{{((}}Example template|argument{{))}}</nowiki>}}
</pre>

; Use this instead
<pre<includeonly/>>
{{preferred|<nowiki><nowiki>{{Example template|argument}}</nowiki></nowiki>}}
</pre>

Whitespaces (except for the ordinary space) are encouraged to be written in HTML codes because it is otherwise hard to know what they are. In general (this applies to both whitespaces and other characters) if HTML codes are used, names are preferred to Unicode code points. In general, if you do use code points, {{w|hexadecimal}} (base-16) is preferred to decimal (e.g. <code>&#x200A;</code> is preferred over <code>&#8202;</code>) for any code point with more than three decimal digits (i.e. <code>&#1000;</code> and above) because code points are usually shown in hexadecimal.

== Stub template and other templates ==
When placing [[Template: Stub]] on a page: always place the Stub template at the very end of a page's source, separated by two blank lines from whatever comes before (usually categories).

When placing or using any template, read that template's documentation before placing it. All templates and their documentation can be found in [[:Category: Templates]].

== Article guidelines for specific tuning systems ==
* [[Xenharmonic Wiki: MOS page style guide]]
* [[Xenharmonic Wiki: Temperament page style guide]]

== See also ==
* [[Help: Introduction]]
* [[Help: Editing]]

[[Category:Xenharmonic Wiki guidelines]]

Category:Xenharmonic Wiki policies and guidelines

2026-06-07T20:11:47Z

Fredg999: Cat main

{{Cat main|Xenharmonic Wiki:Policies and guidelines}}

[[Category:Xenharmonic Wiki| ]]

Xenpaper

2026-05-31T04:42:12Z

Fredg999: Add Xenpaper 2

'''Xenpaper''' is a text-based microtonal sequencer. It supports notes and chords in relative pitch, including [[just intonation]], [[equal-step tuning]]s, arbitrary tuning in [[cent]]s and indexed notation within an equal-step tuning or a custom scale, as well as in absolute pitch (in [[Hz]]). Other features include customizing the BPM and oscillator, looping, displaying a pitch ruler, and sharing tunes by URL or iframe.

The first version of Xenpaper, developed by Damien Clarke (aka mosfez), was released on March 8th, 2021 (or possibly earlier{{confirm}}). Version 1 only supports one voice at a time, including chords.

A beta version of Xenpaper 2, developed by [[Lumi Pakkanen]] (aka frostburn), was released on May 29th, 2026. Version 2 adds support for multiple voices, which can be edited in separate tabs within the app.

Xenpaper is designed to help musicians easily create short tunes and experiment in their web browser, hence its slogan: "Write down musical ideas and share the link around."

== External links ==
=== Xenpaper 2 (beta) ===
* [https://xenpaper.lumipakkanen.com/ Official website]

=== Xenpaper ===
* [https://dxinteractive.github.io/xenpaper/ Official website]
* [https://luphoria.com/xenpaper/ Mirror @ luphoria.com]
** The old site (<code><nowiki>https://xenpaper.com/</nowiki></code>) is down. To transfer a link for a xen sketch from the old site, replace <code><nowiki>https://xenpaper.com/#</nowiki></code> with <code><nowiki>https://dxinteractive.github.io/xenpaper/#</nowiki></code> or <code><nowiki>https://luphoria.com/xenpaper/#</nowiki></code>
* [https://github.com/dxinteractive/xenpaper GitHub repository]

[[Category:Software]]

SW

2026-05-31T04:22:59Z

Fredg999: Redirected page to Scale Workshop

#REDIRECT [[Scale Workshop]]

[[Category:Acronyms]]

Template talk:Under review by Wikiproject TempClean

2026-05-27T23:54:28Z

Fredg999: /* Wording */ support

== Wording ==

The wording off this template is kind of odd. "Jurisdiction", really?
– [[User:Sintel|Sintel🎏]] ([[User_talk:Sintel|talk]]) 15:58, 16 April 2025 (UTC)

: Can we remove this? I don't see what purpose it serves. – [[User:Sintel|Sintel🎏]] ([[User_talk:Sintel|talk]]) 14:00, 27 May 2026 (UTC)
:: I support deprecating this template, seeing as the corresponding Wikiproject seems mostly inactive. --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 23:54, 27 May 2026 (UTC)

343/338

2026-05-13T22:37:19Z

Fredg999: Fix typo

{{Infobox Interval
| Name = sooty fox comma
| Color name = 3uuz32, thuthutrizo 2nd
| Comma = yes
}}
'''343/338''', the '''sooty fox comma''', is a [[small comma|small]] [[13-limit]] [[comma]] of 25.422 [[cent]]s. It is the amount by which a stack of two [[14/13]]'s exceeds [[8/7]], or the amount by which a stack of two [[26/21]]'s falls short of [[14/9]].

It factors into simpler commas as ([[105/104]])⋅([[196/195]]), which in turn equals ([[196/195]])2⋅([[225/224]]).

== Temperaments ==
[[Tempering out]] this comma in the 13-limit leads to the rank-5 '''sooty fox''' temperament, and enables [[sooty fox chords]]. An obvious further temperament is to temper out 196/195 and/or 225/224, equating [[14/13]] with [[15/14]] as well as [[16/15]]. This in the 2.3.5.7.13 subgroup is an extension of [[marvel]] and a restriction of [[tripod]].

It is tempered out in [[edo]]s such as [[19edo]], [[31edo]], [[41edo]], and [[50edo]].

== Etymology ==
The comma is named after the Aleutian sooty fox sparrow, [https://www.inaturalist.org/taxa/343338-Passerella-iliaca-unalaschcensis taxa #343338] on iNaturalist.

It was named by [[Budjarn Lambeth]] in 2024, but he retracted the name one day later out of fear that it would be poorly received due to its arbitrary nature. However, another editor added the name back two months later, which Lambeth and others did not oppose, so the name stuck.

== See also ==
* [[Sooty fox scale]] – equal divisions of 343/338

[[Category:Sooty fox]]
[[Category:Commas named for other reasons]]