Acepedia
Acepedia
(Adding usage of terms where a space is in the middle, especially concerning "air strike" over "airstrike")
Tag: sourceedit
(Moving information from Template:Sic (and some Wikipedia information) to a section here; no policy change in how we handle sic instances)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  +
{{Policy|[[AP:MoS]]<br>[[AP:MOS]]}}
{{Notice|The Manual of Style is currently being written. Check back soon for more updates!}}
 
Acepedia's '''Manual of Style''' ('''MoS''') acts as a {{Wp|style manual}} for all [[Acepedia:About|Acepedia]] articles. This creates guidelines that help keep a uniform look and feel across the wiki. Should you have any questions or comments about the Manual of Style, please feel free to contact an [[Acepedia:Administrators|Administrator]] - we would be more than happy to help.
+
[[Project:About|{{SITENAME}}]]'s '''Manual of Style''' (often abbreviated as '''MoS''' or '''MOS''') is a {{Wp|style manual}} for all main namespace articles and files. It helps keep articles in their highest quality by maintaining consistency, clarity, and precision. Please do your best to adhere to the guidelines outlined below whenever possible. Special cases may warrant exceptions to these guidelines. Keep in mind that the Manual of Style is a loose document to assist in better editing; it does not necessarily apply to personal or discussion areas.
   
  +
==Spelling==
Keep in mind that this article, like the wiki, is constantly being changed. In addition, exceptions may apply to any of these formats - this Manual acts as a guideline, so certain situations may dictate an override. However, please do your best to adhere to the formats outlined below whenever possible.
 
  +
===Language===
  +
'''American English spelling''' should be used on all canon encyclopedia articles, on all templates transcribed on articles, and on all official projects and blog posts. American spelling is preferred over British since Japanese culture surrounding English education leans more towards American. There are the following exceptions:
   
  +
*Regional variations in spelling may be used in all other contexts on {{SITENAME}}, such as comments, message walls, user pages, blog posts, and Discussions.
Do not confuse the Manual of Style for the [[Acepedia:Rules|rules of Acepedia]]. The MoS is a loose document to assist in better editing; the rules are designed to protect users and content, and come with penalties if they are not followed.
 
  +
*If quoting a source or transcript, never alter any part of the quotation, even if it does not use American spelling.
   
  +
In addition, if a word is interchangeably used with or without a space in the middle (e.g. ''airstrike'' or ''air strike''), prefer the version with the space in the middle ({{xt|''air strike''}}).{{Note|The specific example of ''air strike'' follows the usage of the term in [[Close Range Assault|Air Strike Mode]], [[EMERGENCY AIR STRIKE]], and some briefings and debriefings ([[Imminent Threat]], [[Invincible Fleet]], [[The Final Overture]], etc.).}}
Credit goes to the [[w:c:undertale:Undertale Wiki:Manual of Style|''Undertale'' Wiki]] for the general format of Acepedia's Manual of Style.
 
   
==Language==
+
===Sic===
  +
{{Shortcut|AP:Sic|AP:SIC}}
*Acepedia is hosted in English. To standardize spelling, American English is preferred over other types of English. ex: "color" not "colour"
 
  +
The Latin adverb '''''{{Wp|sic}}''''' inserted after a quoted word or passage indicates that the quoted material was transcribed or translated exactly as found in the source text, complete with any erroneous spelling.
**Note that while the entirety of MoS does not apply outside of articles, this rule is specifically unnecessary to follow. Users in many countries who know many languages visit Acepedia, so English is not required on message walls, user profiles, article comments, or blog posts.
 
**Grammar is not strictly based on American English, and includes nods to British English grammar as well. The entire MoS discusses different forms of grammar to use for different situations.
 
*Articles should use the {{Wp|active voice}} ("Mobius 1 destroyed the target") to outline and describe events. Aim to be as succinct and detailed as possible. The passive voice ("Target destroyed by Mobius 1") should be used sparingly. Also, avoid conjecture whenever possible; if something must be inferred, acknowledge it is.
 
*Dates follow the month-day-year convention. ex: "The Second Usean Continental War ended on '''September 19, 2005'''."
 
**Do not use numbers in place of month names. ex: September, not 9.
 
**Do not use suffixes (–st, –nd, –rd or –th) after dates in the month-day style. ex: "On '''July 10''', ISAF liberated San Salvacion."
 
*Times follow military 24-hour conventions. No colon is necessary, and there is no space between the numbers and "hrs" abbreviation. ex: "At '''0000hrs''', Operation Firefly commenced."
 
*All coordinates on Acepedia require references and should follow the degrees (°) N/E/S/W convention where possible. ex: "'''34.6°N, 132.5°E'''" OR "'''112°6' S, 45°18' W'''"
 
*Numbers less than or equal to ten should be spelled out; numbers over 11 should be displayed numerically. Suffixes can be used if the sentence requires one as long as the number is not part of a date (see above). ex: "Blockade is the '''fourth''' campaign mission."
 
**This does not apply to the passage of time - always use numerals here. ex: "3 hours later", "7 minutes"
 
**Do not use numerals for ''general'' numbers in the millions or billions; instead, use the hybrid "X million" format. ex: "Nearly 1 million Useans became refugees after Ulysses."
 
**Many exceptions can apply to the above rule when exact numbers must be given; for example, aircraft prices. When using long numerals, commas (,) must be used for separation of the thousand-degrees, with periods (.) used to denote decimals if necessary. Example: 123,456,789.01
 
*In instances where the gender of a character is not certain (esp. a player character who is never shown or referred to by a pronoun), the singular "they" and "themself" should be used.
 
*When using possessive forms of singular and proper nouns ending with s, append ''{{'}}s'' at the end. Example: Mobius's.
 
*{{Wp|Past tense}} should be used when referring to historical events. {{Wp|Present tense}} should be used when referring to gameplay, within which {{Wp|Grammatical person|third-person}} should be used to refer to the player (i.e. "the player must shoot down all targets", NOT "you must shoot down all targets").
 
[[File:Yellow 13 and Yellow 4.jpg|thumb|250px]]
 
*The {{Wp|serial comma}}, also known as the Oxford comma, should be used most of the time. However, in cases where it would cause ambiguity, try rephrasing the phrase.
 
**Example: "Yellow 13, a flight mechanic, and Yellow 4" causes ambiguity for inexperienced players who may misunderstand Yellow 13 to be a flight mechanic. In this case, "Yellow 13, Yellow 4, and a flight mechanic" works better.
 
*When a word is interchangeably used with or without a space in the middle ("airstrike" or "air strike"), prefer the version with the space in the middle ("air strike").
 
**This specific example with the term "air strike" follows the usage of the term in [[Close Range Assault|Air Strike Mode]], [[EMERGENCY AIR STRIKE]], and some briefings and debriefings ([[Imminent Threat]], [[Invincible Fleet]], [[The Final Overture]], etc.).
 
   
  +
On {{SITENAME}}, any instances of misspelling (or [[#Grammar|incorrect grammar]]) that occur in quoted material should be followed by an instance of [[:Template:Sic]]. This signifies to the reader and future editors that the error was not an editing mistake, rather it was quoted directly from the ''Ace Combat'' game or other material cited. This should only be done for quoted material, transcripts, or the like, not for main article prose. False insertions of the Sic template are not allowed; if an editing mistake occurs, particularly in spelling, it should be corrected as per [[#Language|§&nbsp;Language]].
==Content==
 
===MediaWiki Coding===
 
*Italicized text is generated by surrounding text with two apostrophes: <nowiki>''ITALICIZED TEXT''</nowiki>
 
*Bold text is generated by surrounding text with three apostrophes: <nowiki>'''BOLD TEXT'''</nowiki>
 
*Page breaks act as returns and are coded as follows: <nowiki><br></nowiki> or <nowiki><br/></nowiki> (neither is preferred over the other)
 
*Article links in the same wiki are coded with double square brackets: <nowiki>[[ARTICLE NAME]]</nowiki>
 
**When italicizing a link, put the apostrophes outside of the brackets, not inside: <nowiki>''[[ITALICIZED ARTICLE NAME]]''</nowiki>
 
**Always link to an article's main page, NOT a redirect link. If you click a link and the page says at the top that you were redirected, the link you clicked was a redirect and should be corrected.
 
**Links can be renamed to fit their context: <nowiki>[[ARTICLE NAME|NEW NAME]]</nowiki><br/>ex: "The [[Independent State Allied Forces|ISAF]] declared war on Erusea."
 
*Bullet-pointed lists (like the one you're reading right now) are created using <nowiki>*asterisks</nowiki>. Numbered lists are created using the <nowiki>#number sign</nowiki>. Simple indentations with no bullet or number are created using a <nowiki>:colon</nowiki>.
 
**The more asterisks, number signs, or colons used, the farther the indentation. You can even mix these together!
 
**If a list element is only a name or otherwise not a full sentence, no punctuation is necessary.
 
   
  +
==Grammar==
===Acepedia Content===
 
  +
===Voice===
*All content on Acepedia's mainspace articles must pertain to the ''[[Ace Combat]]'' series. When discussing information on topics that also apply in the real world (real aircraft, real countries, etc.), only ''Ace Combat''-related information should be presented.
 
  +
Use the active voice to outline and describe events. The passive voice should be used sparingly.
*Location coordinates should never be presented in an article except in [[:Template:Location]]. Always discuss a location's relative position to other known locations. ex: Belka is east of Osea.
 
*Operation names DO NOT have colons in them, unless otherwise specified. ex: "'''Operation Blackout'''" is correct; "Operation: Blackout" is incorrect.
 
*Titles and abbreviations of games should be ''italicized'' at ALL TIMES. ex: "Cipher is the hero of '''''Ace Combat Zero: The Belkan War'''''." OR "Cipher is the hero of '''''ACZ'''''."
 
**When abbreviating game titles, '''only''' numbered titles, ''X'', and ''Xi'' may be fully abbreviated; all other titles should simply drop the ''Ace Combat:'' prefix.
 
**:ex: ''AC2'', ''AC3'', ''AC04'' (note: 04, '''not''' 4), ''AC5'', ''ACZ'', ''AC6'', ''AC7'', ''ACX'', ''ACXi''
 
**:ex: ''Air Combat'', ''Joint Assault'', ''Assault Horizon'', ''Assault Horizon Legacy +'', ''Infinity''
 
*Shortening/abbreviated an organization's name must follow the convention provided by the latest game. ex: "Independent State Allied Forces" is shortened to "ISAF" as stated in ''AC04'', NOT "Allies".
 
*Quotations use the following template: [[:Template:Quote|<nowiki>{{Quote|QUOTED TEXT|SPEAKER}}</nowiki>]]
 
**NO italicizing or quotation marks are necessary—the template does it all for you.
 
**NO punctuation is necessary after the speaker's name/identifier. However, a reference IS necessary after the speaker's name/identifier.
 
**Quotations at the top of articles or sections always come ''after'' the infobox or image.
 
*In-text quotations should be italicized and surrounded by "quotation marks". Do NOT use the ''Ace Combat'' in-game << arrow quotes >>. ex: ''"Yo Buddy, you still alive?"''
 
**Punctuation marks following quotations should go ''outside'' of the quotation marks, except if the same punctuation will end the sentence or quotation.<br/>ex: Pixy said ''"Yo Buddy, you still '''alive?"''''' to Cipher.<br/>ex: After Jean-Louis was shot down, a Megalith defender told Gene that he's ''"got to take over the '''command"'',''' but at that point the squadron became disorganized.
 
