View source for StarfinderWiki:Manual of style

{{Badges|prot}}
{{Policy}}
The '''Manual of Style''', often abbreviated '''MoS''' or '''MOS''', is a [[Wikipedia:style guide|style guide]] for StarfinderWiki articles. This article contains basic principles. This guide has been adapted from the extensive MoS located on [[Wikipedia:Wikipedia:Manual of style|Wikipedia]].

If the Manual of Style does not specify a preferred usage, discuss your issues on the [[StarfinderWiki talk:Manual of style|talk page]] of this article.

== General principles{{anchor|Consistency}} == <!--
* This header and all subheaders revised. -Yoda8myhead, 5/21/09
* Refreshed and updated. Noted potential issues with older or inconsistently styled articles where a dominant style or first contributor can't be determined. -Oznogon, 7/26/15
-->
=== Internal consistency ===
An overriding principle is that style and formatting should be consistent within a StarfinderWiki article, though not necessarily throughout StarfinderWiki as a whole. One way of presenting information may be as good as another is, but consistency within an article promotes clarity and cohesion. Therefore, even where the Manual of Style permits alternative usages, be consistent within an article.

=== Stability of articles ===
Editors should not change an article from one guideline-defined style to another without a substantial reason unrelated to mere choice of style. Revert-warring over optional styles is unacceptable.

Where there is disagreement over which style to use in an article, defer to the style used by the first major contributor. If the first major contributor used styles inconsistently, or the first contributions cannot be determined, consistently apply the most commonly used styles.

=== Follow the sources ===
Many points of usage, such as the treatment of proper names, can be decided by seeing what other writers do about the problem. Unless there is some clear reason to do otherwise, it is generally a good idea to follow the usage of reliable secondary sources in English on the subject; the sources for the article itself should be reliable. If the sources for the article can be shown to be unrepresentative of current English usage as a whole, follow current English usage instead — and consult more sources.

== Article titles, headings, and sections ==
<!--Should these direct to PFwiki or Wikipedia help pages? {{main|StarfinderWiki:Naming conventions|Wikipedia:Lead section|Wikipedia:Layout|Help:Section}} -->

=== Article titles === <!-- 
* Subheader complete.  Final bullet point might need revision. -Yoda8myhead, 5/21/09 
* Refreshed and updated with imperative voice and updated examples. -Oznogon, 7/26/15
-->
This guidance applies to the titles of StarfinderWiki articles, not to the titles of external articles that are cited.

* Conform to StarfinderWiki's [[StarfinderWiki:naming conventions|naming conventions]], including [[StarfinderWiki:Use lower case|"Use lower case"]].
* Use nouns or noun phrases. Use ({{xt|Languages of the Great Beyond}}, not {{xt|About languages of the Great Beyond}}).
* Write short titles, preferably fewer than ten words.
* Capitalize the initial letter of a title. Otherwise, only capitalize words where they would be used in a normal sentence. Use ({{xt|Gnoll tribes of the Brazen Peaks and surroundings}}, not {{xt|Gnoll Tribes of the Brazen Peaks and Surroundings}}).
* {{xt|A}}, {{xt|an}}, and {{xt|the}} are normally avoided as the first word. Use ({{xt|Geography of Varisia}}, not {{xt|The geography of Varisia}}), unless part of a proper noun (such as a real-world title: {{xt|The Great Beyond: A Guide to the Multiverse}}).
* Avoid special characters such as the slash ({{xt|/}}), plus sign ({{xt|+}}), braces ({{xt|<nowiki>{&nbsp;}</nowiki>}}), and square brackets ({{xt|[&nbsp;]}}). Use {{xt|and}} instead of an ampersand unless it is part of a formal name, such as ({{xt|Dungeons &amp; Dragons}}). Use commas instead of colons, such as in {{xt|Andoran, Spirit of Liberty}}.
* Title real-world articles, such as product pages, with as complete a title as possible while maintaining the above guidelines. For example, ''{{xt|Princes of Darkness, Book of the Damned, Volume 1}}''.

: '''This guidance also applies to ''[[#Section headings|Section headings]]'', below.'''

=== Section headings === <!--
* Subheading completed. -Yoda8myhead, 5/21/09
* Refreshed and updated with common usage. -Oznogon, 7/26/15
-->
: '''See also the guidance in ''[[#Article titles|Article titles]]'' immediately above, which applies to both article titles ''and'' section headings.'''

A section heading provides an overview and link for the section in the table of contents and helps readers navigate an article's text.

* Change a heading only after careful consideration, because this breaks section links to it within the same article and from other articles. If changing a heading, try to locate and fix broken links.
* Gives sections unique names within a page, including subsections. Duplicate headings can cause problems, such as:
** After editing, the article may load at the wrong section.
** The automatic edit summary generated when editing a same-named section is ambiguous.
** Links to a same-named section might not point to the expected article section.
* Avoid adding links to section headings, especially ones that link only part of the heading; they will cause accessibility problems.
* Avoid explicitly referring to the article's subject or higher-level headings unless doing so is shorter or clearer. Headings can be assumed to be about the subject unless otherwise indicated. For example, StarfinderWiki prefers {{xt|Early life}} as a heading name over {{xt|Aroden's early life}} when {{xt|Aroden}} is the article's subject. 
* Capitalize the first letter of the first word and any proper nouns in headings, but leave the rest in lower case. Thus, use {{xt|Habitat and ecology}}, not {{xt|Habitat and Ecology}}.
* Headings in wikitext use unspaced multiple equal signs: {{xt|<code><nowiki>== H2 ==</nowiki></code>}}. The number of equal signs used to set off a heading determines the heading's level. Do not boldface heading text with three apostrophes ({{xt|<code><nowiki>'''</nowiki></code>}}). 
* Nest headings as follows:
** The automatically generated top-level heading of a page is H1, which gives the article title.
** Primary article headings are then {{xt|<code><nowiki>== H2 ==</nowiki></code>}}, followed by {{xt|<code><nowiki>=== H3 ===</nowiki></code>}}, {{xt|<code><nowiki>==== H4 ====</nowiki></code>}}, and so on.
** Spaces between the <code><nowiki>==</nowiki></code> and the heading text are optional. For example, {{xt|<code><nowiki>==H2==</nowiki></code>}} and {{xt|<code><nowiki>== H2 ==</nowiki></code>}} are both valid headings. These extra spaces do not affect the heading's appearance in the article, but do aid in both reading the heading's text and determining its level in wikitext.
* Blank lines above and below a heading's wikitext are optional. Only two or more blank lines above or below a heading will change the public appearance of the page by adding more white space. For wikitext readability, StarfinderWiki generally prefers adding a blank line before, though not after, headings; whichever style you use, it is best to apply it consistently across an article.

=== Main article link === <!-- 
* Complete, no changes from original wikipedia source. -Yoda8myhead, 5/21/09
-->
If a section is covered in a dedicated article, this should be marked by inserting {{tlx|Main|Article name}} directly beneath the section heading.

=== Section management === <!-- 
* Some minor notes below. Mostly complete but needs revision. -Yoda8myhead, 5/21/09
* Refreshed and updated. -Oznogon, 7/26/15, 8/23/15
-->
When creating new sections or editing existing ones, you can help other chroniclers by following a few conventions.

* When linking to a section, it is courteous to leave an editor's note in the destination article's section to remind others that you have linked to that section. List any linking articles' names so that if the title is altered, others can fix the links without having to perform exhaustive searches. For example:
<pre>== Founding of Absalom == <!-- This section is linked from [[Aroden]] and [[Starstone]] --></pre>
* When changing a section's heading, also consider inserting an {{tl|Anchor}} template into the heading tag with the heading's old name. This prevents existing links from breaking. For example:
<pre>== New section name {{Anchor | Founding of Absalom}} ==<!-- This section is linked from [[Aroden]] and [[Starstone]] --></pre>
* When referring to a section from an article's body without linking, italicize the section name. For example, {{xt|the current section is called ''Section management''}}. (Italicize the ''actual'' section name only if it otherwise requires italics, such as the title of a book.)
* Certain sections, such as the {{xt|<nowiki>== References ==</nowiki>}} section, might apply special rules beyond the style guide. See the relevant [[Help:Contents|Help pages]] for more information.

== Capital letters ==
There are differences between the major varieties of English in the use of capitals (uppercase letters). Where this is an issue, the rules of the cultural and linguistic context apply. As for spelling, consistency is maintained within an article.

Capitals are not used for emphasis on StarfinderWiki. Where wording cannot provide the emphasis, use italics.

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;||{{xt|Contrary to popular belief, ankhegs are Not the same as giant monstrous ants.}}
|- valign=top
| ''Incorrect'':             ||{{xt|Contrary to popular belief, ankhegs are NOT the same as giant monstrous ants.}}
|- valign=top
| ''Correct'':               ||{{xt|Contrary to popular belief, ankhegs are ''not'' the same as giant monstrous ants.}}
|}

