TechInfoDepot:Manual of Style

The Manual of Style (often abbreviated MoS or MOS) is a style guide for all TechInfoDepot articles. This page covers certain topics (such as punctuation) in full, and presents the key points of others. MOS subpages provide detailed guidance on particular topics or subject areas. These are linked in this page's menu and listed on the MOS Contents page.

MOS is TechInfoDepot's house style. It helps editors write articles with consistent, clear, and precise language, layout, and formatting. The goal is to make TechInfoDepot easier and more intuitive to use. Consistency in language, style, and formatting promotes clarity and cohesion. Writing should be clear and concise. Plain English works best: avoid ambiguity, jargon, and vague or unnecessarily complex wording.

Style and formatting choices should be consistent within an article, though not necessarily throughout TechInfoDepot as a whole. Where more than one style is acceptable, editors should not change an article from one of those styles to another without a substantial reason. Revert-warring over optional styles is unacceptable. If discussion cannot determine which style to use in an article, defer to the style used by the first major contributor.

Discuss style issues on the MOS talk page. Some of the past discussions that led to decisions on aspects of style guidance are recorded at the MOS register. In case of discrepancy, this page has precedence over its subpages and the TechInfoDepot:Simplified Manual of Style.

Article titles
When determining the title of an article, refer to the Article titles policy. A title should be recognizable (as a name or description of the topic), natural, sufficiently precise, concise, and consistent with the titles of related articles. If these criteria are in conflict, they need to be balanced against one another.

