-
-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added elements helper and advanced tutorial.
- Documentation updates. - Travis fixes. - Fixes in write_html and write_xml that caused non-termination on Lwt. - Exposed strings_to_bytes.
- Loading branch information
Showing
9 changed files
with
185 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,20 @@ | ||
Error-recovering HTML and XML parsers and writers with a functional interface. | ||
Error-recovering functional HTML5 and XML parsers and writers. | ||
|
||
Markup.ml provides an HTML parser and an XML parser. The parsers are wrapped in | ||
a simple interface: they are functions that transform byte streams to parsing | ||
signal streams. Streams can be manipulated in various ways, such as processing | ||
by fold, filter, and map, assembly into DOM tree structures, or serialization | ||
back to HTML or XML. | ||
|
||
Both parsers are based on their respective standards. The HTML parser, in | ||
particular, is based on the state machines defined in HTML5. | ||
|
||
The parsers are error-recovering by default, and accept fragments. This makes it | ||
very easy to get a best-effort parse of some input. The parsers can, however, be | ||
easily configured to be strict, and to accept only full documents. | ||
|
||
Apart for this, the parsers are streaming (do not build up a document in | ||
Apart from this, the parsers are streaming (do not build up a document in | ||
memory), non-blocking (can be used with threading libraries), lazy (do not | ||
consume input unless the signal stream is being read), and process the input in | ||
a single pass. They automatically detect the character encoding of the input | ||
stream, and convert everything to UTF-8. | ||
|
||
Both parsers are based on their respective standards. The HTML parser, in | ||
particular, is based on the state machines defined in HTML5. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.