=== Use of "the" mid-sentence === <!-- 
* Edited and correct, last example might need to be changed. Need to check actual use of The Puddles in texts. -Yoda8myhead, 5/22/09
** I've verified that the last example is correct. -aeakett, 5/22/09
* Refreshed and updated. -Oznogon, 7/26/15
-->
The definite article is not normally capitalized in the middle of a sentence. However, there are idiomatic exceptions&mdash;including most titles of works of art&mdash;which should be quoted exactly. Follow common on a case-by-case basis. As usual, it is a good idea to [[#Follow the sources|consult the article's sources]].
 
{| style="background: transparent;"
|- valign=top
|''Incorrect''&nbsp;||''(generic)'':&nbsp; &nbsp;||{{xt|Ezren applied to The Arcanimirium in Absalom.}}
|- valign=top
|''Correct''        ||''(generic)'':             ||{{xt|Ezren applied to the Arcanimirium in Absalom.}}
|- valign=top
|''Incorrect''&nbsp;||''(title)'':&nbsp; &nbsp;  ||{{xt|No single author is credited with writing ''the Legends of Lucky Farouq''.}}
|- valign=top
|''Correct''        ||''(title)'':               ||{{xt|No single author is credited with writing ''The Legends of Lucky Farouq''.}}
|- valign=top
|''Correct''        ||''(title)'':               ||{{xt|Asmodeus's sacred text is the ''Asmodean Disciplines''.}}
|- valign=top
|''Incorrect''      ||''(exception)'':           ||{{xt|Only the poorest of citizens live in the Puddles.}}
|- valign=top
|''Correct''        ||''(exception)'':           ||{{xt|Only the poorest of citizens live in The Puddles.}}
|}

=== Titles of people === <!-- 
* Completed. -Aeakett, 5/21/09
* NOTE: There has been confusion on how to handle "Runelord/runelord" in particular. We may want to include that as an example. -Yoda8myhead
* Refreshed and updated. -Oznogon, 7/26/15
-->
Many characters in the Starfinder campaign setting have titles, ranging from regal to heraldic to slang. Their use and function in a sentence often determines their style.

* '''When used generically''', lowercase titles such as {{xt|governor}}, {{xt|baron}}, and {{xt|king}}: {{xt|Markwin Teldas is a Molthunian governor}} and {{xt|Utilinus is a Sargavan baron}}. Similarly: {{xt|Three lords attended the tournament}}.
* '''When referring to the formal name of an office''', capitalize it as a proper noun: {{xt|The Ruby Prince of Osirion is Khemet III}}, {{xt|Markwin Teldas is Imperial Governor of Molthune}} and {{xt|Kharswan is Thakur of Jalmeray}} (where {{xt|Imperial Governor}} and {{xt|Thakur of Jalmeray}} are titles). 
* '''When used as parts of a title''', capitalize them: {{xt|Governor Teldas}}, ''not'' {{xt|governor Teldas}}. 
* '''Capitalize royal styles''': {{xt|Her Majesty}} and {{xt|His Highness}}. Exceptions might apply for particular offices.
** For details on using titles and honorifics in biographical articles, refer to [[Wikipedia:Manual of Style (biographies)#Honorific prefixes|Wikipedia's Manual of Style on honorific prefixes]].

=== Religions, deities, philosophies, doctrines, and their adherents ===<!-- 
* Edited by both Yoda8myhead 5/22/09 and Aeakett 5/21/09, but issues still remain. See notes. 
* Refreshed and updated, including in-world examples. -Oznogon 7/26/15
-->
* Capitalize '''religions, sects, and churches''' and their followers, in noun or adjective form. Generally, {{xt|the}} is not capitalized before such names; use ({{xt|the Desnans}}, not {{xt|The Desnans}}).
* '''Religious texts and scriptures''' are capitalized and italicized. For example, use the {{xt|''Parables of Erastil''}}, the {{xt|''Gorumskagat''}}, and the {{xt|''Skull of Mashag''}}). Do not capitalize the definite article "{{xt|the}}" unless it is canonically part of the work's title, such as {{xt|''The Acts of Iomedae''}}; follow the source material in this regard.
* Capitalize '''honorifics for [[deity|deities]]''', including proper nouns and titles. For example, use ({{xt|Master of the First Vault}}, {{xt|Old Deadeye}}, {{xt|the Inheritor}}, {{xt|the Savored Sting}}, {{xt|Lady of Graves}}, {{xt|the Rough Beast}}, {{xt|the Dawnflower}}). Do not capitalize the definite article "{{xt|the}}" unless it is formally a part of the deity's name. 
** The same is true when referring to major religious figures and figures from mythology by titles or terms of respect. Common nouns denoting deities or religious figures are not capitalized; thus {{xt|the Azlanti worshiped many gods}}, {{xt|many Chelaxians worshiped the god Asmodeus}}, {{xt|Aroden and Norgorber are both ascended gods}}, and {{xt|her husband was her muse}} (but {{xt|the nine Muses}}).
* Do not capitalize '''pronouns and possessives referring to figures of veneration''' in original text within StarfinderWiki articles, even when they traditionally are capitalized in a religion's scriptures. However, leave them capitalized when directly quoting texts that capitalize them.
* Do not capitalize '''broad categories of extra-planar or legendary creatures'''. Use ({{xt|archon}}, {{xt|demon}}, {{xt|devil}}, {{xt|deva}}, {{xt|angel}}). Names or titles of unique individual creatures are capitalized, such as ({{xt|the Lawgiver}} and {{xt|the Tarrasque}}), as are organizations of creatures whose name and membership are fixed, such as ({{xt|the Dukes of Hell}}). As with terms for deities, generalized references are not capitalized: ({{xt|demonic}}, {{xt|elemental}}).
* Capitalize '''spiritual or religious events''' ''only'' when referring to specific incidents or periods. Use ({{xt|Taxfest}} and {{xt|the Swallowtail Release}} for the annual events, but also use {{xt|annual tax collection for Abadar}} and {{xt|a Desnan festival concerning swallowtails}} when referring to them generically.
* Do not capitalize '''philosophies, theories, and doctrines''' unless the name derives from a proper noun ({{xt|lowercase "rule of law" versus uppercase [[Laws of Man]]}}) or has become a proper noun (lowercase {{xt|democracy}} refers to rule by popular vote; uppercase {{xt|Common Rule}} refers to the specific system of government in [[Andoran]]). Doctrinal topics or canonical religious ideas (as distinguished from specific events) are given in lower case in StarfinderWiki, such as {{xt|ascendance}}. 
* '''Platonic or transcendent ideals''', including the canonical alignments of [[good]], [[evil]], [[chaos]], [[law]], and [[neutral]]ity, are lowercase. Personifications represented in art, such as a statue of the figure {{xt|Justice}}, are capitalized.

=== Calendar items === <!-- 
* Completed. Some better examples might be needed. -Yoda8myhead, 5/22/09
* Refreshed and updated. -Oznogon, 7/26/15
-->
* '''Months, days of the week, and holidays''' start with a capital letter: {{xt|Desnus}}, {{xt|Oathday}}, {{xt|the Fifth of Neth}} (when referring to the Galtan Independence Day, otherwise {{xt|5 Neth}}). ''See also [[Absalom Reckoning]] and [[StarfinderWiki:Canon policy#Regarding dates|the Canon Policy on dates]].
* '''Seasons''', in almost all instances, are lowercase: {{xt|This summer was very hot}}; {{xt|The winter solstice occurs about Kuthona 22}}; {{xt|I have spring fever}}. When personified, season names may function as proper nouns, and they should then be capitalized: {{xt|I think Spring is showing her colors}}; {{xt|Old Man Winter}}.

=== Animals, plants, and other organisms === <!--
* Removed scientific nomenclature rules for being irrelevant to project. One remaining issue. -Yoda8myhead, 5/22/09 
* Removed genus/species discussion; we can always resurrect it when Paizo publishes ''Ultimate Academia''. -Oznogon, 7/26/15
-->
Common (vernacular) names of flora and fauna should be written in lower case. For example, use {{xt|oak}} or {{xt|lion}}. Where the common name contains a proper noun, such as the name of a person or place, that proper noun should be capitalized: ({{xt|The Azlanti chariot beetle can be found near ancient tombs throughout the former Azlanti Empire}}.

When an alternate capitalization is used in article title, create a [[Help:redirect|redirect]] to the canonical capitalization.

=== Celestial bodies === <!--
* Revised, but may need additional work/examples to meet the needs of our specific wiki. -Yoda8myhead, 5/22/09
* Refreshed and updated with in-world examples and more details on astronomical objects and solar systems. -Oznogon, 7/26/15
-->
* Do not capitalize '''{{xt|[[sun]]}}, {{xt|earth}}, and {{xt|[[moon]]}}''' in general use: {{xt|The moon rises over the [[Mindspin Mountains]]}}, {{xt|The sun beats down on the caravan}}, and {{xt|Farmers work the earth before planting}}. [[Golarion]] is the Starfinder campaign setting's primary world, and its moon's proper name is [[Somal]]. However, capitalize them when mentioning astronomical bodies that take capitals: {{xt|Golarion orbits the Sun, ''but'' the distant world [[Earth]] also orbits a sun-like [[star]].}}
* '''Names of [[planet]]s, [[moon]]s, [[asteroid]]s, [[comet]]s, [[star]]s, [[constellation]]s, [[galaxy|galaxies]], and [[Great Beyond|planes]]''' are proper nouns and start with a capital letter: {{xt|The planet [[Castrovel]] can be seen in the western sky in the late winter}}, {{xt|Never vacation in the [[Negative Energy Plane]] or the [[Plane of Fire]]}}. When a name has more than one word, treat it like other proper nouns with each first letter capitalized: {{xt|Dark Tapestry}}, ''not'' {{xt|Dark tapestry}}; {{xt|the Lantern Bearer}}, ''not'' {{xt|the lantern bearer}}.
* Lowercase '''[[solar system]]''' in all uses. Refer to the other planets around Golarion's sun as {{xt|Golarion's solar system}}.

=== Directions and regions === <!--
* Section done. -Yoda8myhead, 5/22/09
* Refreshed and updated. -Oznogon, 7/26/15
-->
* Do not capitalize '''directions''' such as {{xt|north}} unless they are part of a proper name. The same is true for their related forms: someone might call the northern tip of a city the {{xt|northern point}}, compared to the {{xt|[[North Point]] district}}. 
* Composite directions can be hyphenated depending on the general style adopted in the article: ({{xt|Southeast Avistan}} and {{xt|northwest}} in American English, but {{xt|South-East Avistan}} and {{xt|north-west}} in British English.
* '''Regions''' that are proper nouns, including widely known expressions such as {{xt|[[Western Ravage]]}}, start with a capital letter.

=== Institutions === <!--
* Section done. -Yoda8myhead, 5/22/09
* Refreshed with imperative voice. -Oznogon, 7/26/15
-->
* Capitalize '''names of institutions''' that are proper nouns, such as {{xt|the Acadamae}}, {{xt|Kitharodian Academy}}, and {{xt|Rhapsodic College}}, but generally not the definite article "{{xt|the}}" at the start of a title ({{xt|a degree from the Acadamae}}).
* Do not capitalize '''generic words''' for institutions: ({{xt|university}}, {{xt|college}}, {{xt|hospital}}, {{xt|abbey}}).

{| style="background: transparent;"
|- valign=top
|''Incorrect''&nbsp;||''(generic)'':&nbsp; &nbsp;||{{xt|The College offers programs in arts and sciences.}}
|- valign=top
|''Correct''        ||''(generic)'':             ||{{xt|The college offers...}}
|- valign=top
|''Correct''        ||''(title)'':               ||{{xt|The Rhapsodic College offers...}}
|}

* '''Bodies of government''', such as settlements, counties, and countries, follow the same rules: the names of specific polities are capitalized proper nouns, but generic words for ''types'' of government bodies are not. Sometimes, the full official name of a body is not needed.

{| style="background: transparent;"
|- valign=top
|''Incorrect''&nbsp;||''(generic)'':&nbsp; &nbsp;||{{xt|The City has a population of 55,967.}}
|- valign=top
|''Correct''        ||''(generic)'':             ||{{xt|The city has...}}
|- valign=top
|''Correct''        ||''(title)'':               ||{{xt|The City of Oregent has...}}
|- valign=top
|''Correct''        ||''(skip type)'':           ||{{xt|Oregent has...}}
|}

== Acronyms and abbreviations == <!-- 
* Completed. -Yoda8myhead, 5/22/09
* Refreshed examples and reorganized. -Oznogon, 7/26/15
-->
In general, follow publication [[StarfinderWiki:point of view|point of view]] unless a specific source uses an acronym or abbreviation in-world.

Avoid abbreviations when they would be confusing to the reader, interrupt the flow, or appear informal or lazy. For example, do not use {{xt|approx.}} for {{xt|approximate}} or {{xt|approximately}} unless you must to maintain the width of an infobox or table of data.

When using an abbreviation or acronym, write out the full version and follow it with the  abbreviation in parentheses at its first occurrence within an article. For example, {{xt|The Starfinder Society Adventure Card Guild (PFSACG) was founded ... Paizo regularly publishes new PFSACG scenarios.}}

If the full term is already in parentheses, use a comma ({{xt|,}}) and {{xt|or}} to indicate the abbreviation. For example: {{xt|Each set of scenarios comes with a Chronicle Sheet (for the Starfinder Society Adventure Card Guild, or PFSACG)}}.

=== Plural and possessive forms ===
Acronyms and initialisms, like other nouns, become plurals by adding {{xt|-s}} or {{xt|-es}}: {{xt|They produced three RPGs in the first year}}; {{xt|The Starfinder RPG was officially supported by three dozen 3PPs in 2009}}. As with other nouns, do not add an apostrophe unless the form is a possessive.

=== Periods (full stops) and spaces ===
Acronyms and initialisms are generally not separated by full stops (periods) or blank spaces: ({{xt|PFRPG}}, {{xt|PFS}}, {{xt|LLC}}). Periods and spaces that were traditionally required have now dropped out of usage; ({{xt|PhD}} is now preferred over {{xt|Ph.D.}} and {{xt|Ph.&nbsp;D.}}). Full stops (periods) are not used in units of measurement.

=== Do not invent abbreviations or acronyms ===
Avoid creating new abbreviations or acronyms that might only see use on StarfinderWiki.
<!-- This link is dead. 
The sole exception is to shorten a work's title in a table. Refer to the [[StarfinderWiki:title acronym key|]] for guidelines when creating title acronyms.
-->
== Italics == <!-- 
* Completed. SEE NOTES. -Yoda8myhead, 5/22/09 
* Refreshed with in-world examples. -Oznogon, 7/26/15
-->
=== Emphasis ===
Use ''italics'' sparingly to emphasize words in sentences, and avoid ever using '''boldface''' for this purpose. Generally, the more highlighting in an article, the less the effect of each instance.

=== Titles ===
Italics are used for the titles of works of literature and art, such as books, paintings, films (feature-length), television series, and musical albums. The titles of articles, chapters, songs, television episodes, short films, and other short works are not italicized, but are enclosed in double quotation marks. This applies equally to in-setting and real-world uses.

Do not italicize major revered real-world religious works, such as {{xt|the Bible}}, {{xt|the Qur'an}}, and {{xt|the Talmud}}). However, you should italicize in-world religious works as you would any other book.

=== Words as words ===
Italics are used when mentioning a word or letter, or a string of words up to a full sentence: {{xt|The most commonly used letter in English is ''e''}}. 

For a whole sentence, you can use quotation marks instead: {{xt|The preposition in ''She sat on the chair'' is ''on''}}, or {{xt|The preposition in "She sat on the chair" is "on"}}. 

Mentioning&mdash;to discuss such features as grammar, wording, and punctuation&mdash;is different from quoting, in which something is usually expressed on behalf of a quoted source.

=== Foreign words ===
StarfinderWiki prefers italics for phrases in other languages and for isolated foreign words that are not commonly used in everyday English (or [[Taldane]], for articles written in the [[StarfinderWiki:Point of view|in-world POV]].) For example, {{xt|the native Shoanti called the river ''Mashkapikki''}}.

==== Italics and quotations ====
For quotations, use only quotation marks for short quotations or [[Template:Quote|block quoting]] for long ones. Do not manually apply italics; short quotations should not be italicized, and the {{xt|Quote}} template automatically italicizes its contents. (See [[#Quotations|Quotations]] below.) 

==== Italics within quotations ====
Italics are used within quotations if they are already in the source material, or are added by a chronicler to emphasize to some words. If the latter, an editorial note {{xt|[emphasis added]}} should appear at the end of the quotation: {{xt2|"Now cracks a noble heart. Good night sweet prince: And ''flights of angels'' sing thee to thy rest" [emphasis added].}}

If the source uses italics for emphasis, and it is desirable to stress that StarfinderWiki has not added the italics, the editorial note {{xt|[emphasis in original]}} should appear after the quote.

==== Effect on nearby punctuation ====
Italicization is restricted to what should properly be affected by italics, and not the punctuation that is part of the surrounding sentence.

{| style="background: transparent;"
|-
| valign=top           | ''Incorrect'':&nbsp; &nbsp;
| colspan=2            | {{xt|What are we to make of ''that?''}}
|-
| valign=top rowspan=2 | ''Correct'':
| colspan=2            | {{xt|What are we to make of ''that''?}}
|-
| &nbsp; &nbsp; &nbsp;
| (Note the difference between {{xt|''?''}} and {{xt|?}}.  The question mark applies to the whole sentence, not just to the emphasized {{xt|that}}.)
|-
| valign=top rowspan=2 | ''Correct'':
| colspan=2            | {{xt|Three of Ailson Kindler's most famous novels are ''Bleak Heart'', ''Galdyce's Guest: Feast of the Nosferatu'', and ''In the Council of Corpses''.}}
|-
|
| (The commas, period, and {{xt|and}} are not italicized.)
|}

==== Italicized links ====
You cannot place italics markup inside a link's markup or the link will not work. However, you can apply internal italicization in [[Wikipedia:piped link|piped link]]s.

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':&nbsp; &nbsp; || {{xt|The novel <code><nowiki>[[''In the Council of Corpses'']]</nowiki></code> is her best.}}
|- valign=top
| ''Correct'':                || {{xt|The novel <code><nowiki>''[[In the Council of Corpses]]''</nowiki></code> is her best.}}
|- valign=top
| ''Correct'':                || {{xt|The <code><nowiki>[[Burnt Saffron|''Burnt Saffron'']]</nowiki></code> is a slave galley.}}
|}

== Non-breaking spaces == <!-- 
* Completed. -Yoda8myhead, 5/22/09
* Refreshed with more relevant examples. -Oznogon, 7/26/15
-->
A non-breaking space (also known as a ''hard space'') is recommended to prevent the end-of-line displacement of elements that could be awkward at the beginning of a new line:

* In many compound expressions in which figures and abbreviations or symbols are separated by a space: ({{xt|17&nbsp;ft.}}, {{xt|565&nbsp;AR}}, {{xt|2:50&nbsp;p.m.}}).
* In other places where displacement might be disruptive to the reader or within the titles of works, such as {{xt|11&nbsp;billion&nbsp;gold}}, {{xt|''create&nbsp;water''}}, or {{xt|''Ultimate&nbsp;Magic''}}, or within elements in an [[:Category:Infoboxes|infobox]] or [[:Category:Content templates|content template]].
* A hard space can be produced with the HTML code <code>&amp;nbsp;</code> instead of the space bar: <code>17&amp;nbsp;ft.</code> yields a non-breaking {{xt|17&nbsp;ft.}}.
* Unlike normal spaces, multiple hard spaces are not compressed by browsers into a single space.

== Quotations == <!--
* Refreshed with more relevant examples. Removed prohibition against linking within quotes as we almost always do so for product articles. Updated block quote advice. -Oznogon, 7/26/15
-->
{{see also|#Italics and quotations|#Quotation marks|l1=Italics and quotations|l2=Quotation marks}}
=== Minimal change ===
Wherever reasonable, preserve the quote's original style, spelling, and punctuation. Where there is a good reason not to do so, insert an editorial explanation of the changes, usually within square brackets (''e.g.'', {{xt|[for example]}}).  If there is an error in the original statement, use {{xt|[''[[Wikipedia:sic]]'']}} to show that the error was not made in transcription.

=== Allowable changes ===
Though the requirement for minimal change is strict, you should alter a few merely typographical elements of the quoted text to conform to StarfinderWiki conventions, and can do so  without comment. Such a practice is universal in all publishing. Such alterations include:

* Styling dashes: Use the style chosen for the article: unspaced em dash or spaced en dash; see [[#Dashes|Dashes]], below.
* Styling apostrophes and quotes: They should all be straight, not curly; see [[#Quotation marks|Quotation marks]], below. Typographical elements as [[Wikipedia:guillemets|guillemets]] ({{xt|«&nbsp;»}} in quoted French, Portuguese, and other foreign-language material should be altered to their English-language equivalents (guillemets become standard straight quote marks, for example).
* Spaces before periods, colons, semicolons, and the like: Remove them, since they are merely typographical and unused in wikitext, or in English-language publishing in general.
* Some text styling: StarfinderWiki's software automatically applies default typefaces to all content, but you should preserve and convert bold, underlining, and italics per our standards. See [[#Italics|Italics]], above.
* [[#Ellipses|Ellipses]]: Use whenever parts of a quotation are skipped, for instance to remove extraneous, irrelevant, or parenthetical words or skip over unintelligible or guttural speech: {{xt|umm}}, {{xt|ahhs}}, and {{xt|hmms}}, for example. Take care not to use ellipses to remove context or  selectively quote to change the meaning of the quote, as is sometimes seen in advertisements that selectively quote critical reviews to make them appear more favorable.

=== Quotations within quotations ===
When a quotation includes another quotation, start with double quote marks outermost, and working inward, alternate single with double quote marks. 

The following example has three levels of quotation: {{xt|"She disputed his statement that 'Voltaire never said "I disapprove of what you say, but I will defend to the death your right to say it."'"}} 

=== Attribution ===
The author of a quote of a full sentence or more should be named; this is done in the main text and not in a footnote. However, attribution is unnecessary for quotations from the subject of the article or section. To attribute a quote in a {{tl|Quote}} block quotation template, use the '''speaker''' parameter. 

==== Block quotations ====
Format a long quote of more than four lines (or more than one paragraph, regardless of number of lines) as a block quotation using the {{tl|Quote}} template. Do not enclose block quotations with quotation marks.

<pre>
{{Quote
| quote = Order is everything, at any cost.
| speaker = ''[[Ultimate Campaign]]'', page 136
}}
</pre>

{{Quote
| quote = Order is everything, at any cost.
| speaker = ''[[Ultimate Campaign]]'', page 136
}}

== Punctuation ==
=== Apostrophes === <!-- 
* Done, removed some overly specific stuff. -aeakett, 5/22/09 
* Internal consistency on italicizing section links. -Oznogon, 7/26/15
-->
* Consistent use of the straight (or ''typewriter'') apostrophe ({{xt|&nbsp;<big>'</big>&nbsp;}}) is recommended, as opposed to the curly (or ''typographic'') apostrophe ({{xt|&nbsp;<big>’</big>&nbsp;}}). For details and reasons, see ''[[#Quotation marks|Quotation marks]]'', below.
* For the possessive apostrophe, see the summary of usage issues at ''[[#Possessives|Possessives]]'', below.

=== Quotation marks === <!-- 
* Done. -aeakett, 05/22/09
* Removed outdated issue with single-quoted text in searches. -Oznogon, 7/26/15
-->
{{see also|#Quotations|l1=Quotations}}
The term ''quotation'' in the material below also includes other uses of quotation marks, such as those for titles of songs, chapters, and episodes; unattributable aphorisms; "scare-quoted" passages; and constructed examples.

==== Double or single ====
Quotations are enclosed within double quotes (''e.g.'', {{xt|Cayden said, "Valeros! You haven't drunk enough this morning."}}). 

Quotations within quotations are enclosed within single quotes (''e.g.'', {{xt|Kyra said, "Did you pretend to be Cayden Cailean and tell Valeros, 'You haven't drunk enough' before breakfast?}}).

==== Inside or outside ====
Punctuation marks are placed inside the quotation marks only if the sense of the punctuation is part of the quotation. This practice is referred to as ''logical quotation''; it is used by StarfinderWiki both because of the principle of minimal change, and also because the method is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing.

{| style="background: transparent;"
| rowspan=2 valign=top | ''Correct'': || {{xt|Ezren said, "Valeros is deplorable and unacceptable."}}
|-
| (The period is part of the quoted text.)
|-
| rowspan=2 valign=top | ''Correct'': || {{xt|Ezren said Valeros was "deplorable".}}
|-
| (The period is not part of the quoted text.)
|-
| rowspan=2 valign=top | ''Correct'': || {{xt|Merisiel asked, "Are you leaving?"}}
|-
| (The question mark belongs inside because the quoted text itself was a question.)
|-
| rowspan=2 valign=top | ''Correct'': || {{xt|Did Merisiel say, "Get out"?}}
|-
| (The very quote is being questioned, so the question mark belongs outside; any punctuation at the end of the original quote is omitted.)
|}

When quoting a sentence fragment that ends in a period, some judgment is required: if the fragment communicates a complete sentence, the period can be placed inside. The period should be omitted if the quotation is in the middle of a sentence.

{| style="background: transparent;"
| ''Correct'': || {{xt|Merisiel said, "Go away", and they did.}}
|}

If the sequence of juxtaposed punctuation marks seems distracting or untidy, try to obviate it.

{| style="background: transparent;"
| ''Correct'': || {{xt|Merisiel said, "Go away" (and they did).}}
|}

==== Article openings ====
When the title of an article appearing in the lead paragraph requires quotation marks (for example, the title of a song or poem), do not boldface the quotation marks, as they are not part of the title:

{| style="background: transparent;"
| ''Correct'': || {{xt|"'''Crisis of Faith'''" is a short story by Michael J. Martinez.}}
|}

==== Block quotes ====
As already noted [[#Quotations|above]], we use quotation marks or block quotes (not both) to distinguish long quotations from other text. Multi-paragraph quotations are always block-quoted. The quotations must be precise and exactly as in the source, and the source should be cited clearly and precisely to help readers find the text that supports the article content in question.

==== Quotation characters ====
The following types of quoting should not be used:

* Grave and acute accents or backticks ({{xt|<big>'''`'''</big>text<big>'''´'''</big>}}) are neither quotation marks nor apostrophes, and must not be used in their place.
* There have traditionally been two styles concerning the look of the quotation marks (that is, the glyph):
* Typewriter or straight style: {{xt|<big >'''"'''</big >text<big >'''"'''</big >, <big ><b >'</b ></big >text<big ><b >'</b ></big >.}} '''Recommended.'''
* Typographic or curly style: {{xt|<big >'''“'''</big >text<big >'''”'''</big>, <big >'''‘'''</big >text<big >'''’'''</big >.}} '''Not recommended.'''

StarfinderWiki recommends exclusively using straight quotes and apostrophes (see [[#Apostrophes|preceding section]]), which are easier to type and edit. Mixed use interferes with some searches, such as those using the browser's search facility (a search for {{xt|Droskar's Crucible}} could fail to find {{xt|Droskar’s Crucible}}, and vice versa).

When quotation marks or apostrophes appear in article titles, you can make a [[Help:redirect|redirect]] from the same title using the alternative glyphs.

==== Other matters ====
* A quotation is not italicized simply because it is a quotation.
* If an entire sentence is quoted in such a way that it becomes a grammatical part of the larger sentence, the first letter loses its capitalization: {{xt|It turned out to be true that "a copper saved is a copper earned".}}

=== Brackets and parentheses === <!--
* Done. -Yoda8myhead, 5/26/09
-->
These rules apply to both round brackets (&nbsp;{{xt|(&nbsp;)}}&nbsp;), often called parentheses, and square brackets (&nbsp;{{xt|[&nbsp;]}}&nbsp;).

If a sentence contains a bracketed phrase, place the sentence punctuation outside the brackets {{xt|(as shown here).}} However, where one or more sentences are wholly inside brackets, place their punctuation inside the brackets (see ''[[#Sentences and brackets|Sentences and brackets]]'' below). There should be no space next to a bracket's inner side. An opening bracket should be preceded by a space except in unusual cases; for example, when it is preceded by:

* An opening quotation mark: {{xt2|He rose to address the meeting: "(Ahem)&nbsp;... Ladies and gentlemen, welcome!"}}
* Another opening bracket: {{xt2|Only the royal characters in the play ([Prince] Hamlet and his family) habitually speak in blank verse.}}
* A portion of a word: {{xt2|We journeyed on the Inter[continental].}}

There should be a space after a closing bracket, except where another punctuation mark (other than an apostrophe or a dash) follows, and in unusual cases similar to those listed for opening brackets.

If sets of brackets are nested, use different types for adjacent levels of nesting; for two levels, it is customary to have square brackets appear within round brackets. This is often a sign of excessively convoluted expression, and it is often better to recast, linking the thoughts with commas, semicolons, colons, or dashes.

Avoid adjacent sets of brackets. Either put the parenthetic phrases in one set separated by commas, or rewrite the sentence. For example:

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;|| {{xt|Zenobia (Zena) Zenderholm (Senior arbiter) (also known as the "Hanging Judge" of the Varisian city of Korvosa) is of House Zenderholm.}}
|- valign=top
| ''Correct'':               || {{xt|Senior arbiter Zenobia "Zena" Zenderholm, of House Zenderholm, is also known as the "Hanging Judge" of the Varisian city of Korvosa.}}
|- valign=top
| ''Correct'':               || {{xt|Senior arbiter Zenobia "Zena" Zenderholm, also known as the "Hanging Judge" of the Varisian city of Korvosa, is of House Zenderholm.}}
|}

Square brackets are used to indicate editorial replacements and insertions within quotations. They serve three main purposes:

* To clarify. ({{xt|"She attended [secondary] school"}}&mdash;where this was the intended meaning, but the type of school was unstated by the original speaker.)
* To reduce the size of a quotation. If a source says, {{xt|"X contains Y, and under certain circumstances, X may contain Z as well"}}, it is acceptable to reduce this to {{xt|"X contains Y [and sometimes Z]"}}, without ellipsis. When an ellipsis ({{xt|...}}; see [[#Ellipses|below]]) is used to indicate material removed from a direct quotation, it should not normally be bracketed.
* To make the grammar work: {{xt|She said that "[she] would not allow this"}}&mdash;where her original statement was "{{xt|I would not allow this}}". (Generally, though, it is better to begin the quotation after the problematic word: {{xt|She said that she "would not allow this."}})

The use of square-bracketed wording should never alter the intended meaning of a quotation.

==== Sentences and brackets ==== <!--
* Updated examples. -Oznogon, 7/28/15
-->
If any sentence includes material that is enclosed in square or round brackets, it still must end&mdash;either with a period, question mark, or exclamation mark&mdash;''after'' those brackets. This principle applies no matter what punctuation is used within the brackets.

However, if the entire sentence is within brackets, the closing punctuation falls within the brackets. This does not apply to matter that is added (or modified editorially) at the beginning of a sentence for clarity, which is usually in square brackets: {{xt|"[Venture-Captain Dreng] already told me that", he objected}} in preference to the potentially more ambiguous {{xt|"He already told me that", he objected.}}

A sentence that occurs within brackets in the course of another sentence does not generally have its first word capitalized just because it starts a sentence. The enclosed sentence may have a question mark or exclamation mark added, but not a period: {{xt|Taldor then conquered (who would have believed it?) most of the known world}}; {{xt|Kyra demanded that he attack (she knew he hated fighting) in the coliseum}}. It is often clearer to separate the thoughts into separate sentences or clauses: {{xt|Taldor then conquered most of the known world. Who would have believed it?}} or {{xt|Kyra demanded that he fight in the coliseum; she knew he hated fighting.}}

=== Ellipses === <!-- 
* Done. -aeakett, 5/22/09
* Minor changes and a typo fix. -Oznogon, 7/28/15
-->
An ellipsis (plural ''ellipses'') is an omission of material, often used in a printed record of conversation. The ellipsis is represented by '''ellipsis points''': a set of three dots.

==== Style ====
Ellipsis points, or ''ellipses'', have traditionally been implemented in three ways:

* ''Three unspaced periods'' ({{xt|...}}). This is the easiest way, and gives a predictable appearance in HTML. '''Recommended.'''
* ''Pre-composed ellipsis character'' ({{xt|…}}); generated with the <code>&amp;hellip;</code> character entity, or as a literal "…". This is harder to input and edit, and too small in some fonts. '''Not recommended''', but used in some places (such as "[[StarfinderWiki:Did you know|Did you know]]" lists) to save space.
* ''Three spaced periods'' ({{xt|.&nbsp;.&nbsp;.}}). This is an older style that is unnecessarily wide and requires non-breaking spaces to keep it from breaking at the end of a line. '''Not recommended.'''

==== Function and implementation ====
Use an ellipsis if material is omitted in the course of a quotation, unless square brackets are used to gloss the quotation (see [[#Brackets and parentheses|above]], and points below).

* Put a space on each side of an ellipsis, except that there should be no space between an ellipsis and:
** a quotation mark, where the ellipsis is on the inside.
** a parenthesis or a bracket, where the ellipsis is on the inside.
** sentence-final punctuation, or a colon, semicolon, or comma (all rare), following the ellipsis.
* Sentence-final punctuation after an ellipsis is shown only if it is textually important (as is often the case with exclamation points and question marks, and rarely with periods).
* Use non-breaking spaces (<code>&amp;nbsp;</code>) only as needed to prevent improper line breaks, ''e.g.'':
** To keep a quotation mark from being separated from the start of the quotation: {{xt|"...<code>&amp;nbsp;</code>we are still worried."}}
** To keep the ellipsis from wrapping to the next line: {{xt|"Andoran, Taldor,<code>&amp;nbsp;</code>... and Osirion but not Cheliax."}}

Three periods (loosely also called ''ellipsis points'') can represent a pause in or suspense of speech, in which case the punctuation is retained in its original form ({{xt|Merisiel's startled reply was: "Could he&nbsp;...? No, I cannot believe it!"}}). Avoid this usage except in direct quotations.

==== With square brackets ====
An ellipsis does not need square brackets around it, since its function is usually obvious&mdash;especially if the guidelines above are followed. Square brackets, however, can optionally clarify that the ellipsis is not itself quoted; this is usually only necessary if the quoted passage also uses three periods in it to indicate a pause or suspension. The ellipsis should follow exactly the principles given above, but with square brackets inserted immediately before and after it. ({{xt|Her long rant continued: "How do I feel? How do you ''think'' I&nbsp;... look, this has gone far enough!&nbsp;[...] I want to go home!"}})

=== Commas === <!-- 
* Done. -aeakett, 05/22/09
-->
Commas are the most frequently used punctuation marks, but also the most difficult to use well. Some important points are made at ''[[#Semicolons|Semicolons]]'', below. Other points include these:

A pair of commas is often used for parenthetic material, and it interrupts the sentence less than parentheses (brackets) or dashes. Sometimes other punctuation can mask the need for a comma, especially for the second in such a pair when parentheses are also used.

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':           || {{xt|The Starfinders, fed by local goblins (on fireworks, and fish) survived for a few hours.}}
|- valign=top
| ''Correct'':&nbsp; &nbsp;|| {{xt|The Starfinders, fed by local goblins (on fireworks, and fish), survived for a few hours.}}
|}

A comma is very rarely correct immediately before an opening parenthesis.

Modern practice avoids excessive comma use. You can often simplify a sentence to use fewer commas.

{| style="background: transparent;"
|- valign=top
| ''Awkward'':                 || {{xt|Valeros was, along with the Dalsines, both Colson and Gaspar, and also Harsk, one of Lubor's heroes.}}
|- valign=top
| ''Much better'':&nbsp; &nbsp;|| {{xt|Lubor's heroes included Valeros, Harsk, and Colsoen and Gaspar Dalsine.}}
|}

==== Serial commas ====
A serial comma (also known as an ''Oxford comma'' or ''Harvard comma'') is a comma used immediately before a conjunction in a list of three or more items: the phrase {{xt|ham, chips, and eggs}} contains a serial comma, while the variant {{xt|ham, chips and eggs}} omits it. 

Both styles are acceptable in StarfinderWiki as long as one is consistently used within an article. However, whenever including or omitting the comma clarifies the meaning of the sentence, that solution should be adopted.

Sometimes omitting the comma can lead to an ambiguous sentence, as in this example:

{{xt|The author thanked her parents, Sister Bethany and Mayor Camden}}, which may list either four people (the two parents and the two people named) or two people (Bethany and Camden, who are the parents).

Including the comma can also cause ambiguity, as in:

{{xt|The author thanked her mother, Sister Bethany, and Mayor Camden}}, which may list either two people (Bethany, who is the mother, and Camden) or three people (the first being the mother, the second Bethany, and the third Camden).

In such cases of ambiguity, there are three ways to clarify:

* Use or omit the serial comma to avoid ambiguity.
* Recast the sentence.
* Format the list, perhaps with paragraph breaks and numbered paragraphs.

Recasting example one:

* To list four people: {{xt|The author thanked Mayor Camden, Sister Bethany, and her parents.}}
* To list two people (the commas here set off non-restrictive appositives): {{xt|The author thanked her father, Mayor Camden, and her mother, Sister Bethany.}}

Recasting example two:

* To list two people: {{xt|The author thanked Mayor Camden and her mother, Sister Bethany.}}
* To list three people: {{xt|The author thanked her mother, Mayor Camden, and Sister Bethany}}

Note that the last example's being clear depends on the reader knowing that Mayor Camden is male and cannot be a mother. If we change the example slightly, we are back to an ambiguous statement: {{xt|The author thanked her mother, Governor Mary Maldris, and Sister Bethany.}}

Recasting again:

* To list three people: {{xt|The author thanked Governor Mary Maldris, Sister Bethany, and her mother.}}

=== Colons === <!--
* Done. -aeakett, 05/22/09
-->
A colon ({{xt|:}}) informs the reader that what comes after it proves, explains, or modifies what has come before, or leads a list of items. You can separate the items in such a list with commas. If list items are more complex and perhaps themselves contain commas, the items should be separated by semicolons:

{{xt|We toured several buildings around the town: the Glassworks, which was far hotter than I imagined; the theater; The Hagfish, where I tried a mug of Norah's tank water; and so many more.}}

A colon can also introduce direct speech enclosed within quotation marks (see [[#quotation marks|above]]).

A colon should normally have a complete grammatical sentence before it, except sometimes when it introduces items set off in new lines like the very next colon here. For instance:

{| style="background: transparent;"
|- valign=top
| ''Correct'':                            ||{{xt|He attempted it in two years: 4681 AR and 4683 AR.}}
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;             ||{{xt|The years he attempted it included: 4681 AR and 4683 AR.}}
|- valign=top
| ''Correct (special case)'':&nbsp; &nbsp;||{{xt|Boggard, Shoanti, Chelaxian: these are but a few of the languages you might hear on your travels through Varisia.}}
|}

Sometimes, more in American than British usage, the word following a colon is capitalized if that word effectively begins a new grammatical sentence, and especially if the colon serves to introduce more than one sentence:

{{xt|The argument is easily stated: We have been given only three tickets. There are four of us here: you, the twins, and me. The twins are inseparable. Therefore, you or I will have to stay home.}}

No sentence should contain more than one colon.

=== Semicolons === <!-- 
Done. -aeakett, 05/22/09
-->
A semicolon ({{xt|;}}) is sometimes an alternative to a full stop (period), enabling related material to be kept in the same sentence; it marks a more decisive division in a sentence than a comma. If it separates clauses, they are usually independent; often, only a comma or only a semicolon will be correct in a given sentence. 

{| style="background: transparent;"
|- valign=top
| ''Correct'':               || {{xt|Though he had been here before, I did not recognize him.}}
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;|| {{xt|Though he had been here before; I did not recognize him.}}
|- valign=top
| ''Correct'':               || {{xt|Efreet are aligned with elemental fire; djinn are classified as air.}}
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;|| {{xt|Efreet are aligned with elemental fire, djinn are classified as air.}}
|}

In very rare cases, a comma may be used where a semicolon would seem to be called for:

{| style="background: transparent;"
|- valign=top
| ''Accepted'':               || {{xt|"Life is short, art is long."}} (citing a brief aphorism)
|- valign=top
| ''Accepted'':               || {{xt|"I have studied it, you have not."}} (reporting brisk conversation)
|}

A semicolon does not force a capital letter in the word that follows it. 

A sentence can contain several semicolons, especially when the clauses are parallel. Multiple unrelated semicolons are often signs that the sentence should be divided into shorter sentences, or otherwise refashioned.

{| style="background: transparent;"
|- valign=top
| ''Unwieldy'':                   || {{xt|Efreet are aligned with elemental fire; djinn are classified as air; shaitan are said to be of earth; these classifications are fundamental to their natures.}}
|- valign=top
| ''One better way'':&nbsp; &nbsp;|| {{xt|Efreet are aligned with elemental fire, djinn are air, and shaitan are earth; these classifications are fundamental to their natures.}}
|}

=== Hyphens === <!--
* Done -aeakett, 05/22/09
-->
Hyphens ({{xt|-}}) indicate conjunction. There are three main uses:

* To distinguish between '''homographs'''. {{xt|Re-dress}} means ''dress again'', but {{xt|redress}} means ''remedy'' or ''set right''.
* To link certain '''prefixes''' with their main word. {{xt|Non-linear}}, {{xt|sub-section}}, {{xt|super-achiever}}.
** There is a clear trend to join both elements in all varieties of English ({{xt|subsection}}, {{xt|nonlinear}}), particularly in American English. British English tends to hyphenate when the letters brought into contact are the same ({{xt|non-negotiable}}, {{xt|sub-basement}}) or are vowels ({{xt|pre-industrial}}), or where a word is uncommon ({{xt|co-proposed}}, {{xt|re-target}}) or may be misread ({{xt|sub-era}}, not {{xt|subera}}). American English reflects the same factors, but tends to close up without a hyphen when possible. Consult a good dictionary.
* To link related terms in '''compound adjectives and adverbs''':
** A hyphen can help with ease of reading ({{xt|face-to-face discussion}}, {{xt|hard-boiled egg}}); a hyphen is particularly useful in long nominal groups where non-experts are part of the readership.
** A hyphen can help to disambiguate ({{xt|little-celebrated paintings}}, not a reference to little paintings).
** Many compound adjectives that are hyphenated when used attributively (before the noun they qualify—{{xt|a light-blue handbag}}), are not hyphenated when used predicatively (after the noun—{{xt|the handbag was light blue}}); this attributive hyphenation also occurs in proper names, such as  {{xt|Great Black-backed Gull}}. Where there would be a loss of clarity, the hyphen may be used in the predicative case too ({{xt|hand-fed turkeys}}, {{xt|the turkeys were hand-fed}}). 
** A hyphen is not used after a standard {{xt|-ly}} adverb ({{xt|a newly available home}}, {{xt|a wholly owned subsidiary}}) unless part of a larger compound ({{xt|a slowly-but-surely strategy}}). Some words ending in {{xt|-ly}} function as both adverbs and adjectives ({{xt|a friendly-looking butcher}}, the natives used us friendly and with kindness). Some such dual-purpose words (like {{xt|early}}, {{xt|only}}, {{xt|northerly}}) are not standard {{xt|-ly}} adverbs, since they are not formed by addition of {{xt|-ly}} to an independent current-English adjective. These need careful treatment: {{xt|Early flowering plants evolved along with sexual reproduction}}, but {{xt|Early-flowering plants risk damage from winter frosts}}; {{xt|northerly-situated islands}}.
** A hyphen is normally used when the adverb {{xt|well}} precedes a participle used attributively ({{xt|a well-meaning gesture}}; but normally {{xt|a very well managed shop}}, since {{xt|well}} itself is modified); and even predicatively, if {{xt|well}} is necessary to, or alters, the sense of the adjective rather than simply intensifying it ({{xt|the gesture was well-meaning}}, {{xt|the child was well-behaved}}, but {{xt|the floor was well polished}}).
** A ''hanging hyphen'' is used when two compound adjectives are separated ({{xt|two- and three-digit numbers}}, {{xt|a ten-camel or -mule convoy}}, {{xt|sloping right- or leftward}}, but better is {{xt|sloping rightward or leftward}}). 
** Values and units used as compound adjectives are hyphenated only where the unit is given as a whole word. Where hyphens are not used, values and units are always separated by a non-breaking space (<code>&amp;nbsp;</code>).

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':             || {{xt|9-in. gap}}
|- valign=top
| ''Correct'':               || {{xt|9&nbsp;in. gap}} (entered as <code>9&amp;nbsp;in. gap</code>)
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;|| {{xt|9&nbsp;inch gap}}
|- valign=top
| ''Correct'':               || {{xt|9-inch gap}}
|- valign=top
| ''Correct'':               || {{xt|12-hour shift}}
|- valign=top
| ''Correct'':               || {{xt|12&nbsp;h shift}}
|}

; Multi-hyphenated items: It is often possible to avoid multi-word hyphenated adjectives by rewording ({{xt|a three-headed dog}} may be easier to read as {{xt|a dog with three heads}}). This is particularly important where converted units are involved ({{xt|the 6-hectare-limit (14.8-acre-limit) rule}} might be possible as {{xt|the rule imposing a limit of 6 hectares (14.8 acres)}}, and the ungainly {{xt|4.9-mile (7.9&nbsp;km) -long tributary}} as simply {{xt|4.9-mile (7.9&nbsp;km) tributary}}). 

; Spacing: A hyphen is never followed or preceded by a space, except when hanging (see above) or when used to display parts of words independently, such as the prefix {{xt|sub-}} and the suffix {{xt|-less}}.

; Minus signs: Do not use a hyphen ({{xt|-}}) as a minus sign ({{xt|&minus;}}), except in code (see [[#En dashes|below]]).

; Image filenames and redirects: A hyphen is used only to mark conjunction, not disjunction (for which en dashes are used: see below). An exception is in image filenames, where the ability to type the URL becomes more important (see ''[[#Dashes|Dashes]]'' below). Article titles with dashes should have a corresponding redirect from the title with hyphens: for example, {{xt|[[Michelson-Morley experiment]]}} redirects to {{xt|[[Michelson–Morley experiment]]}}, as the latter title, while correct, is harder to search for.

Hyphenation involves many subtleties that cannot be covered here; the rules and examples presented above illustrate the broad principles that inform current usage.

=== Dashes === <!--
* Done (whole section). -aeakett, 05/23/09
-->
StarfinderWiki uses two kinds of dashes: '''en dashes''' and '''em dashes'''. The article on [[Wikipedia:Dash#Rendering dashes on computers|dashes]] shows common input methods for these. 

Dashes should never be used in image and media filenames; use hyphens instead. If used in an article's title, there should be a redirect from the version with a hyphen.

==== En dashes ==== <!--
* Done. -aeakett, 05/24/09
* Refreshed and updated. -Oznogon, 7/26/15
-->
En dashes ({{xt|–}}) have three distinct roles:

# To indicate '''disjunction'''. In this role, there are two main applications.
#* To convey the sense of ''to'' or ''through'', particularly in ranges ({{xt|pp. 211–19}}, {{xt|64–75%}},  {{xt|Desnus–Rova}}) and where movement is involved ({{xt|Sandpoint–Magnimar route}}). The word {{xt|to}}, rather than an en dash, is used when a number range involves a negative value or might be misconstrued as a subtraction ({{xt|&minus;3 to 1}}, not {{xt|&minus;3–1}}). This is also the case when the nearby wording demands it, ''e.g.'', {{xt|he served from 4682 AR to 4685 AR}} and not {{xt|he served from 4682–4685}}, in which {{xt|from}} and {{xt|to}} are complementary and should both be spelled out.
#* As a substitute for some uses of {{xt|and}}, {{xt|to}}, or {{xt|versus}} for marking a relationship involving independent elements in certain compound expressions ({{xt|Osirion–Katapesh border}}, {{xt|the quillions mark the hilt-blade transition}}, {{xt|3–2 win in the jousting final}}, {{xt|male–female ratio}}, {{xt|3–2 majority verdict}})
#** ''Spacing:'' All disjunctive en dashes are unspaced, except when there is a space within either one or both of the items ({{xt|the Mwangi Expanse – Osiron trade route}}; {{xt|Desnus 3, 4682 – Rova 18, 4685}}, but {{xt|Desnus–Rova 4682}}).
# As a '''stylistic alternative to em dashes''' ([[#Em dashes|see below]]).

===== Minus signs ===== <!--
* Note exemption for years. -~~~~
-->
Do not use an en dash for negative signs and subtraction operators: use the correct Unicode character for the minus sign ({{xt|<nowiki>&amp;minus;</nowiki>}}). Negative signs ({{xt|&minus;8&nbsp;°F}}) are unspaced; subtraction operators ({{xt|42&nbsp;&minus;&nbsp;4&nbsp;<nowiki>=</nowiki>&nbsp;38}}) are spaced. Note that this is in opposition to Paizo style, which uses en dashes for minus signs.

Due to the large number of articles on years which begin with hyphens instead of minus signs, use hyphens when referring to years.

==== Em dashes ==== <!--
* Done. -aeakett, 05/23/09
* Refreshed and updated. -Oznogon, 7/26/15
-->
Em dashes ({{xt|—}}) indicate interruption in a sentence. They should not be spaced.

Em dashes fill two roles:

# '''Parenthetical''' ({{xt|StarfinderWiki&mdash;one of the most popular Starfinder fan web sites&mdash;has the information you need}}). A pair of em dashes for such interpolations is more arresting than a pair of commas, and less disruptive than parentheses (round brackets).
# '''As a sharp break''' in the flow of a sentence&mdash;sharper than is provided by a colon or a semicolon.

In both roles, em dashes are useful where there are already several commas. Em dashes can clarify the structure, sometimes removing ambiguity. 

Use em dashes sparingly. They are visually striking, so using no more than two in a paragraph is often a good limit. Avoid two "sharp break" em dashes in a sentence, since they are readily mistaken for a parenthetic pair. Do not use ''more'' than two em dashes in a single sentence: which two (if any) make a parenthetic pair? 

Do not use an em dash for a minus sign. (See ''[[#Minus signs|Minus signs]]''.)

===== Spaced en dashes as an alternative to em dashes =====
Spaced en dashes &ndash; such as here &ndash; can be used instead of unspaced em dashes in all of the ways discussed above. Spaced en dashes are used by several major publishers, to the complete exclusion of em dashes. Whichever style you choose, use it consistently throughout an article.

==== Other dashes ==== <!--
* Done --aeakett 05/23/09
-->
StarfinderWiki avoids using other types of dashes, especially two consecutive hyphens ({{xt|--}}).

=== Slashes === <!-- 
* Done. -Yoda8myhead, 5/26/09
-->
Avoid joining two words by a slash, also known as a forward slash ({{xt|&nbsp;/&nbsp;}}). It suggests that the two are related, but does not specify how. It is often also unclear how the construct would be read aloud. Replace the structure with clearer wording.

{| style="background: transparent;"
|- valign = top
| ''Incorrect'':             || {{xt|The soldier/healer must be present at all times.}}
|- valign = top
| ''Correct'':               || {{xt|The soldier and healer must be present at all times.}} (If two people.)
|- valign = top
| ''Correct'':               || {{xt|The soldier-healer must be present at all times.}} (If one person.)
|- valign = top
| ''Correct'':               || {{xt|The soldier who also tends their wounds must always be present.}} (If one person.)
|}

In circumstances involving a distinction or disjunction, the en dash (see [[#En dashes|above]]) is usually preferable to the slash, ''e.g.'', {{xt|the cleric–inquisitor distinction}}.

Never use the backslash character ({{xt|&nbsp;\&nbsp;}}) in place of a slash. 

==== And/or ====
The term {{xt|and/or}} is awkward. In general, where it is important to mark an inclusive {{xt|or}}, use {{xt|x or y, or both}}, rather than {{xt|x and/or y}}. For an exclusive {{xt|or}}, use {{xt|either x or y}}, and optionally add {{xt|but not both}} if it is necessary to stress the exclusivity. 

Where more than two possibilities are presented, from which a combination is to be selected, it is even less desirable to use {{xt|and/or}}. With two possibilities the intention is clear, but with more than two it may not be. Instead of {{xt|x, y, and/or z}}, use an appropriate alternative, such as {{xt|one or more of x, y, and z}}; {{xt|some or all of x, y, and z}}.

Sometimes {{xt|or}} is ambiguous in another way: {{xt|Wild dogs, or dingoes, inhabit this stretch of land}}. Are wild dogs and dingoes the same or different? For one case write: {{xt|wild dogs (dingoes) inhabit&nbsp;...}} (meaning dingoes ''are'' wild dogs); for the other case write: {{xt|either wild dogs or dingoes inhabit&nbsp;...}}.

=== Punctuation at the end of a sentence === <!--
* Done. -Yoda8myhead, 5/26/09
-->
'''Periods''' (referred to as ''full stops'' by most non-US English speakers), '''question marks''', and '''exclamation marks''' are the three ''sentence-enders'': the only punctuation marks used to end sentences. In some contexts, no sentence-ender should be used; in such cases, the sentence often does not start with a capital letter. See ''[[#Quotations|Quotations]]'', ''[[#Quotation_marks|Quotation marks]]'' and ''[[#Sentences_and_brackets|Sentences and brackets]]'', above.

For the use of three periods in succession, see ''[[#Ellipses|Ellipses]]'', above.

Clusters of question marks, exclamation marks, or a combination of them (such as the {{w|interrobang}}) are highly informal, and inappropriate in StarfinderWiki articles.

Use exclamation marks with restraint. It is an expression of surprise or emotion that is generally unsuited to an encyclopedic register.

Question marks and exclamation marks can sometimes be used in the middle of a sentence:

* {{xt|Why me? she wondered.}}
* {{xt|The question is not ''Did Paizo write the errata?'' but ''How did the errata come into being?'', as we have now come to realize.}}
* {{xt|The door flew open with a BANG! that made them jump.}} [Not encyclopedic, but acceptable in transcription from audio, or of course in direct quotation.]

Along with commas, semicolons, and colons, sentence-enders are never preceded by a space in normal prose.

There is no guideline on whether to use one space or two after the end of a sentence, but the issue is not important because the difference is visible only in edit boxes; that is, it is ignored by browsers when displaying the article. For consistency, StarfinderWiki prefers one space after sentence-ending punctuation.

=== Punctuation and inline citations === <!--
* Done. -Yoda8myhead, 5/26/09
* Updated example. -Oznogon, 7/26/15
-->
Place [[Help:Citing sources|inline citations]] ''after'' any punctuation, such as a comma or period, with no intervening space: 

<pre>
... are venomous.<ref>{{Cite book/Bestiary 4|123}}</ref>
</pre>

This yields {{xt|... are venomous.<small><sup>[<u>1</u>]</sup></small>''}}

See [[StarfinderWiki:Citing sources|Citing sources]] for general guidelines about referencing.

== Geographical items == <!--
* Done. -Yoda8myhead, 5/22/09
* Updated link. -Oznogon, 7/26/15
-->
{{see also|StarfinderWiki:Naming conventions}}
Refer to places consistently using the same name as in the title of their article. In general, this should also be consistent with the source material.

== Chronological items == <!--
* Completed. SOME ISSUES REMAIN, esp. re: the AR denotation for years and the lack of a BC-equivalent within the system. -Yoda8myhead, 5/22/09
-->
=== Precise language ===
Avoid statements that age quickly, like {{xt|recently}}, {{xt|soon}}, and {{xt|now}}, unless their meaning is fixed by the context. Avoid relative terms like {{xt|currently}} (usually redundant), {{xt|in modern times}}, {{xt|is now considered}}, and {{xt|is soon to be superseded}}. Instead, use either:

* more precise and absolute expressions ({{xt|since the start of 2005}}; {{xt|during the 4710s}}; {{xt|is expected to be superseded by 2008}}); or
* an {{xt|as of}} phrase ({{xt|as of August 2007}}), which signals the time-dependence of the statement and alerts later editors to update the statement.; or 
* simply use {{xt|at}} instead: {{xt|The population was over 21,000,000 (at December 2008)}}.

<!-- === Times ===
* These will rarely, if ever, be used in this wiki.  Do we keep this here?
* Excised. -Oznogon, 7/26/15
-->
=== Dates === <!-- 
* We have been inconsistent on this issue and should really do searches through the whole wiki for all months (both in-world and real world) to find discrepancies from new policy.
* Point to on-wiki resources. -Oznogon, 7/26/15
-->
StarfinderWiki does not use ordinal suffixes or articles. This applies to both publication and in-world points of view. For real-world dates, do not put a comma between the month and year.

{| style="background: transparent;"
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;||{{xt|February 14th, the 14th of February}}
|- valign=top
| ''Correct'':               ||{{xt|February 14}}
|- valign=top
| ''Incorrect'':             ||{{xt|October, 1976; October of 1976}}
|- valign=top
| ''Correct'':               ||{{xt|October 1976}}
|- valign=top
| ''Incorrect'':&nbsp; &nbsp;||{{xt|14th Kuthona, the 14th of Kuthona}}
|- valign=top
| ''Correct'':               ||{{xt|14 Kuthona}}
|- valign=top
| ''Incorrect'':             ||{{xt|Kuthona 4715; Kuthona of 4715}}
|- valign=top
| ''Correct'':               ||{{xt|Kuthona, 4715}}
|}

* Rarely, a night can be expressed in terms of the two contiguous dates using a slash ({{xt|the night of December 13/14, 2005}}).

==== Real-world dates ====
Because Starfinder is published by Paizo, which is based in the United States, StarfinderWiki maintains United States standards for date format. Thus, month should always precede real-world dates.

* Dates are not normally linked.
* Date ranges are preferably given with minimal repetition, using an unspaced en dash where the range involves numerals alone ({{xt|January 5–7, 2002}}) or a spaced en dash where opening and/or closing dates have internal spaces ({{xt|January 5 – February 18, 1979}}). 
* Yearless dates ({{xt|March 5}}) are inappropriate unless the year is obvious from the context, such as a repeating event.
* ISO 8601 dates (like {{xt|1976-05-13}}) are uncommon in English prose and are generally not used in StarfinderWiki. However, they may be useful in long lists and tables for conciseness and ease of comparison.

==== In-world dates ====
{{Main|StarfinderWiki:Canon policy#Regarding dates}}
[[Absalom Reckoning]] and [[Imperial Calendar]] dates follow a different format than real-world dates: the day of the week followed by a comma, then the numeric date and month, a comma, and the year suffixed with AR or IC, respectively. For example:

{| style="background: transparent;"
|- valign=top
| ''Correct'':&nbsp; &nbsp;|| {{xt|Moonday, {{Golariondate}}}}
|- valign=top
| ''Correct'':             || {{xt|{{Golariondate}}}}
|-
| ''Correct'':             || {{xt|[[Kuthona]], [[4715 AR]]
|}

=== Longer periods ===
Write '''months''' as whole words ({{xt|February}}, not {{xt|2}}). Use abbreviations such as {{xt|Feb}} only where space is extremely limited, such as in tables and infoboxes. Do not insert {{xt|of}} between a month and a year ({{xt|April 2000}}, not {{xt|April of 2000}}).

Because seasons differ on location and context, prefer neutral wording ({{xt|in early 1990}}, {{xt|in the second quarter of 2003}}, {{xt|around September}}) over "seasonal" references ({{xt|Summer 1918}}, {{xt|Spring 1995}}). Even when the season reference is unambiguous in context, a date or month may be preferable to a season name unless there is a logical connection ({{xt|the autumn harvest}}). 

Season names are preferable, however, when they refer to a time of the year rather than as a substitute for a date or range of dates ({{xt|migration to higher latitudes typically starts in mid spring}}). Lowercase season names in this context.

==== Years ====
'''Years''' are normally expressed in digits; a comma is not used in four-digit years ({{xt|1988}}, not {{xt|1,988}}). Avoid inserting the words {{xt|the year}} before the digits ({{xt|1995}}, not {{xt|the year 1995}}), unless the meaning would otherwise be unclear.

In-world years are always counted using [[Absalom Reckoning]]. Each year's article name will include {{xt|AR}} in its title and should be wikilinked in this fashion. Include a visible {{xt|AR}} in the wikilink of the first date per article. All subsequent articles can be piped such that only the year appears {{xt|4707 AR{{!}}4707}}

Absalom Reckoning should remain the only system in use unless an article's context makes it clear that a year is provided by a different reckoning, such as the [[Imperial Calendar]].

Year ranges, like all ranges, are separated by an en dash: do not use a hyphen or slash ({{xt|2005–08}}, not {{xt|2005-08}} or {{xt|2005/08}}). A closing positive AR year (greater than 1 AR) is normally written with two digits ({{xt|1881–86}}) unless it is in a different century from that of the opening year ({{xt|1881–1986}}). The full closing year is acceptable, but abbreviating it to a single digit ({{xt|1881–6}}) or three digits ({{xt|1881–886}}) is not. 

A closing negative AR year (a year before 1 AR) is given in full ({{xt|-2590–2550&nbsp;AR}}). While one era signifier at the end of a date range still requires an unspaced en dash ({{xt|12–5&nbsp;AR}}), a spaced en dash is required when a signifier is used after the opening and closing years ({{xt|-5 AR&nbsp;–&nbsp;29&nbsp;AR}}).

To indicate {{xt|around}}, {{xt|approximately}}, or {{xt|about}}, the abbreviations {{xt|''c.''}} and {{xt|''ca.''}} are preferred over {{xt|''circa''}}, {{xt|approximately}} or {{xt|approx.}}, and are spaced ({{xt|''c.''&nbsp;1291&nbsp;AR}}) and italicized. If you are calculating an in-world date based on its source's publication date, note so in the reference (see [[StarfinderWiki:Canon policy#Regarding dates|the canon policy]]). 

Use a question mark instead ({{xt|1291?}}) ''only'' if the date is in fact questioned rather than approximate. (The question mark may mistakenly be understood as a sign that editors have simply not checked the date.

'''Decades''' contain no apostrophe ({{xt|the 1980s}}, not {{xt|the 1980's}}); the two-digit form is used only where the century is clear ({{xt|the '80s}} or {{xt|the 80s}}).

'''Centuries and millennia''' are written using ordinal numbers, without superscripts or Roman numerals: {{xt|the second millennium}}, {{xt|the 19th century}}, {{xt|a 46th-century book}} (see also ''[[#Numbers as figures or words|Numbers as figures or words]]'' below). 

== Numbers{{anchor|Spelling out numbers}} == <!-- 
* Done, though I think this might need pared down due to its esoteric nature. -Yoda8myhead, 5/22/09
* Replaced anchor span with Anchor template. -Oznogon, 7/26/15
-->

=== Numbers as figures or words ===
As a general rule, in the body of an article, single-digit whole numbers from zero to nine are spelled out in words; numbers greater than nine are commonly rendered in numerals, or may be rendered in words if they are expressed in one or two words ({{xt|16}} or {{xt|sixteen}}, {{xt|84}} or {{xt|eighty&#x2011;four}}, {{xt|200}} or {{xt|two&nbsp;hundred}}, but {{xt|3.75}}, {{xt|544}}, {{xt|21&nbsp;million}}). This applies to ordinal numbers as well as cardinal numbers. However there are frequent exceptions to these rules.
*Numerals are used in [[wikipedia:Table (information)|table]]s and [[Help:Infobox|infobox]]es, and in places where space is limited. Numbers within a table's explanatory text and comments should be consistent with the general rule.
*Comparable quantities should be all spelled out or all figures: we may write either {{xt|5 cats and 32 dogs}} or {{xt|five cats and thirty&#x2011;two dogs}}, not {{xt|five cats and 32 dogs}}.
*Adjacent quantities that are not comparable should usually be in different formats: {{xt|thirty&#x2011;six 6.4&#x2011;inch rifled guns}} is more readable than {{xt|36 6.4&#x2011;inch rifled guns}}.
*Numbers that begin a sentence are spelled out, although it is often better to recast the sentence if simply changing format would produce other problems.
*The numerical elements of dates and times are not normally spelled out, except where customary in historical references such as {{xt|[[First of Rova Massacre]]}}. 
*Centuries are named in figures: ({{xt|the 5th century AR}}; {{xt|19th&#x2011;century warship}}); when the adjective is hyphenated, consider {{xt|nineteenth&#x2011;century warship}}, but not when contrasted with {{xt|warships of the 20th century}}. 
*Simple fractions are normally spelled out; use the fraction form if they occur in a percentage or with an abbreviated unit ({{xt|⅛&nbsp;mm}} or {{xt|an eighth of a millimeter}}) or if they are mixed with whole numbers. Decimal fractions are not spelled out.
*The use of words rather than figures may be preferred when expressing approximate numbers. 
*Proper names, idioms, and formal numerical designations comply with common usage ({{xt|Chanel No.&nbsp;5}}, {{xt|4&nbsp;Main Street}}, {{xt|1&#x2011;Naphthylamine}}, {{xt|Channel&nbsp;6}}). This is the case even where it causes a numeral to open a sentence, although this is usually avoided by rewording.
*Most proper names containing numbers spell them out (''e.g.'' {{xt|Fourth Amendment}}, {{xt|Seventeenth Judicial District}}, {{xt|Seven Years' War}}); the proper names of military units do not.

=== Large numbers ===
* [[Decimal separator#Thousands separator|Commas]] are used to break the sequence every three places: {{xt|2,900,000}}. 
* Large rounded numbers are generally assumed to be approximations; only where the approximation could be misleading is it necessary to qualify with ''about'' or a similar term.
* Where values in the millions occur a number of times through an article, upper-case {{xt|M}} may be used for ''million'', unspaced, after using the full word at the first occurrence.

=== Decimal points ===
* A decimal point is used between the integral and the fractional parts of a decimal; a comma is never used in this role ({{xt|6.57}}, not {{xt|6,57}}).
* Numbers between minus one and plus one require a leading zero ({{xt|0.02}}, not {{xt|.02}}).

=== Percentages ===
* {{xt|Percent}} is commonly used to indicate percentages in the body of an article. The symbol {{xt|%}} may be more common in complex listings.
* The symbol is unspaced ({{xt|71%}}, not {{xt|71 %}}).
* In tables and infoboxes, the symbol is used, not the word {{xt|percent}}.
* Ranges are preferably formatted with one rather than two percentage signifiers ({{xt|22–28%}}, not {{xt|22%–28%}}).

== Units of measurement ==<!-- Done 5/22/09 yoda8myhead -- This may not even be necessary in as much detail as is here. -->
{{See also|Wikipedia:Manual_of_Style_(dates_and_numbers)#Units_of_measurement}} 

The use of units of measurement is based on the following principles:
* Avoid ambiguity: Aim to write so you cannot be misunderstood.
* Familiarity: The less one has to look up definitions, the easier it is to be understood. 
* International scope: StarfinderWiki is not country-specific; it is, however, based around a campaign setting (and game) which consistently provides US-based units of measurement.  
===Which units to use===
In general, prefer units provided in the source material, which will almost always be in imperial units. For this reason, unlike wikipedia and other international wikis, imperial units are preferred over other units, so {{xt|22&nbsp;lb (10&nbsp;kg)}} rather than {{xt|10&nbsp;kg (22&nbsp;lb)}}. 

===Unit conversions===
* Generally, conversions to and from metric units and [[Wikipedia:United States customary units|US]] or [[Wikipedia:Imperial units|imperial]] units should be provided, except where inserting a conversion would make a common expression awkward ({{xt|The four-minute mile}}).
* In the main text, give the main units as words and use unit symbols or abbreviations for conversions in parentheses; for example, {{xt|a pipe 4&nbsp;inches (100&nbsp;mm)}} in diameter and {{xt|16&nbsp;kilometres (10&nbsp;mi) long}} or {{xt|a pipe 4&nbsp;inches (100&nbsp;mm) in diameter and 10&nbsp;miles (16&nbsp;km) long}}. However, where there is consensus to do so, the main units may also be abbreviated in the main text after the first occurrence. 
* Converted values should use a level of precision similar to that of the source value, so {{xt|the Moon is 380,000 kilometres (240,000&nbsp;mi) from Earth}}, not {{xt|(236,121&nbsp;mi)}}. However, small numbers may need to be converted to a greater level of precision where rounding would cause a significant distortion, so {{xt|one mile (1.6&nbsp;km)}}, not {{xt|one mile (2&nbsp;km)}}.

=== Unit symbols and abbreviations ===
{{main|Wikipedia:Manual of Style (dates and numbers)#Unit symbols}}
* Non-breaking spaces are used between values and units; see the [[#Non-breaking spaces|Non-breaking spaces]] section above.
* Standard abbreviations and symbols for units are undotted (do not carry periods). For example, {{xt|m}} for metre/meter and {{xt|kg}} for kilogram (not {{xt|m.}} or {{xt|kg.}}), {{xt|in}} for inch (not {{xt|in.}},&nbsp; or&nbsp;{{xt|&Prime;}}), {{xt|ft}} for foot (not {{xt|ft.}}, or&nbsp;{{xt|&prime;}}) and {{xt|lb}} for pound (not {{xt|lb.}} or&nbsp;{{xt|#}}).
* Do not append an {{xt|s}} for the plurals of unit symbols ({{xt|kg}}, {{xt|km}}, {{xt|in}}, {{xt|lb}}, not {{xt|kgs}}, {{xt|kms}}, {{xt|ins}}, {{xt|lbs}}). A lowercase {{xt|s}} is the SI symbol for second; thus, {{xt|kgs}} can be confused with {{xt|kg&nbsp;s}}, which means "kilogram-second".
* In tables and infoboxes, use symbols and abbreviations for units, not words.
* Ranges are preferably formatted with one rather than two unit signifiers ({{xt|5.9–6.3&nbsp;kg}}, not {{xt|5.9&nbsp;kg – 6.3&nbsp;kg}}).

== Currencies ==<!-- Done 5/22/09 Yoda8myhead -->
=== Real world ===
Since [[Paizo Inc.]] and most other companies producing official support for the [[Starfinder campaign setting]] are located in the United States, the American dollar {{xt|$}} should be the standard currency used on StarfinderWiki. If it is necessary to break from this convention for any reason, provide only published (non-converted) amounts in other currencies.  

Include two decimal places in all currency listings {{xt|$5.00}} ''not'' {{xt|$5}}.

=== In world === <!-- I can see this coming up. This is my opinion of how we should handle it. Comments/changes welcome. -->
When in-world [[StarfinderWiki:Point of view|POV]] references to monetary values are required, the following rules should be used:

* When general units of currency are used, the unit, in singular, should follow space after the value, and should not contain periods.
::{|style="background: transparent;"
|-valign=top
|''Incorrect'':&nbsp; &nbsp;||{{xt|15 cps}}
|-valign=top
|''Incorrect'':             ||{{xt|25sp}}
|-valign=top
|''Incorrect'':             ||{{xt|35 g.p.}}
|-valign=top
|''Correct'':               ||{{xt|45 pp}}
|}

* When known, a specific currency name should be used ({{xt|15 Korvosan Gold Sails}} instead of {{xt|15 gp}}). If the nationality of a currency is clear in the context it is used, the national adjective may be omitted ({{xt|In Korvosa, a decent blade can be purchased for 15 Gold Sails}}).

== Simple tabulation == <!-- Done 5/22/09 Yoda8myhead --> <!-- We might want to remove this altogether, as it's not very helpful and adds more to the TOC and general clutter of the page.-->
Lines that start with blank spaces in the editing window are displayed boxed and in a fixed-width font, for simple tabulation. Lines that contain only a blank space insert a blank line into the table. For a complete guide to constructing tables, see [[Wikipedia:Meta:Help:Table]].

== Grammar == <!-- All sections complete 5/26/09 Yoda8myhead -->
=== Possessives ===
:''For thorough treatment of the English possessive see {{w|Apostrophe}}. See also [[#Apostrophes|Apostrophes]], above.''
*''{{xt|It's}}'' is the short form of {{xt|it is}} or {{xt|it has}} (as in {{xt|it's a nice day}}, {{xt|it's been a nice day}}); the possessive {{xt|its}} (as in {{xt|the dog chased its tail}}) has no apostrophe, nor do {{xt|hers}}, {{xt|ours}}, {{xt|yours}}, {{xt|theirs}}, and {{xt|whose}}.
* The possessive of a '''singular noun''' is formed by adding {{xt|'s}} (as in {{xt|my daughter's achievement}}, {{xt|the boss's wife}}, {{xt|Glass's books}}, {{xt|Illinois's legislature}}). For a '''singular noun ending in one {{xt|s}}''', there are two widely accepted forms:
:*Add {{xt|'s}}: {{xt|James's house}}, {{xt|Euripides's plays}}, {{xt|Moses's early life}}, {{xt|Brahms's music}}. This style is more common for modern names and common nouns.
:*Add just an apostrophe: {{xt|James' house}}, {{xt|Euripides' plays}}, {{xt|Moses' early life}}, {{xt|Brahms' music}}. This style is more common for biblical and classical names ({{xt|Socrates' wife}}; {{xt|Moses' ascent of Sinai}}; {{xt|Jesus' last words}}).
:Either of those forms may be acceptable in StarfinderWiki articles, as long as consistency is maintained within a given article. It should be noted, however, that Paizo adheres to the former of these rules in their in-house manual of style.
* The possessive of a '''plural noun ending in {{xt|s}}''' is formed by adding just the apostrophe ({{xt|my daughters' husbands}}). The possessive of a '''plural noun ''not'' ending in {{xt|s}}''' is formed by adding {{xt|'s}} ({{xt|women's careers}}, {{xt|children's toys}}).
* '''Official names''' (of companies, organizations, or places) should be made to conform to a specific style. For instance [[St Thomas's Hospital]], being the official designation, should ''not'' be rendered as {{xt|St Thomas' Hospital}}.

=== First-person pronouns ===
StarfinderWiki articles must not be based on one person's opinions or experiences; thus, the pronoun {{xt|I}} is never used, except when it appears in a quotation. For similar reasons, avoid the pronoun {{xt|we}}; a sentence such as {{xt|We should note that some critics have argued in favor of the proposal}} sounds more personal than encyclopedic.

=== Second-person pronouns ===
Use of the second person ({{xt|you}}), which is often ambiguous and contrary to the tone of an encyclopedia, is discouraged. Instead, refer to the subject of the sentence or use the {{w|English passive voice|passive voice}}—for example:
{| class="wikitable"
!Use:
| {{xt2|When a player moves past "Go", that player collects $200.}}
|-
! Use:
| {{xt2|Players passing "Go" collect $200.}}
|-
! Use:
| {{xt2|$200 is collected when passing "Go".}}
|-
! Do not use:
| {{xt2|When you move past "Go", you collect $200.}}
|}

This guideline does not apply to quoted text, which should be quoted exactly.

=== Contested vocabulary ===
Words and phrases like ''thusly'', ''overly'', ''whilst'', ''amongst'', ''as per'', ''refute'' in the sense of ''dispute'', along with several others, should be avoided because they are not widely accepted—at least in some of their applications. Some are regional, so unsuitable in an international encyclopedia (see [[#National varieties of English|National varieties of English]] below). Some give an impression of "straining for formality", and therefore of an insecure grasp of English. See {{w|List of English words with disputed usage}}, {{w|Wikipedia:Words to avoid|Words to avoid}}, and {{w|List of commonly misused English words}}; see also [[#Identity|Identity]] and [[#Gender-neutral language|Gender-neutral language]] below.

=== Contractions === <!-- section ''Possessives'' above links here -->
In general, the use of contractions—such as ''don't'', ''can't'', ''won't'', ''they'd'', ''should've'', ''it's''—is informal and should be avoided; however, contractions should be left unchanged when they occur in a quotation.

=== Instructional and presumptuous language ===
Avoid such phrases as ''remember that'' and ''note that'', which address readers directly in an unencyclopedic tone. Similarly, phrases such as ''of course'', ''naturally'', ''obviously'', ''clearly'' and ''actually'' make presumptions about readers' knowledge, and call into question the reason for including the related information in the first place. See {{|Wikipedia:Words to avoid#Of course, naturally, obviously, clearly, actually|Wikipedia:Words to avoid}}.

=== Subset terms ===
A ''subset term'' identifies a set of members of a larger class. Common subset terms are ''including'', ''among'', and ''et cetera'' (''etc.''). Do not use two subset terms ("Among the most well-known members of the fraternity include&nbsp;...", "The elements in stars include hydrogen, helium and iron, ''etc.''"). Do not use ''including'' to introduce a complete list, where ''comprising'', ''consisting of'', or ''composed of'' would be correct.

=== Plurals ===
Use the appropriate plural; allow for cases like oblast, or octopus, when a foreign word has been assimilated into English and normally takes an ''s'' or ''es'' plural, not its original plural. A number of words, like ''army'', ''company'', ''crowd'', ''fleet'', ''government'', ''majority'', ''mess'', ''number'', ''pack'', and ''party'' may refer either to a single entity or the members of the set that compose it. In British English, they are normally treated as singular or plural according to context; names of towns and countries take plural verbs when they refer to sports teams but singular verbs when they refer to the actual place (or to the club as a business enterprise): ''[[England national football team|England]] are playing [[Germany national football team|Germany]] tonight'' refers to a [[Association football|football]] team, but ''England is the most populous country of the United Kingdom'' refers to the country.

In North American English, these words (and ''the United States'', for historical reasons) are invariably treated as singular.<!-- In world examples might be helpful here-->

=== Ampersand ===
The ampersand (''&'') is a symbol representing the word ''and''. In running prose, ''and'' should mainly be used instead as it is more formal. If it appears in the titles of businesses, works, or in a quotation, the use of an ampersand is justified (as in "Dungeons & Dragons"). The ampersand may also be used in tables, infoboxes, and other places where space is limited.

=== National varieties of English ===
{{see also|StarfinderWiki:Manual of Style (spelling)}}
StarfinderWiki does not prefer any major national variety of the language. No variety is more ''correct'' than another. Editors should recognize that the differences between the varieties are superficial. Cultural clashes over spelling and grammar are avoided by using the following three guidelines. (The accepted style of punctuation is covered in the [[#Punctuation|punctuation section]].)

==== Consistency within articles ====
:''See also [[#Internal consistency|Internal consistency]]''
Each article should consistently use the same conventions of spelling, grammar, and punctuation. For example, these should not be used in the same article: ''center'' and ''centre''; ''insofar'' and ''in so far''; em dash and spaced en dash (see [[#Dashes|above]]). The exceptions are:
* quotations (the original variety is retained; though the precise styling of punctuation marks such as dashes, ellipses, apostrophes, and quotation marks should be made consistent with the surrounding article);
* proper names (the original spelling is used, for example ''[[United States Department of Defense]]'' and ''[[Australian Defence Force]]''); 
* book titles (again, use the original spelling—if there are multiple editions which spell a given title differently, use the one consulted); and 
* explicit comparisons of varieties of English.

==== Retaining the existing variety ====
If an article has evolved using predominantly one variety, the whole article should conform to that variety, unless there are reasons for changing it based on strong national ties to the topic. In the early stages of writing an article, the variety chosen by the first major contributor to the article should be used. Where an article that is not a [[StarfinderWiki:Stub|stub]] shows no signs of which variety it is written in, the first person to make an edit that disambiguates the variety is equivalent to the ''first major contributor''.

==== Opportunities for commonality ====
StarfinderWiki tries to find words that are common to all varieties of English.
* In choosing words or expressions, especially for article titles, there may be value in making choices that avoid varying spellings, where possible. In extreme cases of conflicting names, a common substitute (such as [[fixed-wing aircraft]]) is preferred to national varieties (''fixed-wing aeroplanes'' [British English], and ''fixed-wing airplanes'' [American English]).
* If a variable spelling appears in an article name, [[StarfinderWiki:Redirect|redirect]] pages are made to accommodate the other variants, as with [[Artefact]] and [[Artifact]], so that they can always be found in searches and linked to from either spelling.
* Sensitivity to terms that may be used differently between different varieties of English allows for wider readability; this may include glossing terms and providing alternative terms where confusion may arise. Insisting on a single term or a single usage as the only correct option does not serve well the purposes of an international encyclopedia.
* Use an unambiguous word or phrase in preference to one that is ambiguous because of national differences. For example, use ''alternative route'' (or even ''other route'') rather than ''alternate route'', since ''alternate'' may mean only "alternating" to a British English speaker.

Articles such as {{w|English plural}} and {{w|American and British English differences}} provide information on the differences between the major varieties of the language.

=== Foreign terms ===
{{see also|Wikipedia:Interlanguage links}}
Foreign words should be used sparingly.
; No common usage in English
: Use italics for phrases in other languages and for isolated foreign words that are not current in English.
; Common usage in English
: {{W|Loanword}}s and borrowed phrases that have common usage in English—Gestapo, samurai, vice versa, esprit de corps—do not require italics. A rule of thumb is not to italicize words that appear unitalicized in major English-language dictionaries. 
; Spelling and transliteration

=== Gender-neutral language ===
Use gender-neutral language where this can be done with clarity and precision. This does not apply to direct quotations or the titles of works (''The Ascent of Man''), or where all referents are of one gender, such as in an all-female school (''if any student broke that rule, she was severely punished'').

== Images == <!-- Completed 5/21/09 Yoda8myhead -->
{{see|Wikipedia:Picture tutorial|Wikipedia:Accessibility#Images|Wikipedia:Image use policy|Wikipedia:Layout#Images}}

* Start an article with a right-aligned lead image or [[StarfinderWiki:Manual of Style (infoboxes)|InfoBox]].
* Images should be ''inside'' the section they belong to (after the heading and after any links to other articles), and not ''above'' the heading.
* Avoid sandwiching text between two images that face each other.
* Use captions to explain the relevance of the image to the article (see [[#Captions|Captions]], below).
* See [[Wikipedia:Picture tutorial#Avoiding image "stack-ups"|this tutorial]] for how to group images and avoid "stack-ups".
* It is often preferable to place images of faces so that the face or eyes look toward the text. Multiple images in the same article can be staggered right-and-left (for example: [http://en.wikipedia.org/w/index.php?title=Timpani&oldid=223110896 Timpani]). However, images should not be reversed simply to resolve a conflict between these guidelines; doing so misinforms the reader for the sake of our layout preferences. If an image is reversed or otherwise substantially altered, there should be a clear advantage to the reader in doing so (for example, cropping a work of art to focus on a detail that is the subject of commentary), and the alteration must be noted in the caption. 
* Do not place left-aligned images directly below a subsection-level heading (<code>===</code> or lower), as this sometimes disconnects the heading from the text that follows it. This can often be avoided by shifting left-aligned images down a paragraph or two. 
* Most pictures should be between 100 and 400&nbsp;pixels wide. Generally, use the thumbnail option ("thumb"), which is available in the [[WP:Image markup|image markup]]. This results in a default width of 180 pixels (140 pixels if the "upright" option is used as well), although logged-in users can set a different default in their user preferences. As a rule, images should not be set to another size (that is, one that overrides the default). Where it is appropriate to select a particular size, images should generally be no more than 300 pixels wide, so that they can be comfortably displayed on 800x600 monitors. Where appropriate, the {{Tl|Wide image}} template can be used to fit an image into the width of the browser window. Examples where size-forcing may be appropriate include:
:*Images with aspect ratios that are extreme or that otherwise distort or obscure the image
:*Detailed maps, diagrams, or charts
:*Images containing a lot of detail, if the detail is important to the article
:*Images in which a small region is relevant, but cropping to that region would reduce the coherence of the image
:*Lead images, which should usually be no larger than 300 pixels
* The use of [[Wikipedia:Picture tutorial#Photo gallery|galleries]] should be in keeping with [[Wikipedia:Image use policy#Image galleries|StarfinderWiki's image use policy]].
* Editors are encouraged to add [[WP:ALT|alt text]] to all images for which it seems reasonable.  Alternative text describes the image for readers who cannot see the image, such as visually impaired readers or those using web-browsers that do not download images.  
**Instructions on adding alt text to images can be found [[Wikipedia:WP:ALT|here]].  A [[Wikipedia:WP:US|script]] for checking whether an article's images have alt text is given [[Wikipedia:User:Proteins/checkALTtext.js|here]].
** Alt text is not the same as captions: alt text describes the image for those who cannot see it, whereas captions are intended to explain or supplement an image that is visible.  Therefore, alt text should not be redundant with the caption or the main text of the article.  [[Wikipedia:WP:ALT|The guideline on this subject]] notes that images need not have alt text; editors should ask themselves how much sighted readers would lose if the picture were blanked, and how far that is describable in words.  By default, no alt text is defined in images, provided that the <code>thumb</code> or <code>frame</code> parameter is included.  

=== Avoid entering textual information as images ===
Textual information should be entered as text rather than as an image. Text in images is not searchable, and can be slow to download; the image is unlikely to be read as text by devices for the visually impaired. Text may be colored and decorated with [[Wikipedia:Cascading Style Sheets|CSS]] tags and templates. Even if the problems can be worked around, as by including a caption or internal information, editors should still consider whether fancy text really adds anything useful.

== Captions == <!-- Completed 5/22/09 Yoda8myhead -->
{{see|Wikipedia:Captions}}
=== Usage ===
Photographs and other graphics should always have captions, unless they are "self-captioning" (such as reproductions of book covers) or when they are unambiguous depictions of the subject of the article. For example, in a biography article, a caption is not mandatory for a portrait of the subject pictured alone, but might contain the name of the subject and additional information relevant to the image, such as the year or the subject's age.  Images included in infobox templates should never include captions.
=== Formatting ===
* Captions normally start with a capital letter.
* Most captions are not complete sentences, but merely sentence fragments that should not end with a period. If a complete sentence occurs in a caption, that sentence and any sentence fragments in that caption should end with a period.
* Captions should not be italicized, except for words that are conventionally italicized. 
* Captions should be succinct; more information about the image can be included on its description page, or in the main text.

== Bulleted and numbered lists == 
<!--
* Complete. -Yoda8myhead, 5/21/09
* Suggest alphabetizing unordered lists by default. -Oznogon, 7/26/15
-->
{{see also|Help:List|Wikipedia:Lists}}
Do not use lists if a passage reads easily using plain paragraphs.

* Do not leave blank lines between items in a bulleted or numbered list unless there is a reason to do so, since this causes the Wiki software to interpret each list item as an individual list.
* Use numbers rather than bullets only if: 
** there is a need to refer to the elements by number;
** the sequence of the items is critical; or
** the numbering has value of its own, for example in a chapter listing.
* Use the same grammatical form for all elements in a list where possible, and do not mix the use of sentences and sentence fragments as elements. 
** When the elements are complete sentences, they are formatted using sentence case and a final period. 
** When the elements are sentence fragments, they are typically introduced by a lead fragment ending with a colon. When these elements are titles of works, they retain the original capitalization of the title. Other elements are formatted consistently in either sentence or lower case.  Final punctuation for these elements can be omitted entirely, or should otherwise be a period for the terminating element with each of its preceding elements having a final semicolon.
* Alphabetize unordered bulleted lists unless a more logical organization is possible.

== Categories == <!-- 
* Added  to conclude a formal Policy Change (see Discussion Page). -Fleanetha, 7 December 2013
-->
Categories are used on the StarfinderWiki to collate similar information: they act as a classification of entries and a simple way of locating information. Every article should be in one or more categories, and there is no limit to the number of categories that a single article can be in. There is significant help about adding categories and setting up category pages in the help pages, which should also be used to solve most questions about style associated with categories: [[Help:Categories]] & [[Help:Creating category pages]]. The box to the right of these help pages has links to further help pages providing guidance for adding categories to various types of common articles.

One point of style should be noted here: Within the [[:Category:Races]] category tree, all races and ethnicities are used in their singular form. For instance, we use [[:Category:Red dragon]] and [[:Category:Red dragon/Inhabitants]], rather than [[:Category:Red dragons]] and [[:Category:Red dragons/Inhabitants]].

== Links == <!-- Edited by Yoda8myhead 5/21/09 SEE NOTES -->
=== Wikilinks ===
'''Make [[Help:Contents/Links|links]] only where they are relevant to the context:''' It is not useful and can be very distracting to mark all possible words as hyperlinks. Links should add to the user's experience; they should not detract from it by making the article harder to read. A high density of links can draw attention away from the high-value links that you would like your readers to follow up. 

'''Eliminate redundancies:''' Redundant links clutter the page and make future maintenance harder. Link only once to any secondary article within the body of an article.  Links within templates (such as infoboxes or navigation bars) and in ''Main article'' and ''See also'' redirects are the only links which should be duplicated within a single article.

'''Check links:''' After linking, ensure that the destination is the intended one; many words lead to disambiguation pages and not to complete articles on a concept, or to real-world articles that share the same name as an in-world object or person. An anchor into a targeted page—the label after a pound/hash sign (#) in a URL—will get readers to the relevant area within that page.

'''Initial capitalization:''' StarfinderWiki's [[MediaWiki]] software does not require that wikilinks begin with an upper-case character. Only capitalize the first letter where this is naturally called for, or when specifically referring to the linked article by its name: ''[[Vermin]] are often [[venomous]], but [[magical beast]]s only rarely (see ''[[Poison]]'').''

=== External links ===
Articles can include an ''external links'' section at the end to list links to websites outside StarfinderWiki that contain further information, as opposed to citing sources. The standard format is a primary heading named <code><nowiki>== External links ==</nowiki></code> followed by a bulleted list of links. External links should identify the link and briefly indicate its relevance to the article subject. For example:
<!--We should edit this to include more relevant examples after the Manual itself is set-->
:<code><nowiki>*[http://history.nih.gov/exhibits/history/index.html History of NIH]</nowiki></code>
:<code><nowiki>*[http://www.nih.gov/ National Institutes of Health homepage]</nowiki></code>
These will appear as: 
:* [http://history.nih.gov/exhibits/history/index.html History of NIH]
:* [http://www.nih.gov/ National Institutes of Health homepage]
Avoid listing an excessive number of external links; StarfinderWiki is [[Wikipedia:Wikipedia:NOTLINK#LINK|not a link repository]].
<!--Wikipedia has a "what Wikipedia is not" page which is linked to above.  Should we make something similar on PFWiki?-->

== Miscellaneous == <!-- All subsections complete Yoda8myhead 5/21/09 -->
=== Keep markup simple ===
Use the simplest markup to display information in a useful and comprehensible way. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly and only with good reason. Minimizing markup in entries allows easier editing.

In particular, do not use the CSS <code>float</code> or <code>line-height</code> properties because they break rendering on some browsers when large fonts are used.

=== Formatting issues ===
Formatting issues such as font size, blank space and color are issues for the wiki's site-wide style sheet and should not be specified in articles except in special cases. If you absolutely must specify a font size, use a relative size like <code>font-size: 80%</code>, not an absolute size like <code>font-size: 8pt</code>. It is also almost never a good idea to use other style changes, such as font family or color.

Typically, the use of custom font styles will:
* reduce consistency—the text will no longer look uniform;
* reduce usability—it will likely be impossible for people with custom stylesheets (for accessibility reasons, for example) to override it, and it might clash with a different skin as well as bother people with color blindness; and
* increase arguments—other wiki users may disagree aesthetically with the choice of style.

==== Color coding ====
Using color ''alone'' to convey information ({{w|color coding}}) should not be done. It is certainly desirable to use color as an aid for those who can see it, but the information should still be accessible without it.

=== Scrolling lists ===
Scrolling lists and boxes that toggle text display between hide and show are acceptable in infoboxes and navigation boxes, but should never be used in the article prose or references, because of issues with readability, accessibility, and printing.

=== Invisible comments ===
Editors use invisible comments to communicate with each other in the body of the text of an article. These comments are visible only in the wiki source (that is, in edit mode), not in read mode.

Invisible comments are useful for flagging an issue or leaving instructions about part of the text, where this is more convenient than raising the matter on the talk page. They should be used judiciously, because they can clutter the wiki source for other editors. Check that your invisible comment does not change the formatting, such as introducing unwanted white space in read mode.

To leave an invisible comment, enclose the text you intend to be read only by editors within <code>&lt;!--</code> and <code>--&gt;</code>. For example: <nowiki><!--If you change this section title, please also change the links to it on the pages ...--></nowiki>

=== Pronunciation ===
'''Pronunciation''' in StarfinderWiki is indicated using English pronunciation respelling. In general, if an official pronunciation has not been published or a source can not be provided for a pronunciation, do not include it in the article. You can find a {{w|pronunciation respelling key}} on Wikipedia.