Critic Markup is intended to provide basic editorial change tracking in plain text files. The syntax is compatible with Markdown, MultiMarkdown and HTML.
PanDiff is a diff generator with CriticMarkup output support.
- Critic Markup shall be human readable. A human with a simple text editor can easily read and comprehend any text containing Critic Markup.
- Critic Markup shall be computer readable except where it conflicts with rule 1. Markup syntax should be easily parsed with simple regular expressions to support a wide variety of implementations.
- Critic Markup shall be compatible with existing markup syntax for Markdown, MultiMarkdown and HTML except where it conflicts with rules one or two. Many users of plain text write in combinations of Markdown and HTML. Critic Markup should work alongside that syntax.
Critic Markup can be used in any writing environment without special applications or tool kits. While we have supplied processors and plugins that are compatible with popular apps, they are not required.
Critic Markup should be readable inline and clearly indicate the intent of the editor and author.
Critic Markup should support change tracking with multiple authors and editors through the use of comments.
Critic Markup may be used without a conversion to HTML. However, as with Markdown, HTML may be a desirable format for a more stylized presentation. We have several recommendations for how Critic Markup may be converted to HTML. The intent is to allow the HTML to be used without custom CSS. However, custom CSS may be used to enhance the review process.
There are five types of Critic marks:
- Addition
{++ ++} - Deletion
{-- --} - Substitution
{~~ ~> ~~} - Comment
{>> <<} - Highlight
{== ==}{>> <<}
Using these five basic marks you can successfully copy edit in plain text.
Additions are inserted inline by surrounding the desired text with curly braces and double plus marks as shown:
Lorem ipsum dolor{++ sit++} amet...
A space character and "sit" are to be added at the position of the left (or right) most curly brace. The additions may be rendered as <ins> tags in the processed HTML:
Lorem ipsum dolor<ins> sit<ins> amet…
Paragraphs may be inserted in the same manner.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
Mauris massa sem, tempor sed cursus et, semper tincidunt lacus.{++
++}Praesent sagittis, quam id egestas consequat, nisl orci vehicula libero,
quis ultricies nulla magna interdum sem. Maecenas eget orci vitae eros
accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet vitae tellus.
Sed neque justo, cursus in commodo eget, facilisis eget nunc. Cras
tincidunt auctor varius.
To ensure the Markdown processor outputs valid HTML, the <ins> tag encloses a non-breaking space and is followed by two newlines. The result is that both paragraphs render separately. The non-breaking-space gives the tag enough content to render properly, and we assign class=break to allow for custom styling.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
Mauris massa sem, tempor sed cursus et, semper tincidunt lacus.
<ins class=”break”> </ins>
Praesent sagittis, quam id egestas consequat, nisl orci vehicula libero,
quis ultricies nulla magna interdum sem. Maecenas eget orci vitae eros
accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet vitae tellus. Sed
neque justo, cursus in commodo eget, facilisis eget nunc. Cras tincidunt
auctor varius.
Rules for proper use of the <ins> element can be found in the HTML 4 spec.
Deletions are denoted with a similar syntax. The text to be deleted is surrounded with curly braces and double hyphens.
Lorem{‐‐ ipsum‐‐} dolor sit amet…
The word "ipsum" and a space character are marked for deletion in the above example. These deletions are rendered as <del> tags in the processed HTML.
Lorem<del> ipsum</del> dolor sit amet…
Paragraphs may also be deleted.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
Mauris massa sem, tempor sed cursus et, semper tincidunt lacus.{‐‐
‐‐}Praesent sagittis, quam id egestas consequat, nisl orci vehicula libero,
quis ultricies nulla magna interdum sem. Maecenas eget orci vitae eros
accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet vitae tellus.
Sed neque justo, cursus in commodo eget, facilisis eget nunc. Cras
tincidunt auctor varius.
The newlines will be removed by the processor and replaced by an inline <del> tag. Again, the non-breaking-space gives the tag enough content to render properly.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
Mauris massa sem, tempor sed cursus et, semper tincidunt lacus.
<del> </del> Praesent sagittis, quam id egestas consequat, nisl
orci vehicula libero, quis ultricies nulla magna interdum sem. Maecenas eget
orci vitae eros accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet
vitae tellus. Sed neque justo, cursus in commodo eget, facilisis eget nunc.
Cras tincidunt auctor varius.
Rules for proper use of the <del> element can be found in the HTML 4 spec.
Substitutions combine a delete with an insert in one snippet, and are written as curly braces and double tildes. A squiggly arrow made up of a tilde and greater-than symbol separates the old and new text. The characters to be deleted always occur to the left of the squiggly arrow.
Lorem {~~hipsum~>ipsum~~} dolor sit amet…
Despite the unique syntax, substitutions should render as a deletion followed by an insertion.
Lorem <del>hipsum</del><ins>ipsum</ins> dolor sit amet…
Newlines are treated the same as a deletion or insertion, depending on where they're located.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
{~~Mauris massa sem, tempor sed cursus et, semper tincidunt lacus.~>
~~}Praesent sagittis, quam id egestas consequat, nisl orci vehicula libero,
quis ultricies nulla magna interdum sem. Maecenas eget orci vitae eros
accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet vitae tellus.
Sed neque justo, cursus in commodo eget, facilisis eget nunc. Cras
tincidunt auctor varius.
After rendering this example, the deletion and insertion are added to the end of the first paragraph and two newlines ensure the proper paragraph break.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum at orci
magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget nulla.
<del>Mauris massa sem, tempor sed cursus et, semper tincidunt
lacus.</del><ins class=”break”> </ins>
Praesent sagittis, quam id egestas consequat, nisl orci vehicula libero,
quis ultricies nulla magna interdum sem. Maecenas eget orci vitae eros
accumsan mollis. Cras mi mi, rutrum id aliquam in, aliquet vitae tellus. Sed
neque justo, cursus in commodo eget, facilisis eget nunc. Cras tincidunt
auctor varius.
Critic Markup supports generic comments for metadata. A comment may include a note, time stamp, author initial or similar annotation.
Comments are added via a set of curly braces and double greater-than/less-than symbols.
Lorem ipsum dolor sit amet.{>>This is a comment<<}
The contents of a metadata field should render as <span class="critic comment"> after the relevant change.
Lorem ipsum dolor sit amet.<span class=”critic comment”>This is a comment</span>
Metadata may be used however you like, whether as explanations for the changes, time stamps or more. The <span> element is for inline content only, so all newlines will be stripped during conversion to HTML.
Rules for proper use of the <span> element can be found in the HTML 4 spec.
Highlights may be added as required by an editor or author, and are noted by curly braces and double equal signs. While a highlight can be used on it's own, we recommend that it always be followed by a comment related to the highlighted passage.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. {==Vestibulum at
orci magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget
nulla.==}{>>confusing<<} Mauris massa sem, tempor sed cursus et, semper
tincidunt lacus.
Highlights should be rendered as <mark> tags in the processed HTML.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. <mark>Vestibulum at
orci magna. Phasellus augue justo, sodales eu pulvinar ac, vulputate eget
nulla.</mark><span class=”critic metadata”>confusing</span> Mauris massa
sem, tempor sed cursus et, semper tincidunt lacus.
Rules for proper use of the <mark> element can be found in the HTML 5 spec.
When used in combination the marks can indicate more complex changes.
Don’t go around saying{‐‐ to people that‐‐} the world owes you a living. The
world owes you nothing. It was here first. {~~One~>Only one~~} thing is
impossible for God: To find {++any++} sense in any copyright law on the
planet. {==Truth is stranger than fiction==}{>>true<<}, but it is because
Fiction is obliged to stick to possibilities; Truth isn’t.
The above paragraphs should render to HTML in the following manner.
Don’t go around saying<del> to people that</del> the world owes you a
living. The world owes you nothing. It was here first.
<del>One</del><ins>Only one</ins> thing is impossible for God: To find
<ins>any</ins> sense in any copyright law on the planet. <mark>Truth is
stranger than fiction</mark><span class=”critic comment”>true</span>, but it
is because Fiction is obliged to stick to possibilities; Truth isn’t.
There are a few limitations to consider when using CriticMarkup.
Newlines should be avoided as much as possible within CriticMarkup tags. Many of the HTML elements we use are inline elements only. While we've crafted CriticMarkup with as much care as possible, it is possible for you to break the syntax and output invalid HTML if you try hard enough.
While it may support incomplete Markdown tags in the future, the CriticMarkup processor currently chokes on them. Avoid this:
I really love *italic {~~fonts*~>font-styles*~~}.
Instead, wrap the asterisks completely:
I really love {~~*italic fonts*~>*italic font-styles*~~}.
Copyright 2013 Gabe Weatherhead and Erik Hess
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.