1 files changed, 1 insertions, 1 deletions

diff --git a/params.json b/params.json
index b122d13..7d7583f 100644
--- a/params.json
+++ b/params.json
@@ -1 +1 @@
-{"name":"QWebSockets","tagline":"QWebSockets is a pure Qt implementation of WebSockets - both client and server.","body":"### Introduction\r\nQWebSockets is a pure Qt implementation of WebSockets - both client and server.\r\nIt is implemented as a Qt source code module (.pri file), that can easily be embedded into existing Qt projects. It has no other dependencies that Qt.\r\n\r\n### Features\r\n* Text and binary sockets\r\n* Frame-based and message-based signals\r\n* Works through proxies\r\n* Strict Unicode checking\r\n\r\n### Restrictions\r\nNon-characters (according [Unicode Standard 6.2](http://www.unicode.org/versions/Unicode6.2.0/)) are rejected by QWebSockets, **even if the UTF-8 sequence is valid**.  \r\n##### Rationale\r\nThe WebSocket specification is talking about _Valid UTF-8 codes and sequences_. Strictly speaking, UTF-xx encodings are reversible. That means, that the [66 non-character codes](http://www.unicode.org/faq/private_use.html#noncharacters) (including `U+FFFE` and `U+FFFF`), are valid UTF-8, and hence are perfectly acceptable within WebSocket text messages.  \r\nAccording to the Unicode standard, they SHOULD NOT be used in information interchange, but a [recent corrigendum](http://www.unicode.org/versions/corrigendum9.html) clarifies that non-characters CAN be exchanged.  \r\nHowever, non-characters are for internal use, and hence, they are implementation specific (e.g. non-characters can be used to carry meta-information). _They have to be interpreted._  \r\nWhen used with `QString`, they are replaced with `U+FFFD - REPLACEMENT CHARACTER`, and rendered - non-standard - as a question mark (this is the `QString` rendering of the non-character `U+FFFD`: �). Browsers keep the control characters untouched (this is the browser rendering of the non-character `U+FDD0`: ).  \r\n  \r\nWith QWebSockets, text messages are just that: a collection of human-readable characters. Text messages never have to be interpreted to be rendered correctly. In case, you still want to do implementation specific trickery, use binary messages instead. Indeed, if non-characters were allowed in text messages, then every text message has to be parsed, character-per-character, to find out if it contains special control codes, or a protocol should be devised that indicates whether the message contains that kind of control codes. We keep it simple: text is text and nothing more.\r\n\r\n### Requirements\r\nQt 5.x\r\n\r\n### Compliance\r\nQWebSockets is compliant with [RFC6455](http://datatracker.ietf.org/doc/rfc6455/?include_text=1) and has been tested with the [Autobahn Testsuite](http://autobahn.ws/testsuite).  \r\nOnly tests with **invalid Unicode code points** do **not** pass from the Autobahn Testsuite (see [Restrictions](#Restrictions)). \r\n\r\n### Missing Features\r\n* WSS protocol\r\n* Extensions and sub-protocols\r\n\r\n### License\r\nThis code is licensed under LGPL v3.","google":"UA-43042417-1","note":"Don't delete this file! It's used internally to help with page regeneration."}
\ No newline at end of file
+{"name":"QWebSockets","tagline":"QWebSockets is a pure Qt implementation of WebSockets - both client and server.","body":"### Introduction\r\nQWebSockets is a pure Qt implementation of WebSockets - both client and server.\r\nIt is implemented as a Qt source code module (.pri file), that can easily be embedded into existing Qt projects. It has no other dependencies that Qt.\r\n\r\n### Features\r\n* Text and binary sockets\r\n* Frame-based and message-based signals\r\n* Works through proxies\r\n* Strict Unicode checking\r\n\r\n### Restrictions\r\nNon-characters (according [Unicode Standard 6.2](http://www.unicode.org/versions/Unicode6.2.0/)) are rejected by QWebSockets, **even if the UTF-8 sequence is valid**.  \r\n##### Rationale\r\nThe WebSocket specification is talking about _Valid UTF-8 codes and sequences_. Strictly speaking, UTF-xx encodings are reversible. That means, that the [66 non-character codes](http://www.unicode.org/faq/private_use.html#noncharacters) (including `U+FFFE` and `U+FFFF`), are valid UTF-8, and hence are perfectly acceptable within WebSocket text messages.  \r\nAccording to the Unicode standard, they SHOULD NOT be used in information interchange, but a [recent corrigendum](http://www.unicode.org/versions/corrigendum9.html) clarifies that non-characters CAN be exchanged.  \r\nHowever, non-characters are for internal use, and hence, they are implementation specific (e.g. non-characters can be used to carry meta-information). _They have to be interpreted._  \r\nWhen used with `QString`, they are replaced with `U+FFFD - REPLACEMENT CHARACTER`, and rendered - non-standard - as a question mark (this is the `QString` rendering of the non-character `U+FFFD`: �). Browsers keep the control characters untouched (this is the browser rendering of the non-character `U+FDD0`: ).  \r\n  \r\nWith QWebSockets, text messages are just that: a collection of human-readable characters. Text messages never have to be interpreted to be rendered correctly. In case, you still want to do implementation specific trickery, use binary messages instead. Indeed, if non-characters were allowed in text messages, then every text message has to be parsed, character-per-character, to find out if it contains special control codes, or a protocol should be devised that indicates whether the message contains that kind of control codes. We keep it simple: text is text and nothing more.\r\n\r\n### Requirements\r\nQt 5.x\r\n\r\n### Compliance\r\nQWebSockets is compliant with [RFC6455](http://datatracker.ietf.org/doc/rfc6455/?include_text=1) and has been tested with the [Autobahn Testsuite](http://autobahn.ws/testsuite).  \r\nOnly tests with **invalid Unicode code points** do **not** pass from the Autobahn Testsuite (see [Restrictions](#Restrictions)). \r\n\r\n### Missing Features\r\n* WSS protocol\r\n* Extensions and sub-protocols\r\n\r\n### License\r\nThis code is licensed under LGPL v2.1.","google":"UA-43042417-1","note":"Don't delete this file! It's used internally to help with page regeneration."}
\ No newline at end of file