File: README.md

package info (click to toggle)
omd 1.3.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,424 kB
  • sloc: ml: 9,312; makefile: 18
file content (160 lines) | stat: -rw-r--r-- 5,172 bytes parent folder | download
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
OMD: extensible Markdown library and tool in OCaml
==================================================

OMD provides two things:

1. the command-line tool `omd`, which takes some Markdown and 
   converts it to HTML or Markdown.

   Use `omd -help` for more information on how to use it.

2. the library for OCaml contains several modules:
   - the module `Omd` contains most functions a user will need for basic
     Markdown manipulation.
   - the modules `Omd_parser`, `Omd_lexer`, `Omd_backend`, `Omd_representation` and `Omd_utils` basically implement what their names say:
     * `Omd_parser` implements the parser (the most complex part).
     * `Omd_lexer` implements a (basic) lexer.
     * `Omd_backend` implements 3 backends:
        1. HTML: default backend.
        2. Markdown: sometimes it's useful to show that 
           the fix-point is easily reachable.
        3. S-expression: it's mainly used for debugging.
     * `Omd_representation` declares the datatypes used in `Omd`. 
       It also provides some functions to work on those datatypes.
     * `Omd_utils` provides some useful tools that are not very specific
       to the OMD-specific datatypes.


OMD aims at implementing the ["original Markdown 
specs"](http://daringfireball.net/projects/markdown/syntax) with a few
Github Flavour Markdown characteristics. OMD is also meant to be more
"sane" than other Markdown parsers from the semantics point of view: if 
something bothers you from the semantics point of view, please [open an
issue on Github](https://github.com/ocaml/omd/issues).


Encoding
--------

**OMD assumes its input is US-ASCII or UTF-8 encoded.**

Dependencies
------------

OMD is implemented in OCaml, therefore it needs it to be compiled.
OCaml 4.00.1 and then 4.01.0 have been used. OMD should be compatible
with 3.12.0 as well, if it's not then please [open an
issue](https://github.com/ocaml/omd/issues).


The opam package for OMD depends on ocamlfind, which is only
used to compile and install OMD.

The root Makefile uses oasis, ocamlbuild and oasis2opam.
The Makefile in src/ only use the compilers from the standard
distribution of OCaml.

OMD, compiled as a library and/or a tool, doesn't depend on
anything other than the OCaml standard library and runtime.

----------------

Usage
-----

- to install `omd` using opam (recommended)

   `opam install omd`

- to get the development version of omd

  `git clone git://github.com/ocaml/omd.git`

- to compile `omd`
  - without `oasis` nor `ocamlbuild`

      `cd omd/src && make`

  - using `oasis` and `ocamlbuild`

      `cd omd && make`


----------------

Log
---

The recommended version numbers are typefaced in **bold**.
As new releases come out and bugs are discovered, a version can stop
being recommended.

Version numbers are trying to follow this scheme:
`x.y.z`, `z` is is for minor changes, `y` may include
algorithm, interface or editorial policy changes, 
and `x` is for deeper changes.

- 1.3.x might stop checking validity of HTML tag *names*
  and accept any XML-parsable tag name.

- **1.2.5** only fixes a single bug (an ordered list could be transformed into an unordered list)

- 1.2.4 only fixes a single bug (some spaces were wrongly handled in the HTML parsing)

- 1.2.2 and 1.2.3 fix a few issues with HTML parsing.

- 1.2.1 mainly fixes issues with HTML parsing.

- 1.2.0 introduces options `-w` and `-W`. Fixes mostly concern subtle
  uses of `\n`s in HTML and Markdown outputs.

- 1.1.2: fix: some URL-related parsing issues.

- 1.1.0 and 1.1.1: fix: some HTML-related issues.

- 1.0.1: fixes some parsing issues, improves output. (2014-10-02)

- 1.0.0: warning: this release is only partially compatible with previous versions.

- tags 1.0.0.x precede 1.0.0.
Also, tags 1.0.0.x will not be released in OPAM, next release will be 1.0.0.
And 1.0.0.x may not be compatible with each other.

- tag 1.0.0.g: accept HTML blocks which directly follow each other

- tag 1.0.0.f: fix: accept all XML-compatible attribute names for HTML attributes

- tag 1.0.0.e: fix backslash-escaping for hash-ending ATX-titles + fix Markdown output for Html_block

- tag 1.0.0.d: fix (HTML parsing) bugs introduced in 1.0.0.b and 1.0.0.c

- tag 1.0.0.c: rewrite parser of block HTML to use the updated Omd.t

- tag 1.0.0.b: rewrite parser of inline HTML to use the updated Omd.t

- tag 1.0.0.a: upgrade Omd.t for HTML representation


There will not be any newer 0.9.x release although new bugs have been
discovered. Thus it's recommended to upgrade to the latest 1.x.y.

- **0.9.7**: introduction of media:end + bug fixes

  If you need to have a version that still has
  `Tag of extension` instead of `Tag of name * extension` and don't want
  to upgrade, you may use 0.9.3

- 0.9.6: fix a bug (concerning extensions) introduced by 0.9.4.

- 0.9.5: bug fix + `Tag of extension` changed to `Tag of name * extension`

- 0.9.4: fixes a bug for the new feature

- 0.9.3: new feature `media:type="text/omd"`. 

  This version is recommended if you do not use that new feature
  and want to use 0.9.x

- 0.9.2: not released...

- older versions: cf. [commit log](https://github.com/ocaml/omd/commits/master)