*In-text and gallery image captions do not require punctuation unless the caption requires more than one sentence.
 
*Wikipedia links use the template: [[:Template:Wp|<nowiki>{{Wp|WIKIPEDIA ARTICLE TITLE|NEW NAME IF NECESSARY}}</nowiki>]]
 
*Main article links use the template: [[:Template:Main|<nowiki>{{Main|MAIN ARTICLE}}</nowiki>]]
 
*Multiple main article links can be added in series using more vertical bars: <nowiki>{{Main|ART1|ART2|ART3}}</nowiki>
 
   
  +
:{|
==References==
 
  +
|-
:'''''Acepedia:References''' redirects here.''
 
  +
| ''Incorrect''
  +
| ''(passive)'':
  +
| {{!xt|Stonehenge was destroyed by Mobius 1.}}
  +
|-
  +
| ''Correct''
  +
| ''(active)'':
  +
| {{xt|Mobius 1 destroyed Stonehenge.}}
  +
|}
   
  +
===Tense===
Acepedia strives to be the most reliable source of ''Ace Combat'' information. In order to accomplish this, all information is encouraged to include '''references''' to sources of that information. Information that is not referenced may be subject to removal at any time. Read on for the guidelines of using references on Acepedia.
 
  +
Past tense must be used on event articles, articles describing entities that are deceased or no longer exist, or sections of any in-universe article detailing past events. "Current" time in-universe on {{SITENAME}} is generally considered to be fixed at the end of the game furthest down the timeline.
   
  +
