Strikethrough

Appearance

Strikethrough primarily appears as a horizontal line across the middle of words. This appearance is the easiest to achieve by hand, as it only requires one continuous stroke with a pen, pencil, or other writing instruments. Less common forms of strikethrough include drawing an X (cross) or / (solidus) over each letter of the word. To strike long words or phrases, this method is cumbersome to produce by hand, but may be the preferred method for single letters, where the horizontal line does not produce the necessary visibility, and could be missed.

On personal computers, double strikethrough is an option in some word processors, spreadsheets, presentation software, and graphics software, e.g., in Microsoft Office, Collabora Online and LibreOffice. In Japan, double strikethrough is conventionally used because in complex kanji, a single strikethrough may be missed or confused with a stroke in the character. Otherwise, there is no generally agreed meaning of double strikethrough.

Uses

In modern prose, however, strikethrough is primarily used to mark text as a mistake or to be removed. Word processors capable of tracking changes use strikethrough on deleted words.

Historically, however, strikethrough was not even the primary way to mark errors. Errors were more commonly marked by placing dots under letters to be ignored (). In medieval manuscripts such as the Domesday Book, "strikethrough" of text with red ink often functions as highlighting similar to modern underline.

Computer representations

Word processors

Wordstar supported the "strikeout" decoration since version 3.0 in 1982, although the functionality may have been present in earlier versions. Wordstar was launched in 1978. It dominated the personal computer market as the most popular word processing program until 1985, when WordPerfect gained dominance. All word processors with functionality beyond basic editing include strikeout, though the prefer the term "strikethrough".

HTML and CSS

Early versions of the Hypertext Markup Language (HTML) specify the or tags for rendering text with strikethrough. These tags, however, are purely decorative. In 1999, the HTML standard version 4.01 deprecated them in favor of the tag, a semantic element for marking deleted text. Web browser and other user agents often render the contents of this tag with strikethrough. In the HTML5 draft, the is redefined as a semantic tag that marks its text that as no longer correct. The remains unchanged and still specifies deleted text.

Since HTML5 has done away with purely decorative strikethrough tags, the Cascading Style Sheets (CSS) language is in charge of decoration and formatting. A CSS user agent renders the text with strikethrough when the text-decoration CSS property has a line-through value. For example:

<span style="text-decoration: line-through;">ABCD efghi</span></syntaxhighlight>

...renders as:

<blockquote><span style="text-decoration: line-through;">ABCD efghi</span></blockquote>

The {{tag|s|o}} and {{tag|del|o}} tags already carry the aforementioned strikethrough definition, but also attach their semantic properties ("not longer correct" and "deleted") to the text.

==== Other markup symbols ====
* [[BB Code]], a markup language used on many [[web forum]]s, specifies the <code>[s]</code> and <code>[strike]</code> tags for decorating text with strikethrough.
* [[GitHub-flavored Markdown]] uses double tilde <code>~~</code> to wrap around text for strikethrough.<ref>{{cite web |url=https://help.github.com/articles/github-flavored-markdown/ |title=GitHub Flavored Markdown}}</ref>
* [[Google Chat]] or [[WhatsApp]] render text surrounded with the <code>~</code> (tilde) character as struck out.<ref>{{Cite web |title=Add formatting to your Google Chat messages - Computer - Google Chat Help |url=https://support.google.com/chat/answer/7649118 |access-date=2024-03-01 |website=support.google.com}}</ref>

=== Unicode ===
==== Combining characters ====
In [[plain text]] scenarios where markup cannot be used, [[Unicode]] offers a number of [[combining character]]s that achieve similar effects.

The "combining long stroke overlay" (<code>U+0336</code>) results in a stroke across text (may or may not be unbroken depending on the typeface used):
: A̶B̶C̶D̶ ̶e̶f̶g̶h̶i̶
while the "combining short stroke overlay" (<code>U+0335</code>) results in individually struck out characters:
: A̵B̵C̵D̵ ̵e̵f̵g̵h̵i̵
Similarly, the "combining short solidus overlay" (<code>U+0337</code>) results in diagonally struck out letters:
: A̷B̷C̷D̷ ̷e̷f̷g̷h̷i̷
as does the "combining long solidus overlay" (<code>U+0338</code>), which produces longer diagonal strokes:
: A̸B̸C̸D̸ ̸e̸f̸g̸h̸i̸

==== Specific struck-through characters ====
A number of characters that have the visual appearance of struck-through characters exist in Unicode, including: 

* [[ƀ]]
* [[Đ]]
* [[Ð]]
* [[Ǥ]]
* [[Ħ]]
* [[Ɨ]]
* [[Ɉ]]
* [[Ł]]
* [[Ƚ]]
* [[Ɵ]]
* [[ꝵ]]
* [[Ŧ]]
* [[Ʉ]]
* [[Ƶ]]
* [[ƻ]]
* [[ʡ]]
* [[ʢ]]
* [[Ғ]]
* [[Ҟ]]
* [[Ұ]]
* [[Ҍ]]

These usually have specific functions (for example, in the [[Latin Extended-A]] character set) or representations and are not intended for general use. However, they are not precomposed characters and have neither canonical nor compatibility decompositions. This issue has created security considerations since "precomposed" characters like U+019F and sequences like U+004F U+0335 or U+004F U+0336 often cause visual confusion (compare ⟨Ɵ⟩, ⟨O̵⟩ and ⟨O̶⟩). Unicode has acknowledged this issue and has proposed a standardized method for counteraction.<ref>The Unicode Consortium, [https://www.unicode.org/versions/Unicode6.1.0/ch02.pdf#page=44 The Unicode Standard, Chapter 2, Page 44, Non-decomposition of Overlaid Diacritics]</ref><ref>The Unicode Consortium, [https://www.unicode.org/reports/tr39/#Confusable_Detection Unicode Technical Standard #39: Unicode Security Mechanisms, chapter Confusable Detection]</ref>

For slashed letters in an orthography, unitary letters are provided by Unicode. The diacritics are used in generic applications, such as math operators which systematically use the solidus overlay to indicate negation.

== Research ==
Since at least 2014, researchers in the area of [[optical character recognition]] have attempted to solve the problem of recognizing struck-out text in handwritten documents.<ref>{{Cite book | doi=10.1109/ICFHR.2014.113| isbn=978-1-4799-4334-0| chapter=An Approach of Strike-Through Text Identification from Handwritten Documents| title=2014 14th International Conference on Frontiers in Handwriting Recognition| year=2014| last1=Adak| first1=Chandranath| last2=Chaudhuri| first2=Bidyut B.| pages=643–648| s2cid=5364504}}</ref><ref>{{Cite journal | doi=10.1016/j.patcog.2016.07.032| title=An approach for detecting and cleaning of struck-out handwritten text| year=2017| last1=Chaudhuri| first1=Bidyut B.| last2=Adak| first2=Chandranath| journal=Pattern Recognition| volume=61| pages=282–294| bibcode=2017PatRe..61..282C}}</ref>

== See also ==
*[[Bar (diacritic)]]
<!--
== Notes ==
-->

== References ==


[[Category:Typography]]

References

1. "Strikethrough".
2. (1970). "The original statutes of Cambridge University : the text and its history". Cambridge Eng. University Press.
3. See, e.g., [http://www.nationalarchives.gov.uk/education/focuson/domesday/take-a-closer-look/ this image] from the [[British National Archives]]' Focus on the Domesday Book.
4. "Exploring the WordStar file format".
5. [http://www.w3.org/TR/1999/REC-html401-19991224/present/graphics.html#h-15.2.1 15.2.1 Font style elements: the TT, I, B, BIG, SMALL, STRIKE, S, and U elements], HTML 4.01 Specification: Alignment, font styles, and horizontal rules, W3C. 24 December 1999.
6. [http://www.w3.org/TR/1999/REC-html401-19991224/struct/text.html#edef-del 9.4 Marking document changes: The INS and DEL elements] HTML 4.01 Specification: Text – Paragraphs, Lines, and Phrases, W3C. 24 December 1999.
7. [http://www.w3.org/TR/html5/text-level-semantics.html#the-s-element 4.5.5 The s element] {{Webarchive. link. (2015-08-01 ''HTML5'', W3C Last Call Working Draft. 17 June 2014.)
8. [http://www.w3.org/TR/html5/edits.html#the-del-element 4.6.2 The del element] ''HTML5'', W3C Last Call Working Draft 17 June 2014
9. "GitHub Flavored Markdown".
10. "Add formatting to your Google Chat messages - Computer - Google Chat Help".
11. The Unicode Consortium, [https://www.unicode.org/versions/Unicode6.1.0/ch02.pdf#page=44 The Unicode Standard, Chapter 2, Page 44, Non-decomposition of Overlaid Diacritics]
12. The Unicode Consortium, [https://www.unicode.org/reports/tr39/#Confusable_Detection Unicode Technical Standard #39: Unicode Security Mechanisms, chapter Confusable Detection]
13. (2014). "2014 14th International Conference on Frontiers in Handwriting Recognition".
14. (2017). "An approach for detecting and cleaning of struck-out handwritten text". Pattern Recognition.