Wikipedia:Too long; didn't read

"WP:BECONCISE" redirects here. For the policy on article title length, see WP:CONCISE.

"WP:SUCCINCT" redirects here. For the style guideline for succinctness in articles, see Wikipedia:Manual of Style.

“ The present letter is a very long one, simply because I had no leisure to make it shorter. ” — Blaise Pascal

Too long; didn't read (abbreviated TL;DR and tl;dr) is a shorthand to indicate that a passage is too long to invest the time to digest it. Akin to Wall of text.

The label is often used to point out excessive verbosity or to signify the presence of and location of a short summary in case the page is too long and won't otherwise be read. It can be misused as a tactic to thwart collaborative editing or a stoop to ridicule. If a discussion is reasonably concise, it is best practice to read it before commenting.

Reasons for length

Many people edit Wikipedia because they enjoy writing; however, that passion can result in overlong composition. This reflects a lack of time or commitment to refine an effort through successively more concise drafts. With some application, natural redundancies and digressions can often be eliminated. Recall the venerable paraphrase of Pascal: "I made this so long because I did not have time to make it shorter."

Also writers can incorrectly believe that long sentences and big words make that writer appear learned. Some inexperienced contributors over-avoid leaving any ambiguity by using more words (see WP:NOTSTATUTE/GUIDE). Even capable authors recognize the risk of distortion through brevity.

Some policies and procedures can encourage overlong prose due to imposing arbitrary limits. The Did you know? process requires established articles to have a fivefold expansion of prose within a seven-day window to be considered for listing on the main page. This can encourage over-verbose writing to game the system.

A trusted aphorism states that "brevity is the soul of wit." Similarly, "omit needless words." Editors are encouraged to write concisely and to use plain vocabulary when possible. Remember that English may not be a reader's native tongue. If length is essential, a short summary is advised.

While bloated composition may reflect the emotions of an editor, it should be noted that some people are constitutionally loquacious. It is impossible for you, as an editor, to affect either of these before the fact. When editing, always respect Wikipedia policies and editors' feelings. Take the time to distill your thoughts for better communication and rapport.

Internal policy discussions on talk pages can often become long-winded, too, usually for two reasons: because of the detailed nature of Wikipedia policies and guidelines (and their often complicated interaction with each other), and because curt and questionable assertions of policy rationales (especially when many are made in series in a single post) may require a fairly detailed response. The cure for this problem is to make a clear, policy-related statement to begin with, and avoid citing more policy and guideline pages than are necessary to get the point across (many say the same thing in slightly different wording). If you cite five such pages in vague terms for the same point, you open the door to wikilawyering about wording and interpretation – you may get five paragraphs of rebuttal in response instead of one sentence of agreement.

Reducing wordiness

See also: Wikipedia:Summary style and Wikipedia:Content forking § Article spinoffs

“ Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away ” — Antoine de Saint-Exupéry, French writer and aviator

Per the Manual of Style, text in Wikipedia should be written succinctly; or, existing texts should be trimmed if it contains redundancy. The article should be split into another article when appropriate. Be clear before excising copy that it can't be refined and kept. Tagging bloated plot summaries at movie, book, and play pages with the {{plot}} template is not as good as winnowing them yourself.

Some linguists (such as Geoffrey K. Pullum in posts at Language Log) criticize Strunk & White's advice "omit needless words" in the fear that unskilled editors may mistake even necessary length for dross and delete it. Strunk and White, however, were unambiguous that concision does not require "the writer make all his sentences short, or that he avoid all detail and treat his subjects only in outline, but that every word tell." Deleting is not always equivalent to improving, and intelligently differentiating the cases deserves care.

Maintain civility

Being too quick to pointedly mention this essay may come across as dismissive and rude. Preferably, create a section on their talk page and politely offer advice there.

Avoid ad hominems. Substituting a flippant "tl;dr" for reasoned response and cordiality stoops to ridicule and amounts to thought-terminating cliché. Just as one cannot prove through verbosity, neither can one prove by wielding a four letter initialism. When illumination, patience, and wisdom are called for, answer with them.

Some quick tips

• Provide summary/ synopsis

A further option for both readers and writers is to structure the writing so it can be skimmed effectively. This means writing the first sentence of each paragraph as a summary of the paragraph, so the reader can quickly know which paragraphs or sections are of interest to read for more detail, in addition to the usual practice of putting a summary at the beginning of articles or sections. This works even when the content is concise, or for some uses should be complete, but a reader wishes to skim for speed in a disciplined and more accurate way.

• If any talk page discussion is too long:
  • First best try to trim your response yourself. Maybe you can try writing first in your own sandbox before posting on the talk page. Remember don't edit other user's responses.
  • <u> Underline important sentences </u> in your response can help readers in quick browsing. Rather than repeating same arguments again and again you can use (emphasis added) or (pl. read again), if needed, in brackets.

• • Use collapse template

for your detailed long paragraphs
Use {{collapse top|Reply with details 1}} {{collapse bottom}}

• • Provide mid discussion synopsis and discussion end synopsis. Always remember Wikipedia is collaborative project and synopsis helps other users to understand main points of ongoing discussion.
  • If one wants to dot down thorough response for record sake, can write in own user space sub-page and a link in the discussion.
• In Nutshell: Be concise.

See also

• Wikipedia:Article size
• Wikipedia:Avoid instruction creep: Wikipedia's rules and guidelines should not become excessively complicated
• Wikipedia:Don't bludgeon the process
• Wikipedia:Germane
• Wikipedia:Hold the pepper
• Wikipedia:Keep it concise
• Wikipedia:Manual of Style
• Wikipedia:It should be noted
• Wikipedia:Read before commenting, which advocates familiarizing yourself with a discussion before participating in it
• Wikipedia:Too much detail
• Wikipedia:Wall of text
• User:Tony1/Redundancy exercises: removing fluff from your writing
• Template:Policy in a nutshell
• {{TLDR}} – adds (tl;dr); for use in discussions
• {{Very long}} – Template used to flag articles or sections that need trimming.
• Hypergraphia
• Logorrhea
• Self-reference

External links

• Tim Dowling, "Wikipedia too long-winded for you? Try the simple version," The Guardian,14 January 2008. Retrieved 14 April 2024.