From edfc965fec0e6f3fec54c9a9db84582207e77713 Mon Sep 17 00:00:00 2001 From: Markus Unterwaditzer Date: Sun, 28 Nov 2021 00:08:03 +0100 Subject: update wording again --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c6b18a0..ab664f8 100644 --- a/README.md +++ b/README.md @@ -34,10 +34,10 @@ It fully implements [13.2.5 of the WHATWG HTML spec](https://html.spec.whatwg.org/#tokenization), i.e. is able to tokenize HTML documents and passes [html5lib's tokenizer test suite](https://github.com/html5lib/html5lib-tests/tree/master/tokenizer), with the following exceptions: -* [Implement charset detection.](https://html.spec.whatwg.org/#determining-the-character-encoding) This implementation requires all input to be +* html5gum **does not** [implement charset detection.](https://html.spec.whatwg.org/#determining-the-character-encoding) This implementation requires all input to be Rust strings and therefore valid UTF-8. -* [Correct mis-nested tags](https://html.spec.whatwg.org/#an-introduction-to-error-handling-and-strange-cases-in-the-parser) -* Generally qualify as a complete HTML *parser* as per the WHATWG spec (yet). +* html5gum **does not** [correct mis-nested tags](https://html.spec.whatwg.org/#an-introduction-to-error-handling-and-strange-cases-in-the-parser) +* html5gum **does not** generally qualify as a browser-grade HTML *parser* as per the WHATWG spec. This can change in the future. A distinguishing feature of `html5gum` is that you can bring your own token datastructure and hook into token creation by implementing the `Emitter` trait. -- cgit v1.2.3