For guidance on formatting titles, see the Article title format section of the policy. The following points are noteworthy:
 * Use "sentence case", not "title case"; that is, the initial letter of a title is capitalized (except in rare cases, such as eBay), but otherwise, capital letters are used only where they would be used in a normal sentence (Funding of UNESCO projects, not Funding of UNESCO Projects).
 * To italicize a title, add the template italic title near the top of the article. The use of italics should conform to WP:ITALICS.
 * Do not use A, An, or The as the first word (Economy of the Second Empire, not The economy of the Second Empire), unless by convention it is an inseparable part of a name (The Hague) or it is part of the title of a work (A Clockwork Orange, The Tonight Show with Conan O'Brien).
 * Titles should normally be nouns or noun phrases: Early life, not In early life.
 * The final visible character should not be a punctuation mark unless it is part of a name (Saint-Louis-du-Ha! Ha!) or an abbreviation (Inverness City F.C.), or a closing round bracket or quotation mark is required (John Palmer (schooner)).

The guidance contained elsewhere in the MoS, particularly in the section below on punctuation, applies to all parts of an article, including the title. (The policy page TechInfoDepot:Article titles does not contain detailed rules about punctuation.)

Section organization
An article should begin with an introductory lead section, which does not contain section headings (see TechInfoDepot:Manual of Style/Lead section). The remainder is divided into sections, each with a section heading (see below) that can be nested in a hierarchy. If there are at least four section headings in the article, a navigable table of contents is generated automatically and displayed between the lead and the first heading.

If the topic of a section is also covered in more detail in a dedicated article, show this by inserting directly under the section heading (see also TechInfoDepot:Summary style).

As explained in more detail in Standard appendices and footers, optional appendix and footer sections containing the following lists may appear after the body of the article in the following order:
 * books or other works created by the subject of the article (under a section heading "Works", "Publications", "Discography", etc. as appropriate);
 * internal links to related English TechInfoDepot articles (section heading "See also");
 * notes and references (section heading "Notes" or "References", or a separate section for each; see Citing sources);
 * relevant books, articles, or other publications that have not been used as sources (section heading "Further reading");
 * relevant websites that have not been used as sources and do not appear in the earlier appendices (added as part of "Further reading" or in a separate section headed "External links").
 * internal links organized into navigational boxes (sometimes placed at the top in the form of sidebars)
 * categories
 * interlanguage links

Other article elements include disambiguation hatnotes (normally placed at the very top of the article) and infoboxes (usually placed before the lead section).

Section headings
Equal signs are used to mark the enclosed text as a section heading:  for a primary section;   for the next level (a subsection); and so on to the lowest-level subsection, with. (The highest heading level technically possible is ; but do not use it in articles, because it is reserved for the automatically generated top-level heading at the top of the page containing the title of the whole article.) Spaces between the equal signs and the heading text are optional, and will not affect the way the heading is displayed. The heading must be typed on a separate line. Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window. (Only two or more consecutive blank lines will add more white space in the public appearance of the page.)

The provisions in Article titles (above) generally apply to section headings as well (for example, headings are in sentence case, not title case). The following points apply specifically to section headings:
 * Headings should not refer redundantly to the subject of the article, or to higher-level headings, unless doing so is shorter or clearer. (Early life is preferable to His early life when his refers to the subject of the article; headings can be assumed to be about the subject unless otherwise indicated.)
 * Headings should not normally contain links, especially where only part of a heading is linked.
 * Section and subsection headings should preferably be unique within a page; otherwise section links may lead to the wrong place, and automatic edit summaries can be ambiguous.
 * Citations should not be placed within or on the same line as section and subsection headings.
 * Headings should not contain images, including flag icons.
 * Headings should not contain questions.

Before changing a section heading, consider whether you might be breaking existing links to that section. If there are many links to the old section title, create an anchor with that title to ensure that the links still work. Similarly, when linking to a section of an article, leave an invisible comment at that section, specifying the names of the linking articles so that if the title is altered, others can fix the links. For example:

Do not place an invisible comment outside the "== ==" markup but on the same line as the heading:

National varieties of English
The English TechInfoDepot prefers no major national variety of the language over any other. These varieties (e.g. American English vs. British English) differ in vocabulary (soccer vs. football), spelling (center vs. centre), date formatting ("April 13" vs. "13 April") and occasionally grammar (see Plurals, below). The following subsections describe how to determine the appropriate variety for an article. (The accepted style of punctuation is covered in the punctuation section, below.)

Articles such as English plural and Comparison of American and British English provide information on the differences between these major varieties of the language.

Opportunities for commonality 
TechInfoDepot tries to find words that are common to all varieties of English. Insisting on a single term or a single usage as the only correct option does not serve the purposes of an international encyclopedia.
 * Universally used terms are often preferable to less widely distributed terms, especially in article titles. For example, glasses is preferred to the national varieties spectacles (British English) and eyeglasses (American English); 'tens of millions' is preferable to crore (Indian English).
 * If one variant spelling appears in an article title, make a redirect page to accommodate the other variants, as with Artefact and Artifact, so that all variants can be used in searches and in linking.
 * Terms that are uncommon in some varieties of English, or that have divergent meanings, may be glossed to prevent confusion, for example,.
 * Use a commonly understood word or phrase in preference to one that has a different meaning because of national differences (rather than alternate, use alternative or alternating depending on which sense is intended).

Consistency within articles
While TechInfoDepot does not favor any national variety of English, within a given article the conventions of one particular variety should be followed consistently. The exceptions are:
 * quotations (do not alter the quotation to match the variety used in the main text; but see typographic conformity, below);
 * proper names (use the original spelling, for example United States Department of Defense and Australian Defence Force);
 * titles of works such as books, films, or songs (use the spelling of the edition consulted); and
 * explicit comparisons of varieties of English.

Strong national ties to a topic
An article on a topic that has strong ties to a particular English-speaking nation should use the English of that nation. For example:
 * Great Fire of London (British English)
 * American Civil War (American English)
 * Institutions of the European Union (British or Irish English)
 * Australian Defence Force (Australian English)
 * Vancouver, B.C. (Canadian English)
 * Usain Bolt (Jamaican Standard English)

For articles about modern writers or their works, it is sometimes decided to use the variety of English in which the subject wrote (especially if the writings are quoted). For example, the articles on J. R. R. Tolkien's works, such as The Lord of the Rings, use British English with Oxford spelling.

This guideline should not be used to claim national ownership of any article; see TechInfoDepot:Ownership of articles.

Retaining the existing variety
In general, disputes over which English variety to use in an article are strongly discouraged. Such debates waste time and engender controversy, mostly without accomplishing anything positive.

When an English variety's consistent usage has been established in an article, it is maintained in the absence of consensus to the contrary. With few exceptions (e.g. when a topic has strong national ties or a term/spelling carries less ambiguity), there is no valid reason for such a change.

When no English variety has been established and discussion cannot resolve the issue, the variety used in the first non-stub revision is considered the default. If no English variety was used consistently, the tie is broken by the first post-stub contributor to introduce text written in a particular English variety. The variety established for use in a given article can be documented by placing the appropriate Varieties of English template on its talk page.

An article should not be edited or renamed simply to switch from one valid use of English to another. Editors who alter an existing variety can be advised of this guideline via the placement of {{subst:uw-lang}} on their talk pages.

Capital letters
Sentence case rather than title case is used in TechInfoDepot article titles and section headings; see Article titles and Section headings above. For capitalization of list items, see Bulleted and numbered lists. Other points concerning capitalization are summarized below; full information can be found at the MoS page on capital letters.

Do not use capitals for emphasis
Do not use capital letters for emphasis; where wording alone cannot provide the emphasis, use italics.


 * Incorrect: It is not only a LITTLE (or Little) learning that is dangerous.
 * Correct: It is not only a little learning that is dangerous.

Capitalization of "The"
Generally do not capitalize the definite article in the middle of a sentence: an article about the United Kingdom (not about The United Kingdom). However there are some conventional exceptions, including most titles of artistic works: Tolkien wrote The Lord of the Rings (but Homer wrote the Odyssey); public transport in The Hague.

For treatment in band and album names, see TechInfoDepot:Manual of Style/Music.

Titles of works
The English-language titles of compositions (books and other print works, songs and other audio works, films and other visual media works, paintings and other artworks, etc.) are given in title case, in which every word is given an initial capital except for certain less important words (as detailed at WP:Manual of Style/Capital letters). The first and last words in a title are always capitalized. Capitalization in foreign-language titles varies, even over time within the same language; generally, retain the style of the original.
 * Correct: The Unbearable Lightness of Being
 * Correct: Hymnus an den heiligen Geist

Titles of people

 * In generic use, apply lower case for words such as president, king, and emperor (De Gaulle was a French president; Louis XVI was a French king; Three prime ministers attended the conference).
 * In parts of a person's title, begin such words with a capital letter (President Obama, not president Obama). Standard or commonly used names of an office are treated as proper nouns (The British Prime Minister is David Cameron; Hirohito was Emperor of Japan; Louis XVI was King of France). Royal styles are capitalized (Her Majesty; His Highness); exceptions may apply for particular offices.
 * For the use of titles and honorifics in biographical articles, see Honorific prefixes.

Religions, deities, philosophies, doctrines

 * Religions, sects, and churches and their followers (in noun or adjective form) start with a capital letter. Generally, "the" is not capitalized before such names (the Shī‘a, not The Shī‘a).
 * Religious texts (scriptures) are capitalized, but often not italicized (the Bhagavad Gita, the Qur’an, the Talmud, the Granth Sahib, the Bible). When "the" is used, it is not capitalized. Some derived adjectives are capitalized by convention, some are not (biblical, but Koranic); if unsure, check a dictionary.
 * Honorifics for deities, including proper nouns and titles, start with a capital letter (God, Allah, the Lord, the Supreme Being, the Great Spirit, the Horned One, Bhagavan). Do not capitalize "the" in such cases or when referring to major religious figures or characters from mythology (the Prophet, the Messiah, the Virgin). Common nouns for deities and religious figures are not capitalized (many gods; the god Woden; saints and prophets).
 * Pronouns for figures of veneration are not capitalized, even if capitalized in a religion's scriptures.
 * Broad categories of mythical or legendary beings start with lower-case letters (elf, fairy, nymph, unicorn, angel), although in derived works of fantasy, such as the novels of J. R. R. Tolkien and real-time strategy video games, initial capitals are sometimes used to indicate that the beings form a culture or race in a fictional universe. Capitalize the names or titles of individual creatures (the Minotaur, Pegasus) and of groups whose name and membership are fixed (the Magi, or the Three Wise Men, the Cherubim). Generalized references are not capitalized (these priests; several wise men; cherub-like).
 * Spiritual or religious events are capitalized only when referring to specific incidents or periods (the Great Flood and the Exodus; but annual flooding and an exodus of refugees).
 * Philosophies, theories, movements, and doctrines use lower case unless the name derives from a proper noun (capitalism versus Marxism) or has become a proper noun (republican, a system of political thought; Republican, a political party). Use lower case for doctrinal topics or canonical religious ideas (as opposed to specific events), even if they are capitalized by some religious adherents (virgin birth, original sin, transubstantiation).
 * Platonic or transcendent ideals are capitalized in the context of philosophical doctrine (Truth, the Good); used more broadly, they are in lower case (Superman represents American ideals of truth and justice). Use capitals for personifications represented in art (the guidebook mentioned statues of Justice and Liberty).

Calendar items

 * Months, days of the week, and holidays start with a capital letter (June, Monday; the Fourth of July refers only to the US Independence Day—otherwise July 4 or 4 July).
 * Seasons are in lower case (her last summer; the winter solstice; spring fever), except in personifications or in proper names for periods or events (Old Man Winter; the team had great success on the Spring Circuit).

Animals, plants, and other organisms
When using scientific names, capitalize the genus but not the species or taxonomic rank below species if present: Berberis darwinii, Erithacus rubecula superbus. No exception is made for proper names forming part of scientific names. Higher taxa (order, family, etc.) are capitalized in Latin (Carnivora, Felidae) but not in their English equivalents (carnivorans, felids).

Common (vernacular) names are given in lower case, except where proper names appear (zebras, mountain maple, gray wolf, but Przewalski's horse). Some editors prefer to capitalize the IOC-published common names of birds (Golden Eagle) in ornithological articles; do not apply this style to other categories. Use a consistent style for common names within an article. Create redirects from alternative capitalization forms of article titles.

General names for groups or types of animals are not capitalized except where they contain a proper name (oak, bottlenose dolphins, rove beetle, Van cat).

Celestial bodies

 * When used generally, the words  sun, earth, and moon  do not take capitals (The sun was peeking over the mountain top; The tribal people of the Americas thought of the whole earth as their home), except when the entity is personified (Sol Invictus ("Unconquered Sun") was the Roman sun god) or when the term names a specific astronomical body (The Moon orbits the Earth; but Io is a moon of Jupiter).
 * Names of planets, moons, asteroids, comets, stars, constellations, and galaxies are proper nouns, and therefore capitalized (The planet Mars can be seen tonight in the constellation Gemini, near the star Pollux; Halley's Comet is the most famous of the periodic comets; The Andromeda Galaxy is a spiral galaxy). The first letter of every word in such a name is capitalized (Alpha Centauri and not Alpha centauri; Milky Way, not Milky way).

Compass points
Do not capitalize directions such as north, nor their related forms (We took the northern road), except where they are parts of names (such as Great North Road or South Pole).

Capitalize names of regions if they have attained proper-name status, including informal conventional names (Southern California; the Western Desert), and derived terms for people (e.g. a Southerner as someone from the Southern United States). Do not capitalize descriptive names for regions that have not attained the status of proper names, such as southern Poland.

(Composite directions may or may not be hyphenated, depending on the style adopted in the article. Southeast Asia and northwest are more common in American English; but South-East Asia and north-west in British English. In cases such as north–south dialogue and east–west orientation an en dash is used; see en dashes, below.)

Institutions
Names of particular institutions are proper nouns and require capitals, but generic words for institutions (university, college, hospital, high school) do not. For example: The university offers programs in arts and sciences, but The University of Delhi offers ....

The word the at the start of a title is usually uncapitalized, but follow the institution's own usage (a degree from the University of Sydney; but researchers at The Ohio State University).

Similar considerations apply to political or geographical units, such as cities and islands: The city has a population of 55,000, but The City of Smithville ... (an official name). (Note also the use of the City to refer to the City of London.)

Ligatures
Ligatures should be used in languages in which they are standard, hence The meaning of Moreau's last words, clin d'œil, is disputed is preferable to The meaning of Moreau's last words, clin d'oeil, is disputed. Ligatures should not be used in English outside of names, hence Æthelstan was a pre-mediaeval king, not Æthelstan was a pre-mediæval king.

Abbreviations
Write out both the full version and the abbreviation at first occurrence
 * When an abbreviation is to be used in an article, give the expression in full at first, followed immediately by the abbreviation in parentheses (round brackets). In the rest of the article the abbreviation can then be used by itself:
 * the New Democratic Party (NDP) won the 1990 Ontario election with a significant majority, at the first mention of the New Democratic Party; and
 * the NDP quickly became unpopular with the voters, at a subsequent mention.


 * Make an exception for very common abbreviations; in most articles they require no expansion (PhD, DNA, USSR).


 * Do not apply initial capitals in a full version simply because capitals are used in the abbreviation.
 * {|style="background:transparent"


 * Correct (not a proper noun): || We used digital scanning (DS) technology
 * Incorrect: || We used Digital Scanning (DS) technology
 * Correct (a proper noun): || The film was produced by the British Broadcasting Corporation (BBC)
 * }
 * If the full version is already in round brackets, use a comma and or to indicate the abbreviation.
 * They first debated the issue in 1992 (at a convention of the New Democratic Party, or NDP)
 * }
 * If the full version is already in round brackets, use a comma and or to indicate the abbreviation.
 * They first debated the issue in 1992 (at a convention of the New Democratic Party, or NDP)

Plural and possessive forms
 * Acronyms, like other nouns, become plurals by adding -s or -es (they produced three CD-ROMs in the first year; the laptops were produced with three different BIOSes in 2006). As with other nouns, no apostrophe is used unless the form is a possessive.

Periods (full stops) and spaces
 * The letters in an acronym are generally not separated by periods (full stops) or blank spaces (GNP, NORAD, OBE, GmbH). Periods and spaces that were traditionally required have now dropped out of usage (PhD is now preferred over Ph.D. and Ph. D.). Periods are not used in units of measurement; see TechInfoDepot:Manual of Style/Dates and numbers. There are some traditional exceptions (i.e., e.g.; not ie, eg, i. e., e. g.); and see below for US and U.S.
 * Abbreviations formed by truncation (Hon. for Honorable), compression (cmte. for committee), or contraction (Dr. for Doctor) may or may not be closed with a period; a consistent style should be maintained within an article. A period is more usual in North American usage (Dr. Smith of 42 Drummond St.); no period is commonly preferred in British and other usage (Dr Smith of 42 Drummond St). Some British and other authorities prefer to drop the period from truncated and compressed abbreviations generally (XYZ Corp; ABC Ltd), a common practice in science writing. Regardless of punctuation, words that are abbreviated to more than one letter are spaced (op. cit. or op cit; not op.cit. or opcit). There are some exceptions: PhD (see above) for "Philosophiae Doctor"; BVetMed for "Bachelor of Veterinary Medicine".

US and U.S.
 * In American and Canadian English, U.S. (with periods) is the dominant abbreviation for United States. US (without periods) is more common in most other national forms of English. Some major American guides to style, such as The Chicago Manual of Style (16th ed.), now deprecate U.S. and prefer US. Use of periods for acronyms should be consistent within any given article, and congruent with the variety of English used by that article. In longer abbreviations incorporating the country's initials (USN, USAF), periods are not used. When the United States is mentioned with one or more other countries in the same sentence, U.S. or US may be too informal, especially at the first mention or as a noun instead of an adjective (France and the United States, not France and the U.S.). Do not use the spaced U. S., nor the archaic U.S. of A., except when quoting. Do not use U.S.A. or USA, except in a quotation or as part of a proper name (Team USA).

Circa
 * To indicate approximately, the unitalicized abbreviation c. (followed by a space) is preferred over circa, ca., or approx.

Do not use unwarranted abbreviations
 * Avoid abbreviations when they might confuse the reader, interrupt the flow, or appear informal. For example, do not use approx. for approximate or approximately, except to reduce the width of an infobox or a table of data, or in a technical passage in which the term occurs many times.
 * See also TechInfoDepot:Manual of Style/Dates and numbers for when to abbreviate units of measurement.

Do not invent abbreviations or acronyms
 * Generally avoid making up new abbreviations, especially acronyms (World Union of Billiards is good as a translation of Union Mondiale de Billard, but neither it nor the reduction WUB is used by the organization; so use the original name and its official abbreviation, UMB). If it is necessary to abbreviate a heading in a wide table of data, use widely recognized acronyms (for United States gross national product use US and GNP, with a link if the term has not already been written out: US GNP; do not use the made-up acronym USGNP).

HTML elements
 * Either the element or the  template can be used for abbreviations and acronyms: WHO or  will generate WHO; hovering over the rendered text causes a tooltip of the long form to pop up. MediaWiki, the software on which TechInfoDepot runs, does not support.

Ampersand
The ampersand (&) substitutes for the word and (it was a form of Latin et). In normal text, and should be used instead: January 1 and 2, not January 1 & 2. Retain ampersands in titles of works or organizations, such as The Tom & Jerry Show or AT&T. Ampersands may be used with consistency and discretion in tables, infoboxes, and similar contexts where space is limited. Modern editions of old texts routinely replace ampersands with and (just as they replace other disused glyphs, ligatures, and abbreviations), so an article's quotations may be cautiously modified, especially for consistency where different editions are quoted. (For similar allowable modifications see Quotations, below.)

Italics
Emphasis
 * Italics may be used sparingly to emphasize words in sentences (whereas boldface is normally not used for this purpose). Generally, the more highlighting in an article, the less its effectiveness.
 * Use italics when introducing terms, or distinguishing among them (The enamel organ is composed of the outer enamel epithelium, inner enamel epithelium, stellate reticulum, and stratum intermedium).

Titles


 * Use italics for the titles of works of literature and art, such as books, pamphlets, films (including short films), television series, music albums, and paintings. The titles of articles, chapters, songs, television episodes, and other short works are not italicized; they are enclosed in double quotation marks.
 * Italics are not used for major revered religious works (the Bible, the Qur'an, the Talmud).

Words as words
 * Use italics when mentioning a word or letter (see Use–mention distinction) or a string of words up to one full sentence (the term panning is derived from panorama, a word coined in 1787; the most commonly used letter in English is e). When a whole sentence is mentioned, quotation marks may be used instead, with consistency (The preposition in She sat on the chair is on; or The preposition in "She sat on the chair" is "on"). Mentioning (to discuss such features as grammar, wording, and punctuation) is different from quoting (in which something is usually expressed on behalf of a quoted source).

Foreign words
 * Use italics for phrases in other languages and for isolated foreign words that are not common in everyday English. Proper names (such as place names) in other languages, however, are not usually italicized.

Scientific names
 * Use italics for the scientific names of plants, animals and other organisms at the genus level and below (italicize Panthera leo but not Felidae). The hybrid sign is not italicized (Rosa ×damascena), nor is the "connecting term" required in three-part botanical names (Rosa gallica subsp. officinalis).

Quotations in italics
 * For quotations, use only quotation marks (for short quotations) or block quoting (for long ones), not italics. (See Quotations below.) This means that (1) a quotation is not italicized inside quotation marks or a block quote just because it is a quotation, and (2) italics are no substitute for proper quotation formatting. One way to distinguish long block quotes from ordinary text is to use quotation, which will box the text. Citation links may not work within such templates; if so, it may be necessary to use quote.

Italics within quotations
 * Use italics within quotations if they are already in the source material. When adding italics on TechInfoDepot, add an editorial note [emphasis added] after the quotation.
 * "Now cracks a noble heart. Good night sweet prince: And flights of angels sing thee to thy rest" [emphasis added].


 * If the source has used italics (or some other styling) for emphasis and this is not otherwise evident, the editorial note [emphasis in original] should appear after the quotation.

Effect on nearby punctuation
 * Italicize only the elements of the sentence affected by the emphasis. Do not italicize surrounding punctuation.
 * {|style="background:transparent"


 * Incorrect:
 * colspan=2|What are we to make of that?
 * style="vertical-align:top" rowspan=2|Correct:
 * colspan=2|What are we to make of that?
 * (Note the difference between ? and ?. The question mark applies to the whole sentence, not just to the emphasized that.)
 * style="vertical-align:top" rowspan=2|Correct:
 * colspan=2|Four of Patrick White's most famous novels are A Fringe of Leaves, The Aunt's Story, Voss, and The Tree of Man.
 * (The commas, the period, and the word and are not italicized.)
 * }
 * style="vertical-align:top" rowspan=2|Correct:
 * colspan=2|Four of Patrick White's most famous novels are A Fringe of Leaves, The Aunt's Story, Voss, and The Tree of Man.
 * (The commas, the period, and the word and are not italicized.)
 * }
 * (The commas, the period, and the word and are not italicized.)
 * }
 * }

Italicized links
 * The italics markup must be outside the link markup, or the link will not work; however, internal italicization can be used in piped links.
 * {|style="background:transparent"


 * Incorrect:  ||
 * Correct:              ||
 * Correct:              ||
 * }
 * Correct:              ||
 * }
 * }

Non-breaking spaces
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.