:{|
*'''Almost every article''' must have the following code at the end of the article: [[:Template:Reflist|<nowiki>{{Reflist}}</nowiki>]]
 
  +
|-
**The reference list automatically adds a section header and the necessary code to present all references used on that article. A section header is not required prior to the reflist code.
 
  +
| ''Incorrect''
**Few types of articles do not need a reflist. For example, disambiguation pages will never have references.
 
  +
| ''(present)'':
*Information that is blatantly obvious or easily accessible should not be referenced. For example, the date of [[Operation Umbrella]] - September 19, 2004 - does not need a reference because it is presented to the user before the mission starts.
 
  +
| {{!xt|Mobius 1 destroys Stonehenge.}}
*References use the following code: [[:Template:Ref|<nowiki>{{Ref|NAME|INFO}}</nowiki>]]
 
  +
|-
**When referencing a mission:
 
  +
| ''Correct''
***NAME: AC##-M## (ex: AC04-M01), JA-M## (ex: JA-M01), AH-M##, INF-M##, etc. (use leading zeroes for all numbers less than 10)
 
  +
| ''(past)'':
***INFO: <nowiki>[[MISSION NAME]], ''[[GAME NAME]]''.</nowiki>
 
  +
| {{xt|Mobius 1 destroyed Stonehenge.}}
**When referencing a cutscene that you can view again through a "cutscene viewer" in the main menu:
 
  +
|}
***NAME: AC##-Cut## (ex: AC5-Cut02), AC04-Int## (ex: AC04-Int01), JA-Cut##, etc.
 
***INFO: <nowiki>Cutscene ##, ''[[GAME NAME]]''.</nowiki><br/>(use Interlude instead of Cutscene ONLY for ''AC04'')
 
**When referencing a cutscene that you ''cannot'' view again:
 
***NAME: AC##-M##-CutPrior/CutDuring/CutAfter
 
***INFO: <nowiki>Cutscene prior to/during/after [[MISSION NAME]], ''[[GAME NAME]]''.</nowiki>
 
**When referencing a non-''Ace Combat'' website, non-''Ace Combat'' news article, or tweet:
 
***NAME: WebsiteName-ArticleShorthand (ex: Twitter-PA, Famitsu-12102015, etc.)
 
***INFO: <nowiki>2=[URL Description]. Published [DATE]. Retrieved [DATE].</nowiki><br/>Note that Description is what will be shown instead of the URL itself. For articles and websites, use the title of the article or page. For Twitter, use "Twitter / USERNAME".
 
**When referencing something that we have recorded on the wiki:
 
***NAME: Create a shorthand descriptor based on what you're linking. For example, if INFO will be [[Usea Today: Asteroid on Collision Course With Earth!]], then make this "UseaTodayAsteroid".
 
***INFO: <nowiki>[[ARTICLE NAME]].</nowiki>
 
**When referencing something in print, like ''[[Aces At War: A History]]'':
 
***NAME: Shorthand descriptor of the printed name, followed by the page numbers. ex: AAW-125
 
***INFO: <nowiki>''[[NAME]]'', page ###.</nowiki> &nbsp;'''or'''&nbsp; <nowiki>''[[NAME]]'', pages ###-###.</nowiki>
 
*To use a reference more than once, use the above code for the '''first reference on the article''', and then use the following code for all subsequent uses: [[:Template:Refcall|<nowiki>{{Refcall|NAME}}</nowiki>]]
 
**NAME is the same NAME from the first reference.
 
   
  +
Present tense must be used on gameplay articles, and should be used everywhere else where it does not conflict with the past tense guideline.
[[Category:Administration]]
 
  +
  +
===Numbers===
  +
{{Shortcut|AP:NUM|AP:Numbers}}
  +
====Standard====
  +
In prose, numbers less than 11 should be spelled out ({{xt|seven targets}}, not {{!xt|7 targets}}). Numbers greater than ten should be displayed numerically ({{xt|77}}, not {{!xt|seventy-seven}}). The following exceptions apply:
  +
*''General'' numbers in the millions or higher can be displayed in the hybrid "X million" format ({{xt|Nearly 1 million Useans became refugees after Ulysses}}).
  +
*The above exception has its own exception when exact numbers must be provided, such as in aircraft or weapon prices. '''Never hybridize these numbers.''' When displaying these long numerals, commas must be used for separation of thousand-degrees whereas periods must be used to denote decimals if necessary ({{xt|123,456,789.01}}).
  +
*When referring to the passage of time, numbers should always be displayed numerically ({{xt|under 7 minutes}}, {{xt|3 hours later}}).
  +
  +
====Dates====
  +
In prose, dates follow the month-day-year convention with the month name written out in full: {{xt|The Continental War ended on September 19, 2005.}} Do not use suffixes (–st, –nd, –rd or –th) in this style ({{xt|September 19}}, not {{!xt|September 19th}}).
  +
  +
If a full date appears in the middle of a sentence, commas should appear before and after the year. If a date omits the day or the year, commas are unnecessary.
  +
  +
:{|
  +
|-
  +
| ''Incorrect''
  +
| {{!xt|On September 19, 2005 the Continental War ended.}}
  +
|-
  +
| ''Correct''
  +
| {{xt|On September 19, 2005, the Continental War ended.}}
  +
|-
  +
| ''Incorrect''
  +
| {{!xt|The Continental War ended in September, 2005.}}
  +
|-
  +
| ''Correct''
  +
| {{xt|The Continental War ended in September 2005.}}
  +
|}
  +
  +
