Bulbapedia:Manual of style: Difference between revisions

m
no edit summary
mNo edit summary
Line 4: Line 4:


==Keeping continuity with existing style==
==Keeping continuity with existing style==
The Manual of Style attempts to provide general guidelines for Bulbapedia's preferred style.  It cannot address every possible style dispute, and some styles or conventions may be established across Bulbapedia without being formally defined in the Manual of Style.  When a style is established (e.g. used used across multiple pages), or where two styles are used interchangeably, a style should not be changed without a good reason.  If you want to discuss using an alternate style, please use an article's Talk Page or discuss on the Manual of Style talk page if an edit is needed to the Manual of Style to reconcile differing styles.
The Manual of Style attempts to provide general guidelines for Bulbapedia's preferred style.  It cannot address every possible style dispute, and some styles or conventions may be established across Bulbapedia without being formally defined in the Manual of Style.  When a style is established (e.g. used across multiple pages), or where two styles are used interchangeably, a style should not be changed without a good reason.  If you want to discuss using an alternate style, please use an article's Talk Page or discuss on the Manual of Style talk page if an edit is needed to the Manual of Style to reconcile differing styles.


==General style guidance==
==General style guidance==
This section deals with general writing style across Bulbapedia.  For guidance using wikicode, see [[Bulbapedia:Wikicode|Bulbapedia's Wikicode page.]]
This section deals with the general writing style across Bulbapedia.  For guidance using wikicode, see [[Bulbapedia:Wikicode|Bulbapedia's Wikicode page.]]


===Article titles===
===Article titles===
Line 43: Line 43:
Check for spelling and grammatical errors before saving changes to a page; if you notice factual or spelling errors on a page other than the ones you have created, please correct the problems, as Bulbapedia is an open project. In order to avoid disagreements over factual accuracy, it is best to cite sources for controversial statements. If presenting one point of view, it is best to also present a contrasting opinion with it.   
Check for spelling and grammatical errors before saving changes to a page; if you notice factual or spelling errors on a page other than the ones you have created, please correct the problems, as Bulbapedia is an open project. In order to avoid disagreements over factual accuracy, it is best to cite sources for controversial statements. If presenting one point of view, it is best to also present a contrasting opinion with it.   


This policy does not prohibit Bulbapedia from including differeing opinions where they exist in the fandom or the games.  However, Bulbapedia does not take a stand on these differences or elevate one point of view over another.
This policy does not prohibit Bulbapedia from including differing opinions where they exist in the fandom or the games.  However, Bulbapedia does not take a stand on these differences or elevate one point of view over another.


===Names of people===
===Names of people===
All modern persons should have their name given in Western order. Since the definition of "modern" may vary from culture to culture, for the Japanese, all names from the [[wp:Taishō period|Taishō period]] onwards should be given in Western order. Names from the [[wp:Meiji restoration|Meiji restoration]] may be given in Western or Eastern order -- use prevailing convention on a person-by-person basis. Names prior to the Meiji restoration should be given in Eastern order.
All modern persons should have their names given in Western order. Since the definition of "modern" may vary from culture to culture, for the Japanese, all names from the [[wp:Taishō period|Taishō period]] onwards should be given in Western order. Names from the [[wp:Meiji restoration|Meiji restoration]] may be given in Western or Eastern order -- use prevailing convention on a person-by-person basis. Names prior to the Meiji restoration should be given in Eastern order.


When a person has a specific preference for the way their name is rendered, or where convention differs, use that instead. For example, use [[Hiromoto SIN-Ichi]], [[Ikue Ohtani]], and [[Rica Matsumoto]], instead of Shin'ichi Hiromoto, Ikue Ōtani, and Rika Matsumoto.
When a person has a specific preference for the way their name is rendered, or where convention differs, use that instead. For example, use [[Hiromoto SIN-Ichi]], [[Ikue Ohtani]], and [[Rica Matsumoto]], instead of Shin'ichi Hiromoto, Ikue Ōtani, and Rika Matsumoto.
Line 67: Line 67:
: An article for [[Pokémon Adventures]] characters, for example, [[Silver (Adventures)]]. Short link: {{Template|Adv}}.
: An article for [[Pokémon Adventures]] characters, for example, [[Silver (Adventures)]]. Short link: {{Template|Adv}}.
; TCG
; TCG
: An article for a product, set, or other aspect of the [[Pokémon Trading Card Game]], for example, [[Base Set (TCG)]]. Short link: {{Template|TCG}}
: An article for a product, set, or other aspects of the [[Pokémon Trading Card Game]], for example, [[Base Set (TCG)]]. Short link: {{Template|TCG}}
:: Specific cards within the TCG are identified using the TCG ID format, for example, [[Alakazam (Base Set 1)]]. Short link: {{Template|TCG ID}}
:: Specific cards within the TCG are identified using the TCG ID format, for example, [[Alakazam (Base Set 1)]]. Short link: {{Template|TCG ID}}
; TFG
; TFG
Line 90: Line 90:
With regards to romanized Japanese titles, omit macrons and apostrophes in the title (but create redirects from the accurate romanization if you so desire).
With regards to romanized Japanese titles, omit macrons and apostrophes in the title (but create redirects from the accurate romanization if you so desire).


Technical limitations include mandatory capitalization of the first letter of titles and the identical treatment of space, '''+''' and '''_''' as spaces. Use {{Template|Wrongtitle}} to make a note of any wrong titles due to technical limitations. Also note that formerly '''&''' was not an acceptable character, but now it is acceptable to use ''up to two'' ampersands in a title - more than two ampersands in a row will cause problems. Special care must be taken with '''?''', though usually things will work as expected.
Technical limitations include mandatory capitalization of the first letter of titles and the identical treatment of space, '''+''' and '''_''' as spaces. Use {{Template|Wrongtitle}} to make a note of any wrong titles due to technical limitations. Also, note that formerly '''&''' was not an acceptable character, but now it is acceptable to use ''up to two'' ampersands in a title - more than two ampersands in a row will cause problems. Special care must be taken with '''?''', though usually things will work as expected.


===Naming conventions===
===Naming conventions===
Line 102: Line 102:
* Evolutionary levels should be designated as "unevolved," "first evolution," and "second evolution" for Pokémon that have undergone zero, one, and two evolutions respectively during their development. The TCG terminology of "basic Pokémon," "stage 1 Pokémon" and "stage 2 Pokémon" are not used outside of the TCG pages.  
* Evolutionary levels should be designated as "unevolved," "first evolution," and "second evolution" for Pokémon that have undergone zero, one, and two evolutions respectively during their development. The TCG terminology of "basic Pokémon," "stage 1 Pokémon" and "stage 2 Pokémon" are not used outside of the TCG pages.  
** For example, in the TCG {{p|Pikachu}} and several other Pokémon are considered Basic Pokémon, but have a pre-evolved form, making them first-evolution Pokémon. This discrepancy typically applies to evolutionary families that include a [[baby Pokémon]].
** For example, in the TCG {{p|Pikachu}} and several other Pokémon are considered Basic Pokémon, but have a pre-evolved form, making them first-evolution Pokémon. This discrepancy typically applies to evolutionary families that include a [[baby Pokémon]].
* When writing episode names, write them as <code><nowiki>''[[Episode code|Episode name]]''</nowiki></code>; for example, the fifth episode of the [[original series]] is ''[[EP005|Showdown in Pewter City]]''.
* When writing episode or chapter names, write them as <code><nowiki>''[[Episode code|Episode name]]''</nowiki></code>; for example, the fifth episode of the [[original series]] is ''[[EP005|Showdown in Pewter City]]''.
** Note only English titles are used in this way otherwise the episode or chapter code is used, such as in [[XYS06]].
* When multiple numbered [[route]]s are to be listed, they should be listed in numerical order, and only the first should have any prefix to it; for example, "{{p|Jigglypuff}} appears on [[Route]]s {{rtn|3|Kanto}}, {{rtn|4|Kanto}}, {{rtn|5|Kanto}}, {{rtn|6|Kanto}}, {{rtn|7|Kanto}}, {{rtn|8|Kanto}}, {{rtn|34|Johto}}, {{rtn|35|Johto}}, and {{rtn|115|Hoenn}}, depending on the [[Core series|version]] played" is preferred to "{{p|Jigglypuff}} appears on {{rt|3|Kanto}}, {{rt|4|Kanto}}, {{rt|5|Kanto}}, {{rt|6|Kanto}}, {{rt|7|Kanto}}, {{rt|8|Kanto}}, {{rt|34|Johto}}, {{rt|35|Johto}}, and {{rt|115|Hoenn}} depending on the [[Core series|version]] played". The {{cat|Link templates|link template}} {{template|rtn}} can be used for handily linking route numbers.
* When multiple numbered [[route]]s are to be listed, they should be listed in numerical order, and only the first should have any prefix to it; for example, "{{p|Jigglypuff}} appears on [[Route]]s {{rtn|3|Kanto}}, {{rtn|4|Kanto}}, {{rtn|5|Kanto}}, {{rtn|6|Kanto}}, {{rtn|7|Kanto}}, {{rtn|8|Kanto}}, {{rtn|34|Johto}}, {{rtn|35|Johto}}, and {{rtn|115|Hoenn}}, depending on the [[Core series|version]] played" is preferred to "{{p|Jigglypuff}} appears on {{rt|3|Kanto}}, {{rt|4|Kanto}}, {{rt|5|Kanto}}, {{rt|6|Kanto}}, {{rt|7|Kanto}}, {{rt|8|Kanto}}, {{rt|34|Johto}}, {{rt|35|Johto}}, and {{rt|115|Hoenn}} depending on the [[Core series|version]] played". The {{cat|Link templates|link template}} {{template|rtn}} can be used for handily linking route numbers.