@@ -139,7 +139,7 @@ There are many, many places where things can go wrong with unicode. If you are h
139139
140140=head1 OBJECT ORIENTED INTERFACE
141141
142- Since version v0.903.0
142+ Since version v0.904.0, EXPERIMENTAL
143143
144144+++NOTE: This is incompatible with the functional interface and will treat
145145YAML values in a different way.+++
@@ -150,7 +150,7 @@ This has two MAJOR differences to the old functional interface:
150150
151151=item Object with options
152152
153- This provides an interface where you can create a YAML::XS object with
153+ This provides an interface where you create a YAML::XS object with
154154options (instead of the old interface with global variables).
155155
156156=item YAML 1.2 Core Schema
@@ -238,12 +238,12 @@ Sets the number of spaces for indentation for dumping.
238238
239239Default: false
240240
241- When false, the loader will accept utf8 decoded strings, and the dumper returns
242- utf8 decoded strings.
241+ When false, the loader will accept unencoded character strings, and the dumper
242+ returns unencoded character strings.
243243
244- When true, the loader accepts utf8 encoded strings , and the dumper returns
245- utf8 encoded strings. This typically makes sense when you read from / write
246- to a file directly.
244+ When true, the loader accepts a UTF-8 encoded string of bytes , and the dumper
245+ returns a UTF-8 encoded string of bytes.
246+ This typically makes sense when you read from / write to a file directly.
247247
248248=item header
249249
0 commit comments