====Times====
  +
Times follow military 24-hour conventions and are presented in local time. No colon is necessary, and there is no space between the time and the "hrs" abbreviation ({{xt|Operation Firefly commenced at 0000hrs}}).
  +
  +
====Coordinates====
  +
All coordinates on {{SITENAME}} require [[AP:REF|references]] and should follow the degrees (°) N/E/S/W convention where possible ({{xt|123°45"67'N, 89°12"34'E}}). Location coordinates shouldn't be presented in an article except in an infobox. Use relative positions in prose instead ({{xt|Belka is east of Osea}}).
  +
  +
===Other===
  +
*Third-person should always be used on articles ({{xt|he/she/they}}, not {{!xt|I}} or {{!xt|you}}). In instances where a gender is not certain (the player playing a game or a player character who is never given a pronoun), the singular "they" and "themself" should be used.
  +
*When using possessive forms of singular and proper nouns ending with s, append ''{{'}}'' without an s at the end:
  +
:{|
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|Mobius's}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|Mobius'}}
  +
|}
  +
*Squadron names are collective nouns, which means they take singular pronouns:
  +
:{|
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|Wardog Squadron were in Sudentor}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|Wardog Squadron was in Sudentor}}
  +
|}
  +
  +
==Formality==
  +
Formal use of language is mandatory on all canon encyclopedia articles e.g. {{xt|Mobius 1 is a highly-recognized ace pilot in Usea}}, not {{!xt|Mobius 1 the coolest pilot ever}}.
  +
  +
Uncontracted forms such as {{xt|''do not''}} or {{xt|''it is''}} are the default in encyclopedic style; {{!xt|''don't''}} and {{!xt|''it's''}} are too informal.
  +
  +
On encyclopedia articles, avoid such phrases as {{!xt|''remember that''}} and {{!xt|''note that''}}, which address readers directly in a less-than-encyclopedic tone. Similarly, phrases such as {{!xt|''of course'', ''naturally'', ''obviously'', ''clearly''}}, and {{!xt|''actually''}} make presumptions about readers' knowledge, and call into question the reason for including the information in the first place. Do not tell readers that something is {{!xt|ironic, surprising, unexpected, funny, amusing, coincidental, unfortunate}}, etc. This supplies a point of view. Simply state the sourced facts and allow readers to draw their own conclusions. Uses of {{!xt|''however''}} should be minimal since it takes up unnecessary space.
  +
  +
Canon encyclopedia articles should be written as if the in-game world was the real one. Mission names and other gameplay elements should not be stated in a sentence, and the characters should not be treated as fictional constructs.
  +
  +
==Article titles==
  +
{{Shortcut|AP:TITLE}}
  +
An article title is a convenient label for the article, which distinguishes it from other articles. It does not have to be the name of the subject; many article titles are descriptions of the subject or disambiguate from similar article titles.
  +
  +
The following points are critical to formatting article titles:
  +
*'''Use "sentence case" or "sentence-style":''' The initial letter of a title is capitalized; otherwise, capital letters are used only where they would be used in a normal sentence e.g. {{xt|Aircraft carrier}}, not {{!xt|Aircraft Carrier}}.
  +
*'''Use the singular form:''' Article titles should be singular e.g. {{xt|Tank}}, not {{!xt|Tanks}}.
  +
*'''Use full names without ranks for characters:''' Articles about characters should avoid the title or rank, unless the character is known only by the title e.g. {{xt|Allen C. Hamilton}}, not {{!xt|Major Allen C. Hamilton}}.
  +
*'''Use parentheses to distinguish similar articles:''' e.g. {{xt|Kei Nagase (AC2)}}, {{xt|Kei Nagase (AC5)}}, or {{xt|Kei Nagase (Ikaros)}}.
  +
  +
==Section headings==
  +
{{Shortcut|AP:HEADING}}
  +
*Headings should '''not contain links'''.
  +
*Heading should not contain citations.
  +
*Headings should not contain images of any kind.
  +
  +
For sections that feature a combination of quotes, main article links, images, and infoboxes directly below the heading, the following guidelines should be practiced:
  +
*A section should only start with an image ''or'' an infobox (or neither), not both. These take first priority over quotes and main article links.
  +
*A section should only start with a quote ''or'' a main article link (or neither), not both. These should come after an image or infobox at the start of a section, if there are any.
  +
  +
==Capitalization==
  +
'''Unnecessary capitalization should be avoided.''' For example, use {{xt|coup d'état}} rather than {{!xt|Coup D'état}}. This is sometimes referred to as the "down style". Capitalization should be reserved for proper nouns and the start of sentences only.
  +
  +
==="The"===
  +
In general, do not capitalize a definite article in the middle of a sentence. However, some idiomatic exceptions, including most titles of artistic works, should be quoted exactly according to common usage.
  +
  +
:{|
  +
|-
  +
| ''Incorrect''
  +
| ''(generic)'':
  +
| {{!xt|an event article about The Liberation of Gracemeria}}
  +
|-
  +
| ''Correct''
  +
| ''(generic)'':
  +
| {{xt|an event article about the liberation of Gracemeria}}
  +
|-
  +
| ''Incorrect''
  +
| ''(title)'':
  +
| {{!xt|a mission article about "the liberation of Gracemeria"}}
  +
|-
  +
| ''Correct''
  +
| ''(title)'':
  +
| {{xt|a mission article about "The Liberation of Gracemeria"}}
  +
|}
  +
  +
===Ranks and titles===
  +
*'''In generic use''', apply lower case for words such as ''lieutenant'' and ''captain'' e.g. {{xt|Bartlett was an air squadron captain}}.
  +
*'''In parts of a person's title''', begin such words with a capital letter e.g. {{xt|Captain Bartlett}}, not {{!xt|captain Bartlett}}.
  +
*'''Public office names''' are treated as proper nouns e.g. {{xt|the President of Osea}}. Royal styles are similarly capitalized e.g. {{xt|Her Majesty}}; exceptions may apply for particular offices.
  +
  +