Technical information

 * A hard space can be produced with the template space or the HTML code  instead of the space bar:   yields a non-breaking 19 kg.
 * A literal hard space, such as one of the Unicode non-breaking space characters, should not be used, since some web browsers will not load them properly during editing.
 * Non-breaking text can also be achieved by use of the nowrap template: produces a non-breaking 8 sq ft. This is especially useful for short constructions requiring two or more hard spaces, as in the preceding example. This template has the disadvantage that if the enclosed text starts or ends with a space, these spaces are forced outside in the resulting HTML, and unpredicted breaks may occur. If   occurs right before, or at the start of text within , some browsers allow a break at that point.
 * In some older browsers, quotation marks separated by a hard space are broken at the end of a line:  ("She said 'Yes!' "). Use   ("She said 'Yes!) instead.
 * It is possible to use non-breaking spaces within wikilinks like World War II (encoded as ).
 * Unlike normal spaces, multiple hard spaces are not compressed by browsers into a single space.

Use
It is advisable to use a non-breaking space to prevent the end-of-line displacement of elements that would be awkward at the beginning of a new line:
 * in expressions in which figures and their related units, abbreviations, or symbols are separated by a space (e.g. 17 kg, AD 565, 2:50 pm);
 * in other places where breaking across lines might be disruptive to the reader, especially in infoboxes, such as £11 billion, August 2024, 5° 24′ 21.12″ N, Boeing 747, after the number in a numbered address (e.g. 123 Fake Street) and before Roman numerals at the end of phrases (e.g. World War II and Pope Benedict XVI); and
 * before a spaced en dash.

Original wording
The wording of the quoted text should be faithfully reproduced. Where there is good reason to change the wording, enclose it within square brackets (for example, [her father] replacing him, where the context identifying "him" is not included in the quotation: "Ocyrhoe told [her father] his fate"). If there is a significant error in the original statement, use [sic] or the template sic to show that the error was not made by TechInfoDepot. However, trivial spelling and typographic errors should simply be corrected without comment (for example, correct basicly to basically and harasssment to harassment), unless the slip is textually important.

Use ellipses to indicate omissions from quoted text. Legitimate omissions include extraneous, irrelevant, or parenthetical words, and unintelligible speech (umm, and hmm). Do not omit text where doing so would remove important context or alter the meaning of the text. When a vulgarity or obscenity is quoted, it should appear exactly as it does in the cited source; words should never be bowdlerized by replacing letters with dashes, asterisks, or other symbols. In carrying over such an alteration from a quoted source, [sic] may be used to indicate that the transcription is exact.

Typographic conformity
A quotation is not a facsimile, and in most cases it is not desirable to duplicate the original formatting. Formatting and other purely typographical elements of quoted text should be adapted to English TechInfoDepot's conventions without comment; this practice is universal among publishers. These are alterations which make no difference when the text is read aloud, such as:
 * Changing capitalization so that sentences begin with capital letters and do not have unnecessary capitals in the middle (the oft-repeated maxim "a penny saved is a penny earned").
 * Styling of dashes and hyphens: see Dashes, below. Use the style chosen for the article: unspaced em dash or spaced en dash.
 * Styling of apostrophes and quotation marks
 * These should all be straight, not curly or slanted. See Quotation marks, below.
 * When quoting a quotation that itself contains a quotation, single quotes may be replaced with double quotes, and vice versa. See Quotations within quotations below.
 * Replacing non-English typographical elements with their English equivalents. For example, replace guillemets (« ») with straight quotation marks.
 * Removing spaces before punctuation such as periods and colons
 * Generally preserve bold and italics (see Italics, above), but most other styling should be altered. Underlining and spacing  (as found in typewritten documents) should be changed to italics, and other unusual forms of emphasis (colored highlighting, all caps or small caps, etc.) should likewise generally be normalized to italics or boldface. It is also permissible to add appropriate non-emphatic italics or quotation marks, for example to mark the title of a book or poem within a quotation.
 * Expanding abbreviations
 * Normalizing archaic glyphs and ligatures, when doing so will not change or obscure the meaning or intent of the text. Examples include æ→ae, œ→oe, ſ→s, and ye→the. See also ampersand, above.

However, national varieties should not be changed, as these may involve changes in vocabulary, and because articles are prone to flipping back and forth. For example, a quotation from a British source should retain British spelling in an article that otherwise uses American spelling. (See CONSISTENCY above.)

Quotations within quotations
When a quotation includes another quotation (and so on), start with double quote marks outermost, and, working inward, alternate single with double quote marks ("She accepted his statement that 'Voltaire never said "I disapprove of what you say, but I will defend to the death your right to say it., with three levels of quotation). Adjacent quote marks, as at the end of that last example, can be difficult to read ("'") unless kerned apart slightly with CSS; the " ', ' ", and " ' " templates will accomplish this; the example above is achieved by typing this:.

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 with quotations that are clearly from the person discussed in the article or section. When preceding a quotation with its attribution, avoid characterizing it in a biased manner.

Linking
As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.

Block quotations
Format a long quote (more than about 40 words or a few hundred characters, or consisting of more than one paragraph, regardless of length) as a block quotation, which Wikimedia's software will indent from both margins. Do not enclose block quotations in quotation marks (and especially avoid decorative quotation marks in normal use, such as those provided by the centered pull quote template, which are reserved for pull quotes). Block quotations using a colored background are also discouraged. Block quotations can be enclosed between a pair of  HTML tags; or use quote or quote box.

Poetry, lyrics, and other formatted text may be quoted inline if they are short, or presented in a block quotation. If inline, line breaks should be indicated by /, and paragraph or stanza breaks by //. TechInfoDepot's MediaWiki software does not normally render line breaks inside a, but the poem extension can be used to preserve them:

This will result in the following, indented on both sides (it may also be in a smaller font, depending on browser software): Once upon a midnight dreary, while I pondered, weak and weary, Over many a quaint and curious volume of forgotten lore— While I nodded, nearly napping, suddenly there came a tapping, As of some one gently rapping, rapping at my chamber door. "'Tis some visiter," I muttered, "tapping at my chamber door—          Only this and nothing more."

The quote template retains line breaks but not leading spaces (use hard spaces,, instead), and adds a parameter for the attribution.

Foreign-language quotations
Quotations from foreign-language sources should appear in translation. Quotations that are translations should be explicitly distinguished from those that are not. Indicate the original source of a translation (if it is available, and not first published within TechInfoDepot), and the original language (if that is not clear from the context).

If the original, untranslated text is available, provide a reference for it or include it, as appropriate.

Apostrophes

 * Consistent use of the straight (or typewriter) apostrophe (') is recommended, as opposed to the curly (or typographic) apostrophe (’). For details and reasons, see Quotation marks, below.
 * To prevent apostrophes from being misinterpreted as Wiki markup, use the templates, , and , or use  tags.
 * Foreign characters that resemble apostrophes, such as transliterated Arabic ayin (ʿ) and alif (ʾ), are represented by their correct Unicode characters (that is, U+02BF MODIFIER LETTER LEFT HALF RING and U+02BE MODIFIER LETTER RIGHT HALF RING respectively), despite possible display problems. If this is not feasible, use a straight apostrophe instead.
 * For usage of the possessive apostrophe, see the summary of usage issues at Possessives, below.
 * For a thorough treatment of all uses of the apostrophe (possessive, elision, formation of certain plurals, specific foreign-language issues) see the article Apostrophe.

Quotation marks
The term quotation in the material below also includes other uses of quotation marks such as those for titles of songs, chapters, episodes, unattributable aphorisms, literal strings, "scare-quoted" passages, and constructed examples.

Double or single
 * Enclose quotations with double quotation marks (Bob said, "Jim ate the apple."). Enclose quotations inside quotations with single quotation marks (Bob said, "Did Jim say 'I ate the apple' after he left?"). This is by far the dominant convention in current practice; see other reasons, below.
 * There are some conventional codified exceptions, such as single quotation marks for plant cultivars (Malus domestica 'Golden Delicious'); see WP:FLORA.

Article openings
 * When the bolded title in the lead paragraph of an article includes quotation marks (for example around a nickname, or the name of a song or poem), the quotation marks themselves should not be in boldface:
 * {|style="background:transparent"


 * Correct: || William Jefferson "Bill" Clinton is an American politician.
 * }
 * {|style="background:transparent"


 * Correct: || "Jabberwocky" is a nonsense poem by Lewis Carroll.
 * }

Block quotes
 * As already noted above, we use quotation marks or block quotes (not both) to distinguish long quotations from other text. Multiparagraph quotations are always block-quoted. The quotations must be precise and exactly as in the source (except for certain allowable typographical changes, also noted above). The source should be cited clearly and precisely to enable readers to locate the text in question, and to quote it accurately themselves from TechInfoDepot.

Quotation characters
 * Do not use grave and acute accents or backticks (`text´) as quotation marks (or as apostrophes).
 * There are two possible methods for rendering quotation marks at TechInfoDepot (that is, the glyphs, displayed with emphasis here, for clarity):
 * Typewriter or straight style: "text", 'text'. Recommended at TechInfoDepot.
 * Typographic or curly style: “text”, ‘text’. Not recommended at TechInfoDepot.
 * Whenever quotation marks or apostrophes appear in article titles, make a redirect from the same title but using the alternative glyphs.

Reasons to prefer straight quotation marks and apostrophes (and double quotation marks)

Typographical, or curly, quotation marks and apostrophes might be read more efficiently; and many think they look more professional. But for practical reasons the straight versions are recommended, and double rather than single quotation marks as primary.
 * Consistency keeps searches predictable. Search facilities have differences that many readers (and editors) are unaware of:
 * TechInfoDepot's search facility treats differently styled quotation marks in unintuitive ways; and the suggestions that appear as users insert text ignore straight double quotation marks, but treat other quotation marks as significant. They distinguish straight and curly forms (neither ‘occupy’ protests nor “occupy” protests would find the title "Occupy" protests directly).
 * In its search form Google uses double quotation marks to keep a sequence of words intact (these two searches yield quite different results: ;  ). Google searches are insensitive to other punctuation marks; they are simply ignored.
 * Browser searches (of displayed text, perhaps a TechInfoDepot page) distinguish between single and double quotation marks, and also between curly and straight forms. (Searches for Alzheimer's disease could fail to find Alzheimer’s disease and vice versa; similarly for "must see" attractions, 'must see' attractions, “must see” attractions, and ‘must see’ attractions.)
 * Double quotation marks are more difficult to mistake for apostrophes than single quotes are:
 * She wrote that 'Cleanthes' differs from the others', but neither opinion may represent Hume's'; ... (slows the reader down)
 * She wrote that "Cleanthes' differs from the others', but neither opinion may represent Hume's"; ... (clearer)


 * Straight quotation marks are easier to type in reliably, and to edit. They are available on every keyboard.

Names and titles
Quotation marks should be used for the following names and titles: For example: The song "Example" from the album Example by the band Example...
 * Articles and chapters (books and periodicals italicized)
 * Sections of musical pieces (pieces italicized)
 * Individual strips from comics and webcomics (comics italicized)
 * Computer and video games (but not other software)
 * Television episodes (series italicized)
 * Poems (long or epic poems italicized)
 * Songs (albums, song cycles, operas, operettas, oratorios italicized)
 * Individual episodes of television and radio series and serials (series title italicized)

Do not use quotation marks or italics for:
 * Ancient writings
 * Concert tours
 * Locations
 * Myths and epics
 * Prayers

Punctuation inside or outside
On TechInfoDepot, place all punctuation marks inside the quotation marks if they are part of the quoted material and outside if they are not. This practice is sometimes referred to as logical quotation. It is used here because it is deemed by TechInfoDepot consensus to be more in keeping with the principle of minimal change. This punctuation system does not require placing final periods and commas outside the quotation marks all the time, but rather maintaining their original positions in (or absence from) the quoted material.


 * {|style="background:transparent"


 * style="vertical-align:top" rowspan=2|Correct: || Arthur said, "The situation is deplorable and unacceptable."
 * (The period is known to be in the source.)
 * (The period is known to be in the source.)
 * (The period is known to be in the source.)


 * style="vertical-align:top" rowspan=2|Correct: || Arthur said that the situation was "deplorable".
 * (The period is known not to be in the source, its presence in the source is uncertain, or its coverage within the quotation is considered unnecessary.)
 * (The period is known not to be in the source, its presence in the source is uncertain, or its coverage within the quotation is considered unnecessary.)
 * (The period is known not to be in the source, its presence in the source is uncertain, or its coverage within the quotation is considered unnecessary.)
 * (The period is known not to be in the source, its presence in the source is uncertain, or its coverage within the quotation is considered unnecessary.)


 * style="vertical-align:top" rowspan=2|Correct: || Martha asked, "Are you coming?"
 * (The question mark belongs inside because the quoted text itself was a question.)
 * (The question mark belongs inside because the quoted text itself was a question.)
 * (The question mark belongs inside because the quoted text itself was a question.)
 * (The question mark belongs inside because the quoted text itself was a question.)


 * style="vertical-align:top" rowspan=2|Correct: || Did Martha say, "Come with me"?
 * (The very quote is being questioned, so the question mark belongs outside; any punctuation at the end of the original quote is omitted.)
 * (The very quote is being questioned, so the question mark belongs outside; any punctuation at the end of the original quote is omitted.)
 * (The very quote is being questioned, so the question mark belongs outside; any punctuation at the end of the original quote is omitted.)
 * (The very quote is being questioned, so the question mark belongs outside; any punctuation at the end of the original quote is omitted.)


 * }
 * When a quoted sentence fragment 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: || Martha said, "Come with me", and they did.
 * }
 * If the sequence of juxtaposed punctuation marks seems distracting or untidy, try an acceptable alternative.
 * {|style="background:transparent"


 * Correct: || Martha said, "Come with me" (and they did).
 * }

Brackets and parentheses
These rules apply to both round brackets, often called parentheses, and square brackets [ ].

If a sentence contains a bracketed phrase, place the sentence punctuation outside the brackets (as shown here). However, where one or more sentences are wholly inside brackets, place their punctuation inside the brackets. (For examples, see Sentences and brackets, below.) There should be no space next to the inner side of a bracket. An opening bracket should be preceded by a space, except in unusual cases; for example, when it is preceded by an opening quotation mark, another opening bracket, or a portion of a word:
 * He rose to address the meeting: "(Ahem) ... Ladies and gentlemen, welcome!"
 * Only the royal characters in the play ([Prince] Hamlet and his family) habitually speak in blank verse.
 * We journeyed on the Inter[continental].

There should be a space after a closing bracket, except where a punctuation mark follows (though a spaced dash would still be spaced after a closing bracket), 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; 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:
 * {|style="background:transparent"

Square brackets are used to indicate editorial replacements and insertions within quotations, though this should never alter the intended meaning. They serve three main purposes:
 * Incorrect:  ||Nikifor Grigoriev (c. 1885–1919) (also known as Matviy Hryhoriyiv) was a Ukrainian insurgent leader.
 * Correct:              ||Nikifor Grigoriev (c. 1885–1919), also known as Matviy Hryhoriyiv, was a Ukrainian insurgent leader.
 * Correct:              ||Nikifor Grigoriev (c. 1885–1919) was a Ukrainian insurgent leader. He was also known as Matviy Hryhoriyiv.
 * }
 * Correct:              ||Nikifor Grigoriev (c. 1885–1919) was a Ukrainian insurgent leader. He was also known as Matviy Hryhoriyiv.
 * }
 * }
 * To clarify. (She attended [secondary] school, where this was the intended meaning, but the type of school was unstated in the original sentence.)
 * To reduce the size of a quotation. (X contains Y, and under certain circumstances, X may contain Z as well may be reduced to X contains Y [and sometimes Z].) When an ellipsis (...) is used to indicate that material is removed from a direct quotation, it should not normally be bracketed (see Ellipses, below).
 * To make the grammar work. (Referring to someone's statement "I hate to do laundry", one could properly write: She "hate[s] to do laundry".)

Sentences and brackets

 * If any sentence includes material that is enclosed in square or round brackets, it still must end—with a period, or a question or exclamation mark—after those brackets. This principle applies no matter what punctuation is used within the brackets:
 * She refused all requests (except for basics such as food, medicine, etc.).


 * However, if the entire sentence is within brackets, the closing punctuation falls within the brackets. (This sentence is an example.) 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:
 * "[Principal Skinner] already told me that", he objected.
 * That is preferable to this, which is potentially ambiguous:
 * "He already told me that", he objected.
 * But even here consider an addition rather than a replacement of text:
 * "He [Principal Skinner] 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. See the indented example above, and also:
 * Alexander then conquered (who would have believed it?) most of the known world.
 * Clare demanded that he drive (she knew he hated driving) to the supermarket.
 * It is often clearer to separate the thoughts into separate sentences or clauses:
 * Alexander then conquered most of the known world. Who would have believed it?
 * Clare demanded that he drive to the supermarket; she knew he hated driving.

Brackets and linking
If the text of a link needs to contain one or more square brackets, "escape" these using  tags or the appropriate numerical character reference. If a URL itself contains square brackets, the wiki-text should use the url-encoded form: rather than ...  ... to avoid truncation of the link text after "xxx". Of course, this issue only arises for external links as MediaWiki software forbids square brackets in page titles.

Ellipses
An ellipsis (plural ellipses) is an omission of material from quoted text; or some other omission, perhaps of the end of a sentence, 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 (...). This is the easiest way, and gives a predictable appearance in HTML. Recommended.
 * Pre-composed ellipsis character (…); generated with the  character entity, or as a literal "…". This is harder to input and edit, and too small in some fonts. Not recommended.
 * Three spaced periods (. ..). This is an older style (spaces between the periods) 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 above, and points below).
 * Put a space on each side of an ellipsis ("France, Germany, ... and Belgium"), except that there should be no space between an ellipsis and:
 * a quotation mark directly following the ellipsis ("France, Germany, and Belgium ...").
 * any (round, square, curly, etc.) bracket, where the ellipsis is on the inside ("France, Germany (but not Berlin, Munich, ...), and Belgium").
 * sentence-final punctuation, or a colon, semicolon, or comma (all rare), directly following the ellipsis ("Are we going to France ...?").
 * Only place terminal punctuation after an ellipsis if it is textually important (as is often the case with exclamation marks and question marks, and rarely with periods).
 * Use non-breaking spaces as needed to prevent improper line breaks, for example:
 * To keep a quotation mark (and any adjacent punctuation) from being separated from the start or end of the quotation ("... we are still worried"; "Are we going to France ...?").
 * To keep the ellipsis from wrapping to the next line ("France, Germany, ... and Belgium"; "France, Germany, ... and Belgium").

Pause or suspension of speech
 * Three periods (loosely also called ellipsis points) are occasionally used to represent a pause in or suspense of speech, in which case the punctuation is retained in its original form (Virginia's startled reply was: "Could he ...? No, I cannot believe it!"). Avoid this usage on TechInfoDepot, except in direct quotations.

With square brackets
 * An ellipsis does not normally need square brackets around it, because its function is usually obvious—especially if the guidelines above are followed. Square brackets, however, may optionally be used for precision, to make it clear 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 (Her long rant continued: "How do I feel? How do you think I ... look, this has gone far enough! [...] I want to go home!").

Commas
Commas are the most frequently used marks in punctuation and can be the most difficult to use well. Some important points are made in the Semicolons section below. Other points:
 * Pairs of commas are often used to delimit parenthetic material, forming a parenthetical remark. This interrupts the sentence less than a parenthetical remark in (round) brackets or dashes. Do not be fooled by other punctuation, which can mask the need for a comma, especially when it collides with a bracket or parenthesis, as in this example:
 * {|style="background:transparent"


 * Incorrect:          ||Burke and Wills, fed by local Aborigines (on beans, fish, and "ngardu") survived for a few months.
 * Correct:  ||Burke and Wills, fed by local Aborigines (on beans, fish, and "ngardu"), survived for a few months.
 * }
 * On TechInfoDepot, place quotation marks in accordance with the UK-based logical punctuation system:
 * {|style="background:transparent"
 * On TechInfoDepot, place quotation marks in accordance with the UK-based logical punctuation system:
 * {|style="background:transparent"


 * Incorrect:          ||She said, "punctuation styles on TechInfoDepot change too often," and made other complaints.
 * Correct:  ||She said, "punctuation styles on TechInfoDepot change too often", and made other complaints.
 * }
 * Modern practice is against excessive use of commas; there are usually ways to simplify a sentence so that fewer are needed.
 * {|style="background:transparent"
 * Modern practice is against excessive use of commas; there are usually ways to simplify a sentence so that fewer are needed.
 * {|style="background:transparent"


 * Awkward:                ||Mozart was, along with the Haydns, both Joseph and Michael, and also Beethoven, one of Schubert's heroes.
 * Much better:  ||Schubert's heroes included Mozart, Beethoven, and Joseph and Michael Haydn.
 * }
 * Before a quotation embedded within a sentence, the use of a comma is optional. Eve said "He ate the apple." or Eve said, "He ate the apple." Many editors prefer a colon in this position if the quotation forms one or more complete sentences: Eve said: "He ate the apple."
 * }
 * Before a quotation embedded within a sentence, the use of a comma is optional. Eve said "He ate the apple." or Eve said, "He ate the apple." Many editors prefer a colon in this position if the quotation forms one or more complete sentences: Eve said: "He ate the apple."

Serial commas
A serial comma (also known as an Oxford comma or a Harvard comma) is a comma used immediately before a conjunction (and or or, sometimes nor) in a list of three or more items: the phrase ham, chips, and eggs includes a serial comma, while the variant ham, chips and eggs omits it. Editors may use either convention on TechInfoDepot so long as each article is consistent within itself. However, there are some times when the serial comma can create or remove confusion:

Sometimes omitting the comma can lead to an ambiguous sentence, as in this example: The author thanked her parents, Sinéad O'Connor and President Obama, which may list either four people (the two parents and the two people named) or two people (O'Connor and Obama, who are the parents).

Including the comma can also cause ambiguity, as in this example: The author thanked her mother, Sinéad O'Connor, and President Obama, which may list either two people (O'Connor, who is the mother, and Obama) or three people (the first being the mother, the second O'Connor, and the third Obama).

In such cases of ambiguity, there are three ways to clarify:
 * Use or omit the serial comma to avoid ambiguity.
 * Recast the sentence.
 * List the elements by using a format, such as one with paragraph breaks and numbered paragraphs.

Recasting example one:
 * To list four people: The author thanked President Obama, Sinéad O'Connor, and her parents.
 * To list two people (the commas here set off non-restrictive appositives): The author thanked her father, President Obama, and her mother, Sinéad O'Connor.
 * Clearer (but more wordy): The author thanked her father and her mother, who are President Obama and Sinéad O'Connor respectively.

Recasting example two:
 * To list two people: The author thanked President Obama and her mother, Sinéad O'Connor.
 * To list three people: The author thanked her mother, President Obama, and Sinéad O'Connor.
 * The clarity of the last example depends on the reader's knowing that Obama is male and cannot be a mother. If we change the example slightly, we are back to an ambiguous statement: The author thanked her mother, Irish President Mary McAleese, and Sinéad O'Connor.
 * Clearer: The author thanked President Obama, Sinéad O'Connor, and her mother; or The author thanked President Mary McAleese, Sinéad O'Connor, and her mother.

Colons
A colon informs the reader that what comes after it demonstrates, explains, or modifies what has come before, or is a list of items that has just been introduced. The items in such a list may be separated by commas; or, if they are more complex and perhaps themselves contain commas, the items should be separated by semicolons:


 * We visited several tourist attractions: the Leaning Tower of Pisa, which I thought could fall at any moment; the Bridge of Sighs; the supposed birthplace of Petrarch, or at least the first known house in which he lived; and so many more.

A colon may also be used to introduce direct speech enclosed within quotation marks (see above).

In most cases a colon works best with a complete grammatical sentence before it. There are exceptional cases, such as those where the colon introduces items set off in new lines like the very next colon here. Examples:
 * {|style="background:transparent"


 * Correct:              ||He attempted it in two years: 1941 and 1943.
 * Incorrect:  ||The years he attempted it included: 1941 and 1943.
 * Correct (special case):  ||Spanish, Portuguese, French: these, with a few others, are the West Romance languages.
 * }
 * Correct (special case):  ||Spanish, Portuguese, French: these, with a few others, are the West Romance languages.
 * }
 * }

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:


 * 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. There should never be a hyphen or a dash immediately following a colon. Only a single space follows a colon.

Semicolons
A semicolon 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 the semicolon separates clauses, normally each clause must be independent (meaning that it could stand on its own as a sentence); often, only a comma or only a semicolon will be correct in a given sentence.


 * {|style="background:transparent"


 * Correct:              ||Though he had been here before, I did not recognize him.
 * Incorrect:  ||Though he had been here before; I did not recognize him.
 * }
 * Incorrect:  ||Though he had been here before; I did not recognize him.
 * }

Above, "Though he had been here before" cannot stand on its own as a sentence, and therefore is not an independent clause.


 * {|style="background:transparent"


 * Correct:              ||Oranges are an acid fruit; bananas are classified as alkaline.
 * Incorrect:  ||Oranges are an acid fruit, bananas are classified as alkaline.
 * }
 * Incorrect:  ||Oranges are an acid fruit, bananas are classified as alkaline.
 * }

This incorrect use of a comma between two independent clauses is known as a comma splice; however, in very rare cases, a comma may be used where a semicolon would seem to be called for:


 * {|style="background:transparent"


 * Accepted:              ||"Life is short, art is long." (citing a brief aphorism; see Ars longa, vita brevis)
 * Accepted:              ||"I have studied it, you have not." (reporting brisk conversation, like this reply of Newton's)
 * }
 * Accepted:              ||"I have studied it, you have not." (reporting brisk conversation, like this reply of Newton's)
 * }

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

A sentence may 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"


 * Unwieldy:              ||Oranges are an acid fruit; bananas are classified as alkaline; pears are close to neutral; these distinctions are rarely discussed.
 * One better way:  ||Oranges are an acid fruit, bananas are alkaline, and pears are close to neutral; these distinctions are rarely discussed.
 * }
 * One better way:  ||Oranges are an acid fruit, bananas are alkaline, and pears are close to neutral; these distinctions are rarely discussed.
 * }

Semicolon before "however"
The meaning of a sentence containing a trailing clause that starts with the word "however" depends on the punctuation preceding that word. A common error is to use the wrong punctuation, thereby changing the meaning to one not intended.

When the word "however" is an adverb meaning "nevertheless", it should be preceded by a semicolon and followed by a comma. Example:


 * {|style="background:transparent"


 * ||It was obvious they could not convert these people; however, they tried.
 * Meaning:               ||It was obvious they could not convert these people. Nevertheless, they tried.
 * }
 * Meaning:               ||It was obvious they could not convert these people. Nevertheless, they tried.
 * }

When the word "however" is a conjunction meaning "in whatever manner", or "regardless of how", it may be preceded by a comma but not by a semicolon, and should not be followed by punctuation. Example:


 * {|style="background:transparent"


 * ||It was obvious they could not convert these people, however they tried.
 * Meaning:               ||It was obvious they could not convert these people, regardless of how they tried.
 * }
 * Meaning:               ||It was obvious they could not convert these people, regardless of how they tried.
 * }

In the first case, the clause that starts with "however" cannot be swapped with the first clause; in the second case this can be done without change of meaning:


 * {|style="background:transparent"


 * ||However they tried, it was obvious they could not convert these people.
 * Meaning:               ||Regardless of how hard they tried, it was obvious they could not convert these people.
 * }
 * Meaning:               ||Regardless of how hard they tried, it was obvious they could not convert these people.
 * }

If the two clauses cannot be swapped, a semicolon is required.

A sentence or clause can also contain the word "however" in the middle if it is an adverb meaning "though", which could have been placed at the beginning but does not start a new clause in mid-sentence. In this use the word may be enclosed between commas. Example:


 * {|style="background:transparent"


 * ||He did not know, however, that the venue had been changed at the last minute.
 * Meaning:               ||However, he did not know that the venue had been changed at the last minute.
 * }
 * Meaning:               ||However, he did not know that the venue had been changed at the last minute.
 * }

Hyphens
Hyphens (-) indicate conjunction. There are three main uses.
 * 1) In hyphenated personal names: John Lennard-Jones.
 * 2) To link certain prefixes with their main word (non-linear, sub-section, super-achiever).
 * 3) * A hyphen may be used to distinguish between homographs (re-dress means dress again, but redress means remedy or set right).
 * 4) * There is a clear trend to join both elements in all varieties of English (subsection, nonlinear), particularly in American English. British English tends to hyphenate when the letters brought into contact are the same (non-negotiable, sub-basement) or are vowels (pre-industrial), or where a word is uncommon (co-proposed, re-target) or may be misread (sub-era, not subera). American English reflects the same factors, but is more likely to close up without a hyphen. Consult a good dictionary, and see National varieties of English above.
 * 5) To link related terms in compound modifiers:
 * 6) * Hyphens can help with ease of reading (face-to-face discussion, hard-boiled egg); where non-experts are part of the readership, a hyphen is particularly useful in long noun phrases, such as those in TechInfoDepot's scientific articles: gas-phase reaction dynamics. However, hyphens are never inserted into proper-name-based compounds (Middle Eastern cuisine, not Middle-Eastern cuisine).
 * 7) * A hyphen can help to disambiguate (little-celebrated paintings is not a reference to little paintings; a government-monitoring program is a program that monitors the government, whereas a government monitoring program is a government program that monitors something else).
 * 8) * Many compounds that are hyphenated when used attributively (before the noun they qualify: a light-blue handbag), are not hyphenated when used predicatively (separated from the noun: the handbag was light blue). Where there would otherwise be a loss of clarity, the hyphen may be used in the predicative case as well (hand-fed turkeys, the turkeys were hand-fed).
 * 9) * A hyphen is not used after a standard -ly adverb (a newly available home, a wholly owned subsidiary) unless part of a larger compound (a slowly-but-surely strategy). A few words ending in -ly function as both adjectives and adverbs (a kindly-looking teacher; a kindly provided facility). Some such dual-purpose words (like early, only, northerly) are not standard -ly adverbs, since they are not formed by addition of -ly to an independent current-English adjective. These need careful treatment: Early flowering plants appeared around 130 million years ago, but Early-flowering plants risk damage from winter frosts; northerly-situated islands.
 * 10) * A hyphen is normally used when the adverb well precedes a participle used attributively (a well-meaning gesture; but normally a very well managed firm, since well itself is modified); and even predicatively, if well is necessary to, or alters, the sense of the adjective rather than simply intensifying it (the gesture was well-meaning, the child was well-behaved, but the floor was well polished).
 * 11) * In some cases, like diode–transistor logic, the independent status of the linked elements requires an en dash instead of a hyphen. See En dashes below.
 * 12) * A hanging hyphen is used when two compound modifiers are separated (two- and three-digit numbers, a ten-car or -truck convoy, sloping right- or leftward, but better is sloping rightward or leftward).
 * 13) * Values and units used as compound modifiers are hyphenated only where the unit is given as a whole word; when the unit symbol is used, it is separated from the number by a non-breaking space.
 * {|style="background:transparent"


 * Incorrect:            ||9-mm gap
 * Correct:              ||9 mm gap (entered as  )
 * Incorrect:  ||9 millimetre gap
 * Correct:              ||9-millimetre gap
 * Correct:              ||12-hour shift
 * Correct:              ||12 h shift
 * }
 * Correct:              ||9-millimetre gap
 * Correct:              ||12-hour shift
 * Correct:              ||12 h shift
 * }
 * Correct:              ||12 h shift
 * }

Multi-hyphenated items: It is often possible to avoid multi-word hyphenated modifiers by rewording (a four-CD soundtrack album may be easier to read as a soundtrack album of four CDs). This is particularly important where converted units are involved (the 6-hectare-limit (14.8-acre-limit) rule might be possible as the rule imposing a limit of 6 hectares (14.8 acres), and the ungainly 4.9-mile (7.9 km) -long tributary as simply 4.9-mile (7.9 km) tributary).

For optional hyphenation of compound points of the compass such as southwest/south-west, see Compass points above.

Hyphenation rules in other languages may be different. Thus in French a place name such as Trois-Rivières ("three rivers") is hyphenated when it would not be in English. Follow reliable sources in such cases.

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 sub- and the suffix -less.

Image filenames and redirects: Image filenames are not part of encyclopedic content; they're tools. They are most useful tools if they can be readily typed, so they always use hyphens instead of dashes. Similarly, article titles with dashes should have a corresponding redirect from the title with hyphens: for example, Michelson-Morley experiment redirects to Michelson–Morley experiment, as the latter title, while correct, is harder to search for.

Non-breaking: A non-breaking hyphen can be created by using the HTML code.

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

Dashes
Two forms of dash are used on TechInfoDepot: en dash (–) and em dash (—). Type them in as  (–) and   (—) or click on them to the right of the "Insert" tab under the edit window; or see How to make dashes.
 * When naming an article, do not use a hyphen as a substitute for an en dash that properly belongs in the title, for example in Eye–hand span. To aid searching and linking, provide a redirect from the corresponding article title with hyphens in place of en dashes, as in Eye-hand span. Make a similar redirect for categories that contain a dash, so that WP:HotCat recognizes them.

Sources use dashes in varying ways, but for consistency and clarity TechInfoDepot adopts the following principles.

Punctuating a sentence (em or en dashes)
Dashes are often used to mark divisions within a sentence: in pairs (parenthetical dashes, instead of parentheses or pairs of commas); or singly (perhaps instead of a colon). They may also indicate an abrupt stop or interruption, in reporting direct speech.

There are two options. Use one or the other consistently in an article.

1. Unspaced em dash
 * Another "planet" was detected—but it was later found to be a moon of Saturn.

or

2. Spaced en dash
 * Another "planet" was detected – but it was later found to be a moon of Saturn.

To ensure correct linewrap handling, the spaced ndash can be used:

However, do not use the template where the en dash is unspaced.

Do not use spaced em dashes.

Dashes can clarify the sentence structure when there are already commas or parentheses, or both.
 * We read them in chronological order: Descartes, Locke, Hume—but not his Treatise (it is too complex)—and Kant.

Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair.
 * The birds—at least the ones Darwin collected—had red and blue feathers.
 * "Where is the—", she began, but then realized she held it in her hand.
 * Avoid: First in the procession—and most spectacularly—came the bishops—then the other clergy.

En dashes: other uses
The en dash (–) has other roles, beyond its use as a sentence-punctuating dash (see immediately above). It is often analogous to the hyphen (see the section above), which joins components more strongly than the en dash; or the slash (see the section below), which separates alternatives more definitely. Consider the exact meaning when choosing which to use.

1. In ranges that might otherwise be expressed with to or through Do not mix en dashes with prepositions like between and from. If negative values are involved, an en dash might be confusing. Use words instead. The en dash in a range is always unspaced, except when the endpoints of the range already include at least one space.
 * pp. 211–19;  64–75%;   the 1939–45 war
 * 450–500 people
 * between 450 and 500 people, not between 450–500 people
 * from 450 to 500 people, not from 450–500 people
 * −10 to 10, not −10–10
 * 23 July 1790 – 1 December 1791, not 23 July 1790–1 December 1791
 * 14 May – 2 August 2011, not 14 May–2 August 2011
 * 10:30 pm Tuesday – 1:25 am Wednesday;  Christmas Day – New Year's Eve;   Christmas 2001 – Easter 2002
 * 1–17 September;  February–October 2009;   1492? – 7 April 1556
 * Best absorbed were wavelengths in the range 28 mm – 17 m.

'2. In compounds when the connection might otherwise be expressed with to, versus, and, or between'' Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving separate or independent elements. The components may be nouns, adjectives, verbs, or any other independent part of speech. Often if the components are reversed there would be little change of meaning.'''
 * boyfriend–girlfriend problems;  the Paris–Montpellier route;   a New York–Los Angeles flight
 * iron–cobalt interactions; the components are parallel and reversible; iron and cobalt retain their identity
 * Wrong: an iron–roof shed; iron modifies roof, so use a hyphen: an iron-roof shed
 * Wrong: a singer–songwriter; not separate persons, so use a hyphen: a singer-songwriter
 * red–green colorblind; red and green are separate independent colors, not mixed
 * Wrong: blue–green algae; a blended, intermediate color, so use a hyphen: blue-green algae

A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see Slashes below). An en dash is not used for a hyphenated personal name. An en dash is used for the names of two or more people in an attributive compound. A hyphen is used by default in compounded proper names of single entities.
 * Wrong: Franco–British rivalry; "Franco" is a combining form, not independent; use a hyphen: Franco-British rivalry
 * France–Britain rivalry;  French–British rivalry
 * a 51–30 win;  a six–two majority decision
 * an Italian–Swiss border crossing; but an Italian-Swiss newspaper for Italian-speaking Swiss
 * Japanese–American trade; but a family of Japanese-American traders (or a family of Japanese Americans)
 * the Uganda–Tanzania War;  the Roman–Syrian War;   the east–west runway;   the Lincoln–Douglas debates;   a carbon–carbon bond
 * diode–transistor logic;  the analog–digital distinction;   push–pull output;   on–off switch
 * a pro-establishment–anti-intellectual alliance;  Singapore–Sumatra–Java shipping lanes
 * the ballerina's rapid walk–dance transitions;  a male–female height ratio of 1.14
 * the protein–fat ratio, or  the protein/fat ratio,  or  the protein-to-fat ratio
 * Lennard-Jones potential with a hyphen: named after John Lennard-Jones
 * the Seifert–van Kampen theorem;  the Seeliger–Donker-Voet scheme;   the Alpher–Bethe–Gamow theory
 * Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp)
 * Guinea-Bissau; Bissau is the capital, and this distinguishes the country from neighboring Guinea
 * Wilkes-Barre, a single city named after two people, but Minneapolis–Saint Paul, a union of two cities
 * John Lennard-Jones, an individual named after two families
 * McGraw-Hill, a publishing house named after two founders

The en dash in all of the compounds above is unspaced.

3. Instead of a hyphen, when applying a prefix (but not a suffix) to a compound that includes a space Use this punctuation when there are compelling grounds for retaining the construction. For example, from a speech that is simply transcribed and cannot be re-worded; or in a heading where it has been judged most natural as a common name. Otherwise recasting is better.
 * ex–prime minister Thatcher;  pre–World War II aircraft;   but not credit card–sized
 * Keep: Post–September 11 anti-war movement; Trans–New Guinea languages (existing TechInfoDepot articles)
 * Best to recast the examples shown above: former prime minister Thatcher; aircraft [from] before World War II

The en dash in all of the compounds above is unspaced.

4. To separate items in certain lists Spaced en dashes are used within parts of certain lists. Here are two examples:
 * Pairing performers with instruments.
 * James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano.
 * Showing track durations on a CD.
 * "The Future" – 7:21; "Ain't No Cure for Love" – 6:17; "Bird on the Wire" – 6:14.

Other dashes
Do not use substitutes for em or en dashes, such as the combination of two hyphens (--). These were typewriter approximations.

For a negative sign or subtraction operator, use a minus sign (−, Unicode character U+2212 MINUS SIGN ). Input by clicking on it in the insert box beneath the edit window or by typing.

Slashes
Generally avoid joining two words by a slash, also known as a forward slash or solidus (/). 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 with clearer wording.

An example: The parent/instructor must be present at all times. Must both be present? (Then write the parent and the instructor.) Must at least one be present? (Then write the parent or the instructor.) Are they the same person? (Use a hyphen: the parent-instructor.)

In circumstances involving a distinction or disjunction, the en dash (see above) is usually preferable to the slash: the digital–analog distinction.

An unspaced slash may be used:
 * to indicate phonemic pronunciations (ribald is pronounced)
 * to separate the numerator and denominator in a fraction (7/8 or $7/8$)
 * to indicate regular defined yearly periods that do not coincide with calendar years (e.g. the 2009/10 fiscal year), if that is the convention used in reliable sources; see TechInfoDepot:Manual of Style/Dates and numbers for further explanation
 * where a slash occurs in a phrase widely used outside TechInfoDepot, and a different construction would be inaccurate, unfamiliar, or ambiguous

A spaced slash may be used:
 * to separate run-in lines in quoted poetry or song (To be or not to be: that is the question: / Whether 'tis nobler in the mind to suffer / The slings and arrows of outrageous fortune), or rarely in quoted prose, where careful marking of a paragraph break is textually important
 * to separate items that include at least one internal space (the NY 31 east / NY 370 exit), where for some reason use of a slash is unavoidable

Spaced slashes should be coded with a leading non-breaking space and a trailing normal space, as in  (which renders as x / y), to prevent improper line breaks.

Do not use the backslash character (\) in place of a slash.

Prefer the division operator (÷) to (/) when representing elementary arithmetic in general text: 10 ÷ 2 = 5. In more advanced mathematical formulas, a vinculum or slash is preferred: $$\textstyle\frac{x^n}{n!}$$ or xn/n!. (See TechInfoDepot:Manual of Style/Dates and numbers and Help:Displaying a formula.)

And/or
Avoid the construct and/or on TechInfoDepot. In general, where it is important to mark an inclusive or, use x or y, or both, rather than x and/or y. For an exclusive or, use either x or y, and optionally add 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 and/or. With two possibilities, at least the intention is clear; but with more than two it may not be. Instead of x, y, and/or z, use an appropriate alternative, such as one or more of x, y, and z; some or all of x, y, and z.

Sometimes or is ambiguous in another way: Wild dogs, or dingoes, inhabit this stretch of land. Are wild dogs and dingoes the same or different? For one case write: wild dogs (dingoes) inhabit ... or wild dogs, also known as dingoes, inhabit ... (meaning dingoes are wild dogs); for the other case write: either wild dogs or dingoes inhabit ....

Number signs

 * Avoid using the # symbol (known as the number sign, hash sign, or pound sign) when referring to numbers or rankings. Instead use the word "number", or the abbreviation "No." The abbreviation is identical in singular and plural. For example:
 * {|style="background:transparent"

An exception is issue numbers of comic books, which unlike for other periodicals are given in general text in the form #1, unless a volume is also given, like Volume 2, Number 7 or Vol. 2, No. 7.
 * Incorrect:  ||Her album reached #1 in the UK album charts.
 * Correct:              ||Her album reached No. 1 in the UK album charts.
 * }
 * Correct:              ||Her album reached No. 1 in the UK album charts.
 * }
 * Use Vol. and either No. or #.
 * Do not use the symbol №.

Terminal punctuation

 * Periods (also called "full stops"), question marks, and exclamation marks are terminal punctuation, the only punctuation marks used to end sentences in English.
 * In some contexts, no terminal punctuation is necessary. In such cases, the sentence often does not start with a capital letter. See Quotations, Quotation marks, and Sentences and brackets, above. Sentence fragments in captions or lists should in most cases not end with a period. See Formatting of captions and Bulleted and numbered lists below.
 * For the use of three periods in succession, see Ellipses, above.
 * Clusters of question marks, exclamation marks, or a combination of them (such as the interrobang), are highly informal and inappropriate in TechInfoDepot articles.
 * Use the exclamation mark with restraint. It is an expression of surprise or emotion that is generally unsuited to a scholarly or encyclopedic register.
 * Question marks and exclamation marks may sometimes be used in the middle of a sentence:
 * Why me? she wondered.
 * The Homeric question is not Did Homer write the Iliad? but How did the Iliad come into being?, as we have now come to realize.
 * The door flew open with a BANG! that made them jump. (Not encyclopedic, but acceptable in transcription from audio, or in direct quotation.)

Spacing
In normal text, never put a space before a comma, a semicolon, a colon, or a terminal punctuation mark (even in quoted material; see Allowable typographical changes, above). Put a space after these, unless they end a paragraph or are followed by a closing parenthesis, quotation mark, or similar.

Spaces following terminal punctuation
The number of spaces following the terminal punctuation of a sentence in the wiki markup makes no difference on TechInfoDepot; the MediaWiki software condenses any number of spaces to just one when rendering the page (see Sentence spacing). For this reason, editors may use any spacing style they prefer on TechInfoDepot. Multiple spacing styles may coexist in the same article, and adding or removing a double space is sometimes used as a dummy edit.

Consecutive punctuation marks
Where a proper noun that includes terminal punctuation ends a sentence, do not add a second terminal punctuation mark. Where such a noun occurs mid-sentence, punctuation may be added.
 * {|style="background:transparent"


 * Incorrect:||Slovak returned to the Red Hot Chili Peppers in 1985 after growing tired of What Is This?.
 * Correct:||Slovak returned to the Red Hot Chili Peppers in 1985 after growing tired of What Is This?
 * Correct:||Slovak, growing tired of What Is This?, returned to the Red Hot Chili Peppers in 1985.
 * }
 * Correct:||Slovak, growing tired of What Is This?, returned to the Red Hot Chili Peppers in 1985.
 * }
 * }

Punctuation and footnotes
 (ref tags) are used to create footnotes (sometimes called endnotes or notes). The ref tags should immediately follow the text to which the footnote applies, including any punctuation (see exceptions below), with no intervening space. Adjacent ref tags should have no space between them. Ref tags are used for explanatory notes but are more often used for citation footnotes.

When ref tags are used, a footnote list must be added, and is usually placed in the Notes and References section near the end of the article in the standard appendices and footers.

[Note: Dummy note links in these examples are not clickable.]
 * Example: Flightless birds have a reduced keel and smaller wing bones than flying birds of similar size.

Exceptions: ref tags are placed before dashes, not after; and where a footnote applies only to material within parentheses, the ref tags belong just before the closing parenthesis.
 *  Example: Paris is not the capital city of England—the capital of which is London—but that of France, and is widely known as a beautiful city.
 * Example: Kim Jong-un (Korean: 김정은; Hanja: 金正恩) is the third and youngest son of Kim Jong-il with his late consort Ko Young-hee.

Punctuation after formulae
A sentence that ends with a formula should have terminal punctuation (period, exclamation mark, or question mark) after the formula. Within a sentence, other punctuation (such as comma or colon) is used after a formula just as it would be if the text were not a formula. See Punctuation after formulae at the mathematics MoS page.

Dates and time
For ranges of dates and times, see En dashes above.

Dates should only be linked when they are germane and topical to the subject, as discussed at TechInfoDepot:Manual of Style/Linking.

Time of day
Time of day is normally expressed in figures rather than being spelled out. Context determines whether the 12- or 24-hour clock is used.
 * 12-hour clock times are written in the form 11:15 a.m. and 2:30 p.m., or the form 11:15 am and 2:30 pm, with a space (preferably a non-breaking space) before the abbreviation. Use noon and midnight rather than 12 pm and 12 am; it may need to be specified whether midnight refers to the start or the end of a date.
 * 24-hour clock times are written in the form 08:15, 22:55, with no suffix. Note that 00:00 refers to midnight at the start of a date, and 24:00 to midnight at the end of a date.

Days

 * For full dates, use the format 10 June 1921 or the format June 10, 1921. Similarly, where the year is omitted, use 10 June or June 10. For choice of format, see below.
 * Do not use numerical date formats such as "03/04/2005", as this could refer to 3 April or to March 4. If a numerical format is required (e.g. for conciseness in long lists and tables), use the YYYY-MM-DD format: 2005-04-03.

Choice of format

 * All the dates in a given article should have the same format (day-month or month-day). However, for citations, see TechInfoDepot:Citing sources. These requirements do not apply to dates in quotations or titles.
 * Articles on topics with strong ties to a particular English-speaking country should generally use the more common date format for that country (month-day for the US, except in military usage; day-month for most others; articles related to Canada may use either consistently).
 * Otherwise, do not change an article from one form to another without good reason. More details can be found at WP:MOSNUM.

Months and seasons

 * For month and year, write June 1921, with no comma.
 * Abbreviations for months, such as Feb. in the United States or Feb in most other countries, are used only where space is extremely limited.
 * Avoid ambiguous references to seasons (seasons are opposite in the southern and northern hemispheres).

Years and longer periods

 * Do not use the year before the digits (1995, not the year 1995), unless the meaning would otherwise be unclear.
 * Decades are written in the format the 1980s, with no apostrophe. Use the two-digit form ('80s) only with an established social or cultural meaning. Avoid forms such as the 1700s that could refer to 10 or 100 years.
 * Years are denoted by AD and BC or, equivalently, CE and BCE. Use only one system within an article, and do not change from one system to the other without good reason. The abbreviations are written without periods, and with a non-breaking space, as in 5 BC. Omit AD or CE unless this would cause ambiguity.

More information on all of the above topics can be found at WP:MOSNUM, including the handling of dates expressed in different calendars, and times corresponding to different time zones.

Current
Use of the term "current" should be avoided. What is current today may not be tomorrow; situations change over time. Instead, use date- and time-specific text. To help keep information updated use the as of template.
 * {|style="background:transparent"


 * Incorrect:||He is the current ambassador to ...
 * Correct:||As of 2011, he is the ambassador to ...
 * }
 * Correct:||As of 2011, he is the ambassador to ...
 * }

Numbers
MOSNUM clarifies a number of situations, including the following:
 * In general, write whole numbers from one to nine as words, write other numbers that take two words or fewer to say as either figures or words (with consistency within each article), and write all other numbers as figures: 1/5 or one fifth, 84 or eighty-four, 200 or two hundred, but 3.75, 544, 21 million. See MOSNUM for exceptions and fine points.
 * In general, use a comma to delimit numbers with five or more digits to the left of the decimal point. Numbers with four digits are at the editor's discretion: 12,345, but either 1,000 or 1000.  See MOSNUM for exceptions.
 * In general, use decimals rather than vulgar fractions with measurements, but the latter are permitted with measuring systems such as Imperial units, Avoirdupois, and U.S. customary units. Keep articles internally consistent.
 * Scientific notation (e.g. $5.8 kg$) is preferred in scientific contexts; editors can use the val template, which generates such expressions with the syntax.
 * Write out "million" and "billion" on the first use. After that, unspaced "M" can be used for millions and "bn" for billions: 70M and 25bn. See MOSNUM for similar words.
 * Write 3%, three percent, or three per cent, but not 3 % (with a space) or three %. "Percent" is American usage, and "per cent" is British usage (see National varieties of English, above). In ranges of percentages written with an en dash, write only one percent sign: 3–14%.
 * Indicate uncertainties as value/±/uncertainty/×/10n/unit symbol: $5.8 kg$ See MOSNUM for other acceptable formats.

Currencies

 * Use the full abbreviation on first use (US$ for the U.S. dollar and A$ for the Australian dollar), unless the currency is already clear from context. For example, the Government of the United States always spends money in American dollars, and never in Canadian or Australian dollars.
 * Use only one symbol with ranges, as in $250–300.
 * In articles that are not specific to a country, express amounts of money in United States dollars, euros, or pounds sterling. Do not link the names or symbols of currencies that are commonly known to English-speakers ($, £, €), unless there is a particular reason to do so; do not use potentially ambiguous currency symbols, unless the meaning is clear in the context.
 * In country-specific articles, use the currency of the country. On first occurrence, consider including conversion to US dollars, euros, or pounds sterling, at a rate appropriate to the context. For example, Since 2001 the grant has been 10,000,000 Swedish kronor (US$1.4M as of August 2009); alternatively: Since 2001 the grant has been 10,000,000 Swedish kronor (€1.0M as of August 2009). Wording such as "approx." is not appropriate for simple rounding-off of the converted amount.
 * Generally, use the full name of a currency, and link it on its first appearance if English-speakers are likely to be unfamiliar with it (52 Nepalese rupees); subsequent occurrences can use the currency sign (just 88 Rs).
 * Most currency signs are placed before the number; they are unspaced ($123), except for alphabetic signs (R 75).

Units of measurement

 * The main unit in which a quantity is expressed should generally be an SI unit or non-SI unit officially accepted for use with the SI. However:
 * Scientific articles may also use specialist units appropriate for the branch of science in question.
 * In non-scientific articles relating to the United States, the main unit is generally an American customary unit (22 pounds (10 kg)).
 * In non-scientific articles relating to the United Kingdom, although the main unit is generally a metric unit (10 kg (22 pounds)), Imperial units are still used as the main units in some contexts (7 miles (11 km) by road).
 * Where English-speaking countries use different units for the same measurement, provide a conversion in parentheses. Examples: the Mississippi River is 2320 mi long; the Murray River is 2375 km long. The template is useful for producing such expressions.
 * In a direct quotation, always keep the source units. If a conversion is required, it should appear within square brackets in the quote, or else an obscure use of units can be explained in a footnote.
 * In places where space is limited, such as tables, infoboxes, and parenthetical notes, and in mathematical formulas, use unit symbols. In main text it is usually better to spell out unit names, but symbols may also be used when a unit (especially one with a long name) is used repeatedly. However, spell out the first instance of each unit in an article (for example, the typical batch is 250 kilograms ... and then 15 kg of emulsifier is added), except for unit names that are hardly ever spelled out (e.g. the degree Celsius). Most unit names are not capitalized. Use "per" when writing out a unit, rather than a slash: meter per second, not meter/second. (For spelling differences, follow National varieties of English, above.)
 * Potentially unfamiliar unit symbols should be introduced parenthetically at their first occurrence in the article, with the full name given first: for example, His initial betatron reached energies of 2.3 megaelectronvolts (MeV), while subsequent betatrons achieved 300 MeV.
 * For ranges, see En dashes: other uses (above) and MOSNUM.
 * When dimensions are given, each number should be followed by a unit name or symbol (e.g. write 1 m × 3 m × 6 m, not 1 × 3 × 6 m).
 * When they form a compound adjective, values and unit names should be separated by a hyphen: for example, a five-day holiday.
 * Unit symbols are preceded by figures, not by spelled-out numbers. Values and unit symbols are separated by a non-breaking space. For example, 5 min. The percent sign, and units of degrees, minutes, and seconds for angles and coordinates, are unspaced.
 * Standard unit symbols do not require a full stop (period). However non-standard abbreviations should always be given a full stop.
 * No s is appended, e.g. km, in, lb, not kms, ins, lbs.
 * Write powers of unit symbols with HTML, e.g. 5 km2 not Unicode superscripts and subscripts.
 * For quantities of bytes and bits, specify whether the binary or decimal meanings of K, M, G, etc. are intended. The IEC prefixes kibi-, mebi-, gibi-, etc. (symbols Ki, Mi, Gi, etc.) are not familiar to most readers, and should not generally be used (for exceptions, see MOSNUM).

Common mathematical symbols

 * For a negative sign or subtraction operator, use a minus sign (−, Unicode character U+2212 MINUS SIGN ). Input by clicking on it in the insert box beneath the edit window or by typing.
 * For a multiplication sign between numbers, use × (Unicode character U+00D7 MULTIPLICATION SIGN ), which is input by clicking on it in the edit toolbox under the edit window or by typing .  However, the unspaced letter x is accepted as a substitute for by in such terms as 4x4.
 * Exponentiation is indicated by a superscript, an (typed as ). Exponential notation can be spaced or unspaced, depending on circumstances.
 * Do not use programming language notation outside computer program listings. In most programming languages, subtraction, multiplication, and exponentiation are respectively represented by the hyphen-minus , the asterisk  , and either the caret   or the double asterisk  , and scientific notation is replaced by E notation.
 * Symbols for binary operators and relations are spaced on both sides:
 * plus, minus, and plus-or-minus (as binary operators): +, −, ± (as in 5 − 3);
 * multiplication and division: ×, ÷;
 * equals, does not equal, equals approximately: =, ≠, ≈;
 * is less than, is less than or equal to, is greater than, is greater than or equal to: <, ≤, >, ≥.
 * Symbols for unary operators are closed-up to their operand:
 * positive, negative, and positive-or-negative signs: +, −, ± (as in −3);
 * other unary operators, such as the exclamation mark as a factorial sign (as in 5!).

Possessives
''For the apostrophe character, see above. For thorough treatment of the English possessive see Apostrophe.''

Singular nouns
 * For the possessive of most singular nouns, add 's (my daughter's achievement, my niece's wedding, Cortez's men, the boss's wife, Glass's books, Illinois's largest employer, Descartes's philosophy, Verreaux's eagle). Exception: abstract nouns ending with an /s/ sound, when followed by sake (for goodness' sake, for his conscience' sake).
 * For the possessive of singular nouns ending with just one s (sounded as /s/ or /z/), there are three practices:
 * Add 's: James's house, Sam Hodges's son, Jan Hus's life, Vilnius's location, Brahms's music, Dickens's novels, Morris's works, the bus's old route.
 * Add just an apostrophe: James' house, Sam Hodges' son, Jan Hus' life, Vilnius' location, Brahms' music, Dickens' novels, Morris' works, the bus' old route.
 * Add either 's or just an apostrophe, according to how the possessive is pronounced:
 * Add only an apostrophe if the possessive is pronounced the same way as the non-possessive name: Sam Hodges' son, Moses' leadership;
 * Add 's if the possessive has an additional at the end: Jan Hus's life, Morris's works.
 * Some possessives have two possible pronunciations: James's house or James' house, Brahms's music or Brahms' music, Vilnius's location or Vilnius' location, Dickens's novels or Dickens' novels.
 * Apply just one of these three practices consistently within an article. If the third practice is used and there is disagreement over the pronunciation of a possessive, the choice should be discussed and then that possessive adopted consistently in an article. (Possessives of certain classical and biblical names have traditional pronunciations that may be deemed to take precedence: Jesus' answer and Xerxes' expeditions, but Zeus's anger; and in some cases—particularly possessives of inanimate objects—rewording may be an option: the location of Vilnius, the old bus route, the moons of Mars.)

Plural nouns
 * For a normal plural noun, ending with a pronounced s, form the possessive by adding just an apostrophe (my sons' wives, my nieces' weddings).
 * For a plural noun not ending with a pronounced s, add 's (women's careers, people's habits, the mice's whiskers; The two Dumas's careers were controversial, but where rewording is an option, this may be better: The career of each Dumas was controversial).

Official names
 * Official names (of companies, organizations, or places) should not be altered (St Thomas' Hospital should therefore not be rendered as St Thomas's Hospital, even for consistency).

Pronouns
 * The possessive its (the dog chased its tail) has no apostrophe. (It's is the short form of it is or it has: it's a nice day, it's been a nice day.) Hers, ours, yours, theirs, and whose likewise lack apostrophes. Possessives of non-personal pronouns such as everyone are formed as if they were nouns (everyone's mother, nobody's hat, anyone else's opinion, the others' husbands).

First-person pronouns
TechInfoDepot articles must not be based on one person's opinions or experiences, so never use I, my, or similar forms (except in quotations).

Also avoid we, us, and our: We should note that some critics have argued against our proposal (personal rather than encyclopedic). But these forms are acceptable in certain figurative uses. For example:
 * In historical articles to mean the modern world as a whole: The text of De re publica has come down to us with substantial sections missing.
 * The author's we found in scientific writing: We are thus led also to a definition of "time" in physics (Albert Einstein); Throughout the proof of this theorem we assume that the function ƒ is uniformly continuous. Often rephrasing is preferable: Throughout the proof of this theorem it is assumed that the function ƒ is uniformly continuous.

Second-person pronouns
Do not use the second person (you, your); it is often ambiguous and contrary to the tone of an encyclopedia (see also Instructional and presumptuous language, below).
 * Use the third person (a noun, or he, one, etc.): instead of When you move past "Go", you collect $200, use When players pass "Go", they collect $200, or A player passing "Go" collects $200.
 * The passive voice may sometimes be used instead: When "Go" is passed, $200 is collected.

Plurals
Use the appropriate plural; allow for cases (such as excursus or hanif) in which a word is now listed in major English dictionaries, and normally takes an s or es plural, not its original plural: two excursuses, not two excursus as in Latin; two hanifs, not two hanufa as in Arabic.

Some collective nouns—such as team (and proper names of them), army, company, crowd, fleet, government, majority, mess, number, pack, and party—may refer either to a single entity or to the members that compose it. In British English, such words are sometimes treated as singular, but more often treated as plural, according to context. Exceptionally, names of towns and countries usually take singular verbs (unless they are being used to refer to a team or company by that name, or when discussing actions of that entity's government). For example, in England are playing Germany tonight, England refers to a football team; but in England is the most populous country of the United Kingdom, it refers to the country. In North American English, these words (and the United States, for historical reasons) are almost invariably treated as singular; the major exception is when sports teams are referred to by nicknames that are plural nouns, when plural verbs are commonly used to match. See also National varieties of English above.

Contractions
Uncontracted forms such as do not or it is are the default in encyclopedic style; don't and it's are too informal. But contractions should not be expanded mechanically. Sometimes rewriting the sentence as a whole is preferable; occasionally contractions provide the best solution anyway.

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), which should not be altered; or to wording about one-gender contexts, such as an all-female school (When any student breaks that rule, she loses privileges).

Ships may be referred to using either feminine forms ("she", "her", "hers") or neutral forms ("it", "its"). Either usage is acceptable, but each article should be internally consistent and employ one or the other exclusively. As with all optional styles, articles should not be changed from one style to another unless there is a substantial reason to do so. See TechInfoDepot:Manual of Style/Military history.

Contested vocabulary
Avoid words and phrases that give the impression of straining for formality, that are unnecessarily regional, or that are not widely accepted. See List of English words with disputed usage and TechInfoDepot:List of commonly misused English words; see also Identity (below) and Gender-neutral language (above).

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 information in the first place. Do not tell readers that something is ironic, surprising, unexpected, amusing, coincidental, etc. This supplies a point of view. Simply state the sourced facts and allow readers to draw their own conclusions.

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 redundant subset terms (so avoid constructions like these: Among the most well-known members of the fraternity are included two members of the Onassis family or The elements in stars include hydrogen, helium, etc.). Do not use including to introduce a complete list, where comprising, consisting of, or composed of would be more accurate.

Identity

 * Disputes over how to refer to a person or group are addressed by policies such as Verifiability, Neutral point of view, and Article titles where the term appears in the title of an article. When there is no dispute, the term most commonly used for a person will be the one that person uses for himself or herself, and the most common terms for a group will be those that the group most commonly uses for itself. TechInfoDepot should use them too. (For example, see the article Jew, which demonstrates that most Jews prefer that term to "Jewish person".)
 * Any person whose gender might be questioned should be referred to by the gendered nouns (for example "man/woman", "waiter/waitress", "chairman/chairwoman"), pronouns, and possessive adjectives that reflect that person's latest expressed gender self-identification. This applies in references to any phase of that person's life. Direct quotations may need to be handled as exceptions. Nevertheless, avoid confusing or seemingly logically impossible text that could result from pronoun usage (for example: instead of He gave birth to his first child, write He became a parent for the first time).
 * Use specific terminology. For example, often it is more appropriate for people from Ethiopia (a country in Africa) to be described as Ethiopian, not carelessly (with the risk of stereotyping) as African.
 * The adjective Arab (never to be confused with Muslim or Islamic) refers to people and things of ethnic Arab origin. The term Arabic refers to the Arabic language or writing system, and related concepts (Not all Arab people write or converse in Arabic).

Foreign terms
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
 * Loanwords and borrowed phrases that have common usage in English—Gestapo, samurai, vice versa—do not require italics. A rule of thumb is not to italicize words that appear unitalicized in major English-language dictionaries.

Spelling and romanization

Names not originally written in a Latin alphabet (written for example in Greek, Cyrillic, or Chinese scripts) must be given a romanized form for use in English. Use a systematically transliterated or otherwise romanized name (Aleksandr Tymoczko, Wang Yanhong); but if there is a common English form of the name (Tchaikovsky, Chiang Kai-shek), use that form instead.

The use of diacritics (such as accent marks) for foreign words is neither encouraged nor discouraged; their usage depends on whether they appear in verifiable reliable sources in English and on the constraints imposed by specialized TechInfoDepot guidelines. Provide redirects from alternative forms that use or exclude diacritics.

Spell a name consistently in the title and the text of an article. See relevant policy at Article titles; see also Naming conventions (use English). For foreign names, phrases, and words generally, adopt the spellings most commonly used in English-language references for the article, unless those spellings are idiosyncratic or obsolete. If a foreign term does not appear in the article's references, adopt the spelling most commonly used in other verifiable reliable sources (for example other English-language dictionaries and encyclopedias). For punctuation of compounded forms, see relevant guidelines in Punctuation, above.

Sometimes the usage will be influenced by other guidelines such as National varieties of English, above, which may lead to different choices in different articles.

Technical language
Some topics are intrinsically technical, but editors should try to make them understandable to as many readers as possible. Minimize jargon, or at least explain it; or tag it using Technical or Technical-statement for other editors to fix. For unavoidably technical articles a separate introductory article (like Introduction to special relativity) may be the best solution. Avoid excessive wikilinking (linking within TechInfoDepot) as a substitute for parenthetic explanations such as the one in this sentence. Do not introduce new and specialized words simply to teach them to the reader, when more common alternatives will do. When the notions named by jargon are too complex to concisely explain in a few parenthetical words, write one level down. For example, consider adding a brief background section with main tags pointing to the full treatment article(s) of the prerequisite notions; this approach is practical only when the prerequisite concepts are central to the exposition of the article's main topic, and when such prerequisites aren't too numerous. Short articles like stubs generally do not have such sections.

Geographical items
Places should generally be referred to consistently by the same name as in the title of their article (see TechInfoDepot:Naming conventions (geographic names)). Exceptions are made if there is a widely accepted historical English name appropriate to the given context. In cases where such a historical name is used, it should be followed by the modern name in round brackets (parentheses) on the first occurrence of the name in applicable sections of the article. This resembles linking; it should not be done to the detriment of style. On the other hand, it is probably better to provide such a variant too often than too rarely. If more than one historical name is applicable for a given context, the other names should be added after the modern English name, that is: "historical name (modern name, other historical names)".

Images

 * Infoboxes, images, and related content in the lead must be right-aligned.
 * Use captions to clarify the relevance of the image to the article (see Captions, below).
 * Each image should be inside the major section to which it relates (within the section defined by the most recent level 2 heading or at the top of the lead), not immediately above the section heading.
 * Avoid sandwiching text between two images that face each other, and between an image and an infobox or similar.
 * It is often preferable to place images of faces so that the face or eyes look toward the text. However, it is not necessary to reverse an image simply to have the subject facing the text.
 * Multiple images in the same article can be staggered right-and-left (for example, [ Timpani]).
 * The thumbnail option may be used (" "), or another size may be fixed. The default thumbnail width is 220 pixels; users can adjust this in their preferences. Lead images should be no wider than "upright=1.35" (by default this is 300 pixels). See Manual of Style/Images for information on when and how to use other sizes.
 * Link to more images on Wikimedia Commons when appropriate; see TechInfoDepot:Wikimedia sister projects for advice and methods. The use of galleries should be in keeping with TechInfoDepot's image use policy.
 * Avoid referring to images as being on the left or right. Image placement is different for viewers of the mobile version of TechInfoDepot, and is meaningless to people having pages read to them by assistive software. Instead, use captions to identify images.
 * Alt text takes the place of an image for text-only readers, including those using screen readers. Images should have an alt attribute added to the alt parameter. See WP:ALT for more information.

Avoid entering textual information as images
Textual information should almost always be entered as text rather than as an image. True text can be colored and adjusted with CSS tags and templates, but text in images cannot be. Images are not searchable, are slower to download, and are unlikely to be read as text by devices for the visually impaired. Any important textual information in an image should also appear in the image's alt text, caption, or other nearby text.

Captions
Photographs and other graphics should always have captions, unless they are "self-captioning" images (such as reproductions of album or book covers) or when they are unambiguous depictions of the subject of the article. In a biography article no caption is necessary for a portrait of the subject pictured alone; but one might be used, to give the year, the subject's age, or other circumstances of the portrait along with the name of the subject.

Formatting of captions

 * 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 any complete sentence occurs in a caption, all sentences and any sentence fragments in that caption should end with a period.
 * The text of captions should not be specially formatted (with italics, for example), except in ways that would apply if it occurred in the main text.
 * Captions should be succinct; more information about the image can be included on its description page, or in the main text.
 * Captions for technical charts and diagrams may be substantially longer than those for other images. Captions for technical images should fully describe all the elements of the image, and the image's significance.

Bulleted and numbered lists

 * Do not use lists if a passage is read easily as plain paragraphs.
 * Use proper wikimarkup- or template-based list code (see WP:Manual of Style/Lists and Help:List).
 * 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 item as beginning a new list.
 * Use numbers rather than bullets only if:
 * a need to refer to the elements by number may arise;
 * the sequence of the items is critical; or
 * the numbering has some independent meaning, for example in a listing of musical tracks.
 * Use the same grammatical form for all elements in a list, and do not mix sentences and sentence fragments as elements.
 * When the elements are complete sentences, each one is formatted with sentence case (its first letter is capitalized) and a final period (full stop).
 * When the elements are sentence fragments, the list is typically introduced by a lead fragment ending with a colon. When these elements are titles of works, they retain the original capitalization of the titles. Other elements are formatted consistently in either sentence case or lower case.

Wikilinks
Make links only where they are relevant and helpful in the context: Excessive use of hyperlinks can be distracting, and may slow the reader down. Redundant links (like the one in the tallest people on Earth) clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly.

Linking to sections: A hash sign (#) followed by the appropriate heading will lead to a relevant part of a page. For example,  links to a particular section of the article Apostrophe.

Initial capitalization: TechInfoDepot'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: Snakes are often venomous, but lizards only rarely (see Poison).

Check links: Ensure that the destination is the intended one; many dictionary words lead to disambiguation pages and not to complete or well-chosen articles.

Keep markup simple
The simplest markup is often the easiest to edit, the most comprehensible, and the most predictable. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly; in particular, do not use the CSS  or   properties because they break rendering on some browsers when large fonts are used.

An HTML entity is sometimes better than the equivalent Unicode character, which may be difficult to identify in edit mode; for example,  is understood where   (the upper-case form of Greek  ) may not be.

Formatting issues
Modifications in font size, blank space, and color (see Color coding, below) are an issue for the TechInfoDepot site-wide style sheet, and should be reserved for special cases only.

Typically, the use of custom font styles will:
 * reduce consistency, since the text will no longer look uniform;
 * reduce usability, since it might be impossible for people with custom style sheets (for accessibility reasons, for example) to override it, and it might clash with a different skin as well as inconvenience people with color blindness (see below); and
 * cause disputes, since other editors may disagree aesthetically with the choice of style.

Outside article text, different font sizes are routinely used in navigation templates and infoboxes, tables (especially in larger ones), and some other contexts where alternatives are not available (such as table captions). Specify font sizes relatively (for example in CSS with ) rather than absolutely (like  ).

Color coding
Information should be accessible to all. Do not use color alone to mark differences in text: they may be invisible to people with color blindness. Also, black-and-white printouts, older computer displays with fewer colors, and monochrome displays (older PDAs and cell phones) cannot show such distinctions.

Choose colors that can be distinguished by the readers with the commonest form of colorblindness (red–green), such as maroon  and  teal ; and also mark the differences with change of font or some other means (maroon and alternative font face,  teal ). Viewing the page with Vischeck can help with the choice of colors. See also color coding.

Scrolling lists and collapsible content
Scrolling lists, and boxes that toggle text display between hide and show, should not conceal article content, including reference lists, image galleries, and image captions. They especially should not be used to conceal "spoiler" information (see TechInfoDepot:Spoiler). Collapsible sections or cells may be used in tables that consolidate information covered in the main text, and in navboxes. When scrolling lists or collapsible content are used, take care that the content will still be accessible on devices that do not support JavaScript or CSS.

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 inadvertently change the formatting, for example by introducing white space in read mode.

To leave an invisible comment, enclose the text you intend to be read only by editors between  and. For example:.

Pronunciation
Pronunciation in TechInfoDepot is indicated in the International Phonetic Alphabet (IPA). In most situations, for ease of understanding by the majority of readers and across variants of the language, quite broad IPA transcriptions are best for English pronunciations. See TechInfoDepot:IPA for English and TechInfoDepot:IPA (general) for keys, and IPA for templates that link to these keys. For English pronunciations, pronunciation respellings may be used in addition to the IPA.

Within Manual of Style
(Links to policy and guidelines on specific questions.)

Names

 * Policy for naming articles: WP:AT
 * Proper names
 * Generally (dedicated MOS page): TechInfoDepot:Manual of Style/Proper names (MOS:PN)
 * Place names: MOS:PN, at Place names
 * Diacritical marks in names: MOS:PN, at Diacritics
 * Same name for peoples and languages: MOS:PN, at Peoples and their languages
 * Naming and identifying individuals and peoples:
 * Generally: current page, at MOS:IDENTITY
 * Specifically (for individuals): MOS:BIO, at WP:FULLNAME
 * Opening paragraph of biographies: MOS:BIO, at WP:OPENPARA
 * Names of organizations:
 * Generally (may have application beyond cue sports): MOS:CUE, at Respect for official organization names
 * Names that are also trademarks (dedicated MOS page): MOS:TM
 * Names of animal species, etc. (in article titles): WP:FAUNA

Capitalization

 * Generally (dedicated MOS page): MOS:CAPS
 * In musical items: MOS:MUSIC, at Capitalization

Language varieties

 * English national varieties (U.S., British, and other): current page, at WP:ENGVAR
 * Commonalities across national varieties: current page, at WP:COMMONALITY
 * Topic strongly tied to one nation: current page, at MOS:TIES

Foreign terms used in English

 * current page, at MOS:FOREIGN

Quotations in articles

 * Generally: current page, at MOS:QUOTE
 * Form of quotation marks: current page, at MOS:QUOTATION MARKS

Numbers, times, and dates

 * Generally (dedicated MOS page): WP:MOSNUM
 * Fractions: WP:MOSNUM, at MOS:FRAC
 * Months, seasons, years, and longer periods of time: WP:MOSNUM, at Longer periods

Lists

 * Bulleted, numbered, or otherwise: current page, at Bulleted and numbered lists

Punctuation guidance

 * Generally: current page, at Punctuation
 * Apostrophe: current page, at Apostrophes
 * Possessive apostrophe: current page, at MOS:POSS
 * Ampersand ("&"): current page, at MOS:&
 * Hyphen ("-"): current page, at MOS:HYPHEN
 * Dashes
 * Generally (em dash "—" and en dash "–"): current page, at MOS:DASH
 * En dash (more): current page, at MOS:ENDASH
 * Em dash, no spaces before or after: current page, at MOS:EMDASH

Style guides on other Wikimedia projects

 * Wikibooks:Manual of Style – Wikibooks, collection of open-content textbooks
 * Wikinews:Style guide – Wikinews, the free news source
 * Wikiquote:Manual of style – Wikiquote
 * Wikisource:Style guide – Wikisource
 * Wikiversity:Manual of Style – Wikiversity
 * Wikivoyage:Manual of style – Travel guides at Wikivoyage
 * Wiktionary:Style guide – Wiktionary

Search engines

 * OnlineStylebooks.com (a stylebook search engine)