Skip to content

Commit a985a0c

Browse files
committed
Update documentation for RFC 7159 support
1 parent 08b6feb commit a985a0c

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

README.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -25,13 +25,6 @@ encoded, please use the to\_json\_raw\_object method of String (which produces
2525
an object, that contains a byte array) and decode the result on the receiving
2626
endpoint.
2727

28-
The JSON parsers can parse UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, and UTF-32LE
29-
JSON documents under Ruby 1.8. Under Ruby 1.9 they take advantage of Ruby's
30-
M17n features and can parse all documents which have the correct
31-
String#encoding set. If a document string has ASCII-8BIT as an encoding the
32-
parser attempts to figure out which of the UTF encodings from above it is and
33-
trys to parse it.
34-
3528
## Installation
3629

3730
It's recommended to use the extension variant of JSON, because it's faster than
@@ -91,10 +84,6 @@ You can also use the pretty\_generate method (which formats the output more
9184
verbosely and nicely) or fast\_generate (which doesn't do any of the security
9285
checks generate performs, e. g. nesting deepness checks).
9386

94-
To create a valid JSON document you have to make sure, that the output is
95-
embedded in either a JSON array [] or a JSON object {}. The easiest way to do
96-
this, is by putting your values in a Ruby Array or Hash instance.
97-
9887
There are also the JSON and JSON[] methods which use parse on a String or
9988
generate a JSON document from an array or hash:
10089

0 commit comments

Comments
 (0)