===Locations===
  +
*'''Names of institutions''' are proper nouns and must be capitalized e.g. {{xt|Heierlark Air Force Base}}.
  +
*'''Generic words''' for institutions should not be normally capitalized e.g. {{xt|air base}}, {{xt|air force base}}. In situations where a generic term may conflict with another proper noun, try rewording the sentence:
  +
  +
:{|
  +
|-
  +
| ''Incorrect''
  +
| ''(name)'':
  +
| {{!xt|they retreated to Heierlark air force base}}
  +
|-
  +
| ''Correct''
  +
| ''(name)'':
  +
| {{xt|they retreated to Heierlark Air Force Base}}
  +
|-
  +
| ''Incorrect''
  +
| ''(generic)'':
  +
| {{!xt|the Osean Air Force Base near Oured}}
  +
|-
  +
| ''Misleading''
  +
| ''(generic)'':
  +
| {{!xt|the Osean air force base near Oured}}
  +
|-
  +
| ''Correct''
  +
| ''(generic)'':
  +
| {{xt|the Osean air base near Oured}}
  +
|-
  +
| ''Correct''
  +
| ''(generic)'':
  +
| {{xt|the OADF air base near Oured}}
  +
|}
  +
  +
===Calendar items===
  +
'''Seasons''' should be in lower case e.g. {{xt|in the summer}}; {{xt|the winter holidays}}.
  +
  +
===Celestial bodies===
  +
Names of celestial bodies, such as planets and constellations, are proper nouns and therefore '''do take capitals''' e.g. {{xt|Earth}}. However, capitalization of a definite article should follow common usage e.g. {{xt|the Southern Cross}}, not {{!xt|The Southern Cross}}.
  +
  +
Generic descriptors of celestial bodies should remain lowercase e.g. {{xt|a moon of Jupiter}} as opposed to {{!xt|a Moon of Jupiter}}. Generic descriptors should only be capitalized if a subject is commonly referred to by that descriptor e.g. {{xt|Earth's Moon}}.
  +
  +
==Italics==
  +
Titles of works of literature and art, especially games, should be italicized at all times e.g. {{xt|Cipher is the hero of ''Ace Combat Zero: The Belkan War''}} or {{xt|Cipher is the hero of ''Ace Combat Zero''}}.
  +
  +
Missions, published articles, chapters, songs, and other short works should not be italicized. Instead, use double quotes around them e.g. {{xt|"Sitting Duck"}}. Quotations should not be italicized either; see [[#Quotation marks|§&nbsp;Quotation marks]] for the proper punctuation.
  +
  +
When italicizing a link, put the apostrophes outside of the brackets instead of masking the link. Link masking should only be done if more than the article name is being italicized, but consider reorganizing the link in those circumstances:
  +
  +
:{|
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|<code><nowiki>[[Ace Combat|''Ace Combat'']]</nowiki></code>}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|<code><nowiki>''[[Ace Combat]]''</nowiki></code>}}
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|<code><nowiki>[[Ace Combat|''Ace Combat'' games]]</nowiki></code>}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|<code><nowiki>''[[Ace Combat]]'' games</nowiki></code>}}
  +
|}
  +
  +
==Punctuation==
  +
===Quotation marks===
  +
*'''Do not use typographic marks''', otherwise known as curly or smart quotation marks.
  +
::{|
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|‘...’ and “...”}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|'...' and "..."}}
  +
|}
  +
*In-text quotations should be surrounded by "double quotation marks". Do NOT use the in-game <<&nbsp;arrow&nbsp;quotes&nbsp;>> e.g. {{xt|"Yo Buddy, you still alive?"}} not {{!xt|<<&nbsp;Yo Buddy, you still alive?&nbsp;>>}}.
  +
**Quotations inside of quotations should be surrounded by 'single quotation marks' e.g. {{xt|"Decrypting message. 'Yo Buddy, you still alive?' It's...!"}}
  +
*Punctuation marks following quotations should go ''outside'' of the quotation marks, except if the same punctuation will end the surrounding sentence or the quotation itself:
  +
*:{{xt|Pixy said, "Looks like we were just a couple of decoys."}}
  +
*:{{xt|"Looks like we were just a couple of decoys", Pixy said.}}
  +
*When the title of an article appearing in the lead paragraph requires quotation marks (for example, the title of a mission or song), the quotation marks should not be in boldface since they are not part of the title e.g. {{xt|"'''Sitting Duck'''"}}.
  +
  +
===Ellipses===
  +
An ellipsis is an omission, often used in a printed record of conversation. The ellipsis is represented by '''ellipsis points''': a set of three dots.
  +
  +
====Style====
  +
Ellipsis points (plural ''ellipses'') have traditionally been implemented in three ways:
  +
*'''Recommended''': Three unspaced periods ({{xt|...}}). This is the easiest way in the context of web publishing, and gives a predictable appearance in HTML.
  +
*'''Not recommended''': Three spaced periods ({{!xt|. . .}}). 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 e.g. "<code>&amp;nbsp;.&amp;nbsp;.&amp;nbsp;.&amp;nbsp;</code>".
  +
*'''Not 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.
  +
  +
====Implementation====
  +
Use an ellipsis if material is omitted in the course of a quotation, with the following guidelines:
  +
*Put a space on each side of an ellipsis, except there should be no space between an ellipsis and...
  +
**a quotation mark directly following the ellipsis
  +
**any bracket the ellipsis is inside of
  +
**sentence-final punctuation, or a colon, semicolon, or comma directly following the ellipsis
  +
*Only place terminal punctuation after an ellipsis if it is textually important (as is often the case with exclamation marks and question marks).
  +
*Use non-breaking spaces (<code>&amp;nbsp;</code>) only as needed to prevent improper line breaks, for example:
  +
**To keep a quotation mark from being separated from the start of the quotation ({{xt|"...<code>&amp;nbsp;</code>we don't have to worry about any radar"}}).
  +
**To keep the ellipsis from wrapping to the next line ({{xt|"Those nukes are exactly why the Belkans have lowered themselves to<code>&amp;nbsp;</code>... pitting two countries against each other"}}).
  +
*Do not use ellipsis to represent a pause in speech, unless it is a direct quotation that includes the ellipsis.
  +
**In the very rare cases where ellipses are used for both material omission and speech pauses for a single quotation, the ellipsis used for material omission should have square brackets around it [...]. Do not use square brackets otherwise.
  +
  +
===Others===
  +
*If a list element is only a name or otherwise not a full sentence, no punctuation is necessary at the end.
  +
*Image captions do not require punctuation unless the caption has more than one sentence.
  +
*Commas should be used according to '''serial comma''' usage. However, in cases where it would cause ambiguity, try rephrasing the phrase.
  +
::{|
  +
|-
  +
| ''Incorrect:''
  +
| {{!xt|Cipher, Pixy and PJ}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|Cipher, Pixy, and PJ}}
  +
|-
  +
| ''Ambiguous:''
  +
| {{!xt|Yellow 13, a flight mechanic, and Yellow 4}}
  +
|-
  +
| ''Correct:''
  +
| {{xt|Yellow 13, Yellow 4, and a flight mechanic}}
  +
|}
  +
*Colons should only be used to indicate the start of a list or the start of a sentence that describes what came before the colon. The first word following a colon is capitalized if that word begins a new grammatical sentence. Operation names do not have colons unless directly specified.
  +
*Semicolons can be used in place of a period between two independent but related sentences, but should be used to separate items in a list when commas are also used in the middle of an item's description.
  +
*Hyphens must not be used except in specific circumstances. Instead, use an ''em dash'' (—) in place of commas and an ''en dash'' (–) for number ranges. Do not use spaces before or after either of these dashes.
  +
  +
==Abbreviations==
  +
===Games===
  +
'''Do not abbreviate game titles in prose''' e.g. {{!xt|Cipher is the hero of ACZ}}. Only abbreviate game titles in situations where space is limited such as infoboxes or tabbers. Use the following abbreviations in those situations and '''do not italicize abbreviations''':
  +
:AC1, AC2, AC3, AC04 (note: {{xt|AC04}}, not {{!xt|AC4}}), AC5, AC6, AC7
  +
:ACZ, ACX, Xi, JA, AH, Legacy (or 3D), Infinity (or INF)
  +
  +
If using multiple game abbreviations, such as in an infobox, denote them chronologically separated by slashes e.g. {{xt|AC2/3/04/X}}.
  +
  +
===Organizations===
  +
An organization's abbreviated name must follow the convention provided by the latest game e.g. "Independent State Allied Forces" is shortened to "{{xt|ISAF}}" as stated in ''Ace Combat 5'', not "{{!xt|Allies}}" as sometimes stated in ''Ace Combat 04''.
  +
  +
==Asteroid terminology==
  +
Use the following terms to refer to certain aspects of asteroids:
  +
*'''asteroid''': the main celestial body itself e.g. {{xt|the Ulysses 1994XF04 asteroid}}
  +
*'''fragments''': the pieces of an asteroid splitting apart in the atmosphere e.g. {{xt|Stonehenge attacked Ulysses fragments}}
  +
*'''meteorite''': any asteroid fragments that land on the planet surface, sometimes causing a crater, e.g. {{xt|the meteorites that struck Farbanti}}
  +
*'''meteor''': the flash of light from a fragment entering the atmosphere, '''not''' the fragment itself e.g. {{xt|meteors were visible over Gracemeria}}
  +
  +
{{Notelist}}

Latest revision as of 21:41, 15 October 2019

page
This page documents a policy for Acepedia.
It describes a standard that all editors should normally follow.
Feedback, suggestions, or concerns should be addressed on the talk page. Any changes should reflect consensus.
Shortcuts:
AP:MoS
AP:MOS

Acepedia's Manual of Style (often abbreviated as MoS or MOS) is a style manual for all main namespace articles and files. It helps keep articles in their highest quality by maintaining consistency, clarity, and precision. Please do your best to adhere to the guidelines outlined below whenever possible. Special cases may warrant exceptions to these guidelines. Keep in mind that the Manual of Style is a loose document to assist in better editing; it does not necessarily apply to personal or discussion areas.

Spelling

Language

American English spelling should be used on all canon encyclopedia articles, on all templates transcribed on articles, and on all official projects and blog posts. American spelling is preferred over British since Japanese culture surrounding English education leans more towards American. There are the following exceptions:

  • Regional variations in spelling may be used in all other contexts on Acepedia, such as comments, message walls, user pages, blog posts, and Discussions.
  • If quoting a source or transcript, never alter any part of the quotation, even if it does not use American spelling.

In addition, if a word is interchangeably used with or without a space in the middle (e.g. airstrike or air strike), prefer the version with the space in the middle (air strike).[note 1]

Sic

The Latin adverb sic inserted after a quoted word or passage indicates that the quoted material was transcribed or translated exactly as found in the source text, complete with any erroneous spelling.

On Acepedia, any instances of misspelling (or incorrect grammar) that occur in quoted material should be followed by an instance of Template:Sic. This signifies to the reader and future editors that the error was not an editing mistake, rather it was quoted directly from the Ace Combat game or other material cited. This should only be done for quoted material, transcripts, or the like, not for main article prose. False insertions of the Sic template are not allowed; if an editing mistake occurs, particularly in spelling, it should be corrected as per § Language.

Grammar

Voice

Use the active voice to outline and describe events. The passive voice should be used sparingly.

Incorrect (passive): Stonehenge was destroyed by Mobius 1.
Correct (active): Mobius 1 destroyed Stonehenge.

Tense

Past tense must be used on event articles, articles describing entities that are deceased or no longer exist, or sections of any in-universe article detailing past events. "Current" time in-universe on Acepedia is generally considered to be fixed at the end of the game furthest down the timeline.

Incorrect (present): Mobius 1 destroys Stonehenge.
Correct (past): Mobius 1 destroyed Stonehenge.

Present tense must be used on gameplay articles, and should be used everywhere else where it does not conflict with the past tense guideline.

Numbers

Standard

In prose, numbers less than 11 should be spelled out (seven targets, not 7 targets). Numbers greater than ten should be displayed numerically (77, not seventy-seven). The following exceptions apply:

  • General numbers in the millions or higher can be displayed in the hybrid "X million" format (Nearly 1 million Useans became refugees after Ulysses).
  • The above exception has its own exception when exact numbers must be provided, such as in aircraft or weapon prices. Never hybridize these numbers. When displaying these long numerals, commas must be used for separation of thousand-degrees whereas periods must be used to denote decimals if necessary (123,456,789.01).
  • When referring to the passage of time, numbers should always be displayed numerically (under 7 minutes, 3 hours later).

Dates

In prose, dates follow the month-day-year convention with the month name written out in full: The Continental War ended on September 19, 2005. Do not use suffixes (–st, –nd, –rd or –th) in this style (September 19, not September 19th).

If a full date appears in the middle of a sentence, commas should appear before and after the year. If a date omits the day or the year, commas are unnecessary.

Incorrect On September 19, 2005 the Continental War ended.
Correct On September 19, 2005, the Continental War ended.
Incorrect The Continental War ended in September, 2005.
Correct The Continental War ended in September 2005.

Times

Times follow military 24-hour conventions and are presented in local time. No colon is necessary, and there is no space between the time and the "hrs" abbreviation (Operation Firefly commenced at 0000hrs).

Coordinates

All coordinates on Acepedia require references and should follow the degrees (°) N/E/S/W convention where possible (123°45"67'N, 89°12"34'E). Location coordinates shouldn't be presented in an article except in an infobox. Use relative positions in prose instead (Belka is east of Osea).

Other

  • Third-person should always be used on articles (he/she/they, not I or you). In instances where a gender is not certain (the player playing a game or a player character who is never given a pronoun), the singular "they" and "themself" should be used.
  • When using possessive forms of singular and proper nouns ending with s, append ' without an s at the end:
Incorrect: Mobius's
Correct: Mobius'
  • Squadron names are collective nouns, which means they take singular pronouns:
Incorrect: Wardog Squadron were in Sudentor
Correct: Wardog Squadron was in Sudentor

Formality

Formal use of language is mandatory on all canon encyclopedia articles e.g. Mobius 1 is a highly-recognized ace pilot in Usea, not Mobius 1 the coolest pilot ever.

Uncontracted forms such as do not or it is are the default in encyclopedic style; don't and it's are too informal.

On encyclopedia articles, avoid such phrases as remember that and note that, which address readers directly in a less-than-encyclopedic 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 information in the first place. Do not tell readers that something is ironic, surprising, unexpected, funny, amusing, coincidental, unfortunate, etc. This supplies a point of view. Simply state the sourced facts and allow readers to draw their own conclusions. Uses of however should be minimal since it takes up unnecessary space.

Canon encyclopedia articles should be written as if the in-game world was the real one. Mission names and other gameplay elements should not be stated in a sentence, and the characters should not be treated as fictional constructs.

Article titles

An article title is a convenient label for the article, which distinguishes it from other articles. It does not have to be the name of the subject; many article titles are descriptions of the subject or disambiguate from similar article titles.

The following points are critical to formatting article titles:

  • Use "sentence case" or "sentence-style": The initial letter of a title is capitalized; otherwise, capital letters are used only where they would be used in a normal sentence e.g. Aircraft carrier, not Aircraft Carrier.
  • Use the singular form: Article titles should be singular e.g. Tank, not Tanks.
  • Use full names without ranks for characters: Articles about characters should avoid the title or rank, unless the character is known only by the title e.g. Allen C. Hamilton, not Major Allen C. Hamilton.
  • Use parentheses to distinguish similar articles: e.g. Kei Nagase (AC2), Kei Nagase (AC5), or Kei Nagase (Ikaros).

Section headings

  • Headings should not contain links.
  • Heading should not contain citations.
  • Headings should not contain images of any kind.

For sections that feature a combination of quotes, main article links, images, and infoboxes directly below the heading, the following guidelines should be practiced:

  • A section should only start with an image or an infobox (or neither), not both. These take first priority over quotes and main article links.
  • A section should only start with a quote or a main article link (or neither), not both. These should come after an image or infobox at the start of a section, if there are any.

Capitalization

Unnecessary capitalization should be avoided. For example, use coup d'état rather than Coup D'état. This is sometimes referred to as the "down style". Capitalization should be reserved for proper nouns and the start of sentences only.

"The"

In general, do not capitalize a definite article in the middle of a sentence. However, some idiomatic exceptions, including most titles of artistic works, should be quoted exactly according to common usage.

Incorrect (generic): an event article about The Liberation of Gracemeria
Correct (generic): an event article about the liberation of Gracemeria
Incorrect (title): a mission article about "the liberation of Gracemeria"
Correct (title): a mission article about "The Liberation of Gracemeria"

Ranks and titles

  • In generic use, apply lower case for words such as lieutenant and captain e.g. Bartlett was an air squadron captain.
  • In parts of a person's title, begin such words with a capital letter e.g. Captain Bartlett, not captain Bartlett.
  • Public office names are treated as proper nouns e.g. the President of Osea. Royal styles are similarly capitalized e.g. Her Majesty; exceptions may apply for particular offices.

Locations

  • Names of institutions are proper nouns and must be capitalized e.g. Heierlark Air Force Base.
  • Generic words for institutions should not be normally capitalized e.g. air base, air force base. In situations where a generic term may conflict with another proper noun, try rewording the sentence:
Incorrect (name): they retreated to Heierlark air force base
Correct (name): they retreated to Heierlark Air Force Base
Incorrect (generic): the Osean Air Force Base near Oured
Misleading (generic): the Osean air force base near Oured
Correct (generic): the Osean air base near Oured
Correct (generic): the OADF air base near Oured

Calendar items

Seasons should be in lower case e.g. in the summer; the winter holidays.

Celestial bodies

Names of celestial bodies, such as planets and constellations, are proper nouns and therefore do take capitals e.g. Earth. However, capitalization of a definite article should follow common usage e.g. the Southern Cross, not The Southern Cross.

Generic descriptors of celestial bodies should remain lowercase e.g. a moon of Jupiter as opposed to a Moon of Jupiter. Generic descriptors should only be capitalized if a subject is commonly referred to by that descriptor e.g. Earth's Moon.

Italics

Titles of works of literature and art, especially games, should be italicized at all times e.g. Cipher is the hero of Ace Combat Zero: The Belkan War or Cipher is the hero of Ace Combat Zero.

Missions, published articles, chapters, songs, and other short works should not be italicized. Instead, use double quotes around them e.g. "Sitting Duck". Quotations should not be italicized either; see § Quotation marks for the proper punctuation.

When italicizing a link, put the apostrophes outside of the brackets instead of masking the link. Link masking should only be done if more than the article name is being italicized, but consider reorganizing the link in those circumstances:

Incorrect: [[Ace Combat|''Ace Combat'']]
Correct: ''[[Ace Combat]]''
Incorrect: [[Ace Combat|''Ace Combat'' games]]
Correct: ''[[Ace Combat]]'' games

Punctuation

Quotation marks

  • Do not use typographic marks, otherwise known as curly or smart quotation marks.
Incorrect: ‘...’ and “...”
Correct: '...' and "..."
  • In-text quotations should be surrounded by "double quotation marks". Do NOT use the in-game << arrow quotes >> e.g. "Yo Buddy, you still alive?" not << Yo Buddy, you still alive? >>.
    • Quotations inside of quotations should be surrounded by 'single quotation marks' e.g. "Decrypting message. 'Yo Buddy, you still alive?' It's...!"
  • Punctuation marks following quotations should go outside of the quotation marks, except if the same punctuation will end the surrounding sentence or the quotation itself:
    Pixy said, "Looks like we were just a couple of decoys."
    "Looks like we were just a couple of decoys", Pixy said.
  • When the title of an article appearing in the lead paragraph requires quotation marks (for example, the title of a mission or song), the quotation marks should not be in boldface since they are not part of the title e.g. "Sitting Duck".

Ellipses

An ellipsis is an omission, often used in a printed record of conversation. The ellipsis is represented by ellipsis points: a set of three dots.

Style

Ellipsis points (plural ellipses) have traditionally been implemented in three ways:

  • Recommended: Three unspaced periods (...). This is the easiest way in the context of web publishing, and gives a predictable appearance in HTML.
  • Not recommended: Three spaced periods (. . .). 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 e.g. "&nbsp;.&nbsp;.&nbsp;.&nbsp;".
  • Not recommended: Pre-composed ellipsis character (); generated with the &hellip; character entity, or as a literal "…". This is harder to input and edit, and too small in some fonts.

Implementation

Use an ellipsis if material is omitted in the course of a quotation, with the following guidelines:

  • Put a space on each side of an ellipsis, except there should be no space between an ellipsis and...
    • a quotation mark directly following the ellipsis
    • any bracket the ellipsis is inside of
    • sentence-final punctuation, or a colon, semicolon, or comma directly following the ellipsis
  • Only place terminal punctuation after an ellipsis if it is textually important (as is often the case with exclamation marks and question marks).
  • Use non-breaking spaces (&nbsp;) only as needed to prevent improper line breaks, for example:
    • To keep a quotation mark from being separated from the start of the quotation ("...&nbsp;we don't have to worry about any radar").
    • To keep the ellipsis from wrapping to the next line ("Those nukes are exactly why the Belkans have lowered themselves to&nbsp;... pitting two countries against each other").
  • Do not use ellipsis to represent a pause in speech, unless it is a direct quotation that includes the ellipsis.
    • In the very rare cases where ellipses are used for both material omission and speech pauses for a single quotation, the ellipsis used for material omission should have square brackets around it [...]. Do not use square brackets otherwise.

Others

  • If a list element is only a name or otherwise not a full sentence, no punctuation is necessary at the end.
  • Image captions do not require punctuation unless the caption has more than one sentence.
  • Commas should be used according to serial comma usage. However, in cases where it would cause ambiguity, try rephrasing the phrase.
Incorrect: Cipher, Pixy and PJ
Correct: Cipher, Pixy, and PJ
Ambiguous: Yellow 13, a flight mechanic, and Yellow 4
Correct: Yellow 13, Yellow 4, and a flight mechanic
  • Colons should only be used to indicate the start of a list or the start of a sentence that describes what came before the colon. The first word following a colon is capitalized if that word begins a new grammatical sentence. Operation names do not have colons unless directly specified.
  • Semicolons can be used in place of a period between two independent but related sentences, but should be used to separate items in a list when commas are also used in the middle of an item's description.
  • Hyphens must not be used except in specific circumstances. Instead, use an em dash (—) in place of commas and an en dash (–) for number ranges. Do not use spaces before or after either of these dashes.

Abbreviations

Games

Do not abbreviate game titles in prose e.g. Cipher is the hero of ACZ. Only abbreviate game titles in situations where space is limited such as infoboxes or tabbers. Use the following abbreviations in those situations and do not italicize abbreviations:

AC1, AC2, AC3, AC04 (note: AC04, not AC4), AC5, AC6, AC7
ACZ, ACX, Xi, JA, AH, Legacy (or 3D), Infinity (or INF)

If using multiple game abbreviations, such as in an infobox, denote them chronologically separated by slashes e.g. AC2/3/04/X.

Organizations

An organization's abbreviated name must follow the convention provided by the latest game e.g. "Independent State Allied Forces" is shortened to "ISAF" as stated in Ace Combat 5, not "Allies" as sometimes stated in Ace Combat 04.

Asteroid terminology

Use the following terms to refer to certain aspects of asteroids:

  • asteroid: the main celestial body itself e.g. the Ulysses 1994XF04 asteroid
  • fragments: the pieces of an asteroid splitting apart in the atmosphere e.g. Stonehenge attacked Ulysses fragments
  • meteorite: any asteroid fragments that land on the planet surface, sometimes causing a crater, e.g. the meteorites that struck Farbanti
  • meteor: the flash of light from a fragment entering the atmosphere, not the fragment itself e.g. meteors were visible over Gracemeria

Footnotes

  1. The specific example of air strike follows the usage of the term in Air Strike Mode, EMERGENCY AIR STRIKE, and some briefings and debriefings (Imminent Threat, Invincible Fleet, The Final Overture, etc.).