kc3-lang/md4c/README.md
MD4C Readme
Home: http://github.com/mity/md4c
MD4C stands for “MarkDown for C” and, unsurprisingly, it is a C Markdown parser implementation.
Warning: This project is very young (read “immature”) and work in progress. Most important features are not yet implemented. See the current status below. And there may be bugs.
What is Markdown
In short, Markdown is the markup language this README.md file is written in.
The following resources can explain more if you are unfamiliar with it:
What is MD4C
Main features:
- Compactness: MD4C is implemented in one source file and one header file.
- Flexibility: Flags allow to tune the desired dialect of the Markdown parser.
- Encoding agnosticism: As much as possible, MD4C by design does not care about input text encoding, relying only on the Markdown control characters being ASCII compatible. (The actual text data are propagated back to the caller in the same encoding unchanged.)
-
UTF-16LE support: On Windows, MD4C may be built to consume (and produce)
wide strings (
WCHAR*instead ofchar*). - Easily embeddable: MD4C depends only on few functions of C standard library.
- Portability: MD4C builds and works on Windows and Linux, and it should be fairly trivial to build it also on other systems.
- Permissive license: MD4C is available under the MIT license.
Using MD4C
The parser is implemented in a single C source file md4c.c and its
accompanying header md4c.h.
The main provided function is md_parse(). It takes a text in Markdown syntax
as an input and a renderer structure which holds pointers to few callback
functions. As md_parse() eats the input, it calls appropriate callbacks
allowing application to convert it into another format or render it onto
the screen.
Refer to the header file for more details, the API is mostly self-explaining and there are some explanatory comments.
Example implementation of simple renderer is available in the md2html
directory which implements a conversion utility from Markdown to HTML.
Current Status
CommonMark Specification
The goal is to become compliant to the latest version of CommonMark specification.
The list below corresponds to chapters of the specification version 0.27 and more or less forms our to do list.
-
Preliminaries:
- [x] 2.1 Character and lines
- [x] 2.2 Tabs
- [x] 2.3 Insecure characters
-
Blocks and Inlines:
- [x] 3.1 Precedence
- [x] 3.2 Container blocks and leaf blocks
-
Leaf Blocks:
- [x] 4.1 Thematic breaks
- [x] 4.2 ATX headings
- [x] 4.3 Setext headings
- [x] 4.4 Indented code blocks
- [x] 4.5 Fenced code blocks
- [x] 4.6 HTML blocks
- [x] 4.7 Link reference definitions
- [x] 4.8 Paragraphs
- [x] 4.9 Blank lines
-
Container Blocks:
- [x] 5.1 Block quotes
- [x] 5.2 List items
- [x] 5.3 Lists
-
Inlines:
- [x] 6.1 Backslash escapes
- [x] 6.2 Entity and numeric character references
- [x] 6.3 Code spans
- [x] 6.4 Emphasis and strong emphasis
- [x] 6.5 Links
- [x] 6.6 Images
- [x] 6.7 Autolinks
- [x] 6.8 Raw HTML
- [x] 6.9 Hard line breaks
- [x] 6.10 Soft line breaks
- [x] 6.11 Textual content
Considered Extensions
Aside of CommonMark features, various Markdown implementations out there support various extensions and/or some deviations from the CommonMark specification which may be found desired or useful in some situations.
Therefore some extensions or deviations from the CommonMark specification may be considered and implemented. However, such extensions and deviations from the standard shall be enabled only if explicitly enabled by the application.
Default behavior shall stick to the CommonMark specification.
The list below is incomplete list of extensions I see as worth of consideration.
-
Block Extensions:
- [x] Tables
-
[ ] Header anchors:
## Chapter {#anchor}(allowing fragment links pointing to it, e.g.[link text](#anchor))
-
Inline Extensions:
-
[ ] Underline:
__foo bar__ -
[ ] Strikethrough:
~~foo bar~~ -
[ ] Highlight:
==foo bar== -
[ ] Quote:
"foo bar" -
[ ] Superscript:
a^2^ + b^2^ = c^2^ -
[ ] Subscript:
matrix A~i,j~
-
[ ] Underline:
-
Miscellaneous:
-
[x] Permissive ATX headers:
###Header(without space) -
[x] Permissive URL autolinks:
http://google.com(without<…>) -
[x] Permissive e-mail autolinks:
john.doe@example.com(without `<`...`>` and `mailto:`) - [x] Disabling indented code blocks
- [x] Disabling raw HTML blocks/spans
-
[x] Permissive ATX headers:
License
MD4C is covered with MIT license, see the file LICENSE.md.
Reporting Bugs
If you encounter any bug, please be so kind and report it. Unheard bugs cannot get fixed. You can submit bug reports here:
Source
-
README.md
-
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160
[](https://travis-ci.org/mity/md4c) [](https://ci.appveyor.com/project/mity/md4c/branch/master) [](https://scan.coverity.com/projects/mity-md4c) [](https://coveralls.io/github/mity/md4c) # MD4C Readme Home: http://github.com/mity/md4c MD4C stands for "MarkDown for C" and, unsurprisingly, it is a C Markdown parser implementation. **Warning:** This project is very young (read "immature") and work in progress. Most important features are not yet implemented. See the current status below. And there may be bugs. ## What is Markdown In short, Markdown is the markup language this `README.md` file is written in. The following resources can explain more if you are unfamiliar with it: * [Wikipedia article](http://en.wikipedia.org/wiki/Markdown) * [CommonMark site](http://commonmark.org) ## What is MD4C Main features: * **Compactness:** MD4C is implemented in one source file and one header file. * **Flexibility:** Flags allow to tune the desired dialect of the Markdown parser. * **Encoding agnosticism:** As much as possible, MD4C by design does not care about input text encoding, relying only on the Markdown control characters being ASCII compatible. (The actual text data are propagated back to the caller in the same encoding unchanged.) * **UTF-16LE support:** On Windows, MD4C may be built to consume (and produce) wide strings (`WCHAR*` instead of `char*`). * **Easily embeddable:** MD4C depends only on few functions of C standard library. * **Portability:** MD4C builds and works on Windows and Linux, and it should be fairly trivial to build it also on other systems. * **Permissive license:** MD4C is available under the MIT license. ## Using MD4C The parser is implemented in a single C source file `md4c.c` and its accompanying header `md4c.h`. The main provided function is `md_parse()`. It takes a text in Markdown syntax as an input and a renderer structure which holds pointers to few callback functions. As `md_parse()` eats the input, it calls appropriate callbacks allowing application to convert it into another format or render it onto the screen. Refer to the header file for more details, the API is mostly self-explaining and there are some explanatory comments. Example implementation of simple renderer is available in the `md2html` directory which implements a conversion utility from Markdown to HTML. ## Current Status ### CommonMark Specification The goal is to become compliant to the latest version of [CommonMark specification](http://spec.commonmark.org/). The list below corresponds to chapters of the specification version 0.27 and more or less forms our to do list. - **Preliminaries:** - [x] 2.1 Character and lines - [x] 2.2 Tabs - [x] 2.3 Insecure characters - **Blocks and Inlines:** - [x] 3.1 Precedence - [x] 3.2 Container blocks and leaf blocks - **Leaf Blocks:** - [x] 4.1 Thematic breaks - [x] 4.2 ATX headings - [x] 4.3 Setext headings - [x] 4.4 Indented code blocks - [x] 4.5 Fenced code blocks - [x] 4.6 HTML blocks - [x] 4.7 Link reference definitions - [x] 4.8 Paragraphs - [x] 4.9 Blank lines - **Container Blocks:** - [x] 5.1 Block quotes - [x] 5.2 List items - [x] 5.3 Lists - **Inlines:** - [x] 6.1 Backslash escapes - [x] 6.2 Entity and numeric character references - [x] 6.3 Code spans - [x] 6.4 Emphasis and strong emphasis - [x] 6.5 Links - [x] 6.6 Images - [x] 6.7 Autolinks - [x] 6.8 Raw HTML - [x] 6.9 Hard line breaks - [x] 6.10 Soft line breaks - [x] 6.11 Textual content ### Considered Extensions Aside of CommonMark features, various Markdown implementations out there support various extensions and/or some deviations from the CommonMark specification which may be found desired or useful in some situations. Therefore some extensions or deviations from the CommonMark specification may be considered and implemented. However, such extensions and deviations from the standard shall be enabled only if explicitly enabled by the application. Default behavior shall stick to the CommonMark specification. The list below is incomplete list of extensions I see as worth of consideration. - **Block Extensions:** - [x] Tables - [ ] Header anchors: `## Chapter {#anchor}` (allowing fragment links pointing to it, e.g. `[link text](#anchor)`) - **Inline Extensions:** - [ ] Underline: `__foo bar__` - [ ] Strikethrough: `~~foo bar~~` - [ ] Highlight: `==foo bar==` - [ ] Quote: `"foo bar"` - [ ] Superscript: `a^2^ + b^2^ = c^2^` - [ ] Subscript: `matrix A~i,j~` - **Miscellaneous:** - [x] Permissive ATX headers: `###Header` (without space) - [x] Permissive URL autolinks: `http://google.com` (without `<`...`>`) - [x] Permissive e-mail autolinks: `john.doe@example.com` (without `<`...`>` and `mailto:`) - [x] Disabling indented code blocks - [x] Disabling raw HTML blocks/spans ## License MD4C is covered with MIT license, see the file `LICENSE.md`. ## Reporting Bugs If you encounter any bug, please be so kind and report it. Unheard bugs cannot get fixed. You can submit bug reports here: * http://github.com/mity/md4c/issues