… | |
… | |
154 | |
154 | |
155 | If C<$enable> is true (or missing), then the C<encode> method will not |
155 | If C<$enable> is true (or missing), then the C<encode> method will not |
156 | generate characters outside the code range C<0..127> (which is ASCII). Any |
156 | generate characters outside the code range C<0..127> (which is ASCII). Any |
157 | unicode characters outside that range will be escaped using either a |
157 | unicode characters outside that range will be escaped using either a |
158 | single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, |
158 | single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, |
159 | as per RFC4627. |
159 | as per RFC4627. The resulting encoded JSON text can be treated as a native |
|
|
160 | unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string, |
|
|
161 | or any other superset of ASCII. |
160 | |
162 | |
161 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
163 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
162 | characters unless required by the JSON syntax. This results in a faster |
164 | characters unless required by the JSON syntax. This results in a faster |
163 | and more compact format. |
165 | and more compact format. |
164 | |
166 | |