Forking ‘i/o misquotes SF Chronicle’ by Dennis Hackethal

Original
Accurately reproduce the original text. Don’t change it – copy/pasting works best. Retain inline formatting by using markdown syntax.
Where is the original text from? Provide a link or, when quoting from a book, provide at least the author and title. The more information the better.
Quote
Quote the original. Do not use any surrounding quotation marks. If you are reusing a pre-existing quote, don’t change it; follow the guidelines given for the original text.
If you are reusing a pre-existing quote, provide a source. Again, the more information the better.
Used for omissions. The default is ‘[...]’, but ‘. . .’ and variations thereof are also commonly used. If you are reusing a pre-existing quote, reflect its use of ellipsis.
Advanced

You can adjust additional settings below. Odds are you don’t need to.

/ /m
A Ruby regular expression determining what is considered a diffable chunk. Defaults to . for individual characters. Use \w+ to compare whole words instead.
Pick the algorithm that generates the most semantic diff for your purposes. Myers often works best. Different algorithms sometimes produce the same results.
Please note
  • This tool is in its beta stage. Expect things to break; proceed with caution.
  • This tool isn't magic. It can only catch errors that can be determined programmatically. But quoting properly is also about accurately reflecting the meaning of the quoted content to the reader. That requires an understanding of the content, which is something this site cannot give you. Quoting properly is still your responsibility.
  • Red markings indicate that something was removed in the quote that was present in the original. Conversely, green markings indicate that something added in the quote that wasn't present in the original. Red and green markings don't necessarily error – improper additions and deletions are underlined in wavy red.
  • When no issues are found, that is NOT a guarantee that a quote is not a misquote.
  • Results are not necessarily in line with your styleguide. For example, for ellipses at the end of a sentence, preceding punctuation may or may not be omitted depending on your style guide. Given the following original...
    Tim had dinner, and he enjoyed it.
    ...the quote below will be marked as incorrect because it omits the comma:
    Tim had dinner [...].
    This quote, however, will pass with zero issues:
    Tim had dinner, [...].
    Whether punctuation can be omitted without breaking the meaning the author of the quoted text intended also depends on context and content, so you need to check yourself.
  • Depending on your styleguide, ‘swallowing’ a linebreak with an ellipsis may not be permissible, but this site does permit it.
  • Formatting, such as italics and bold text, is not yet supported. Consequently, changes in formatting cannot be detected. Use something like markdown syntax – *single asterisks for italics*, **double asterisks for bold text**, etc. – to indicate and detect changes in formatting. Pasting from other websites should convert to this syntax automatically. If your quote adds or omits emphasis, be sure to indicate that in your text (eg by saying 'emphasis added' or 'emphasis removed').