Changes between Version 3 and Version 4 of MarkupStream

Timestamp:

Jul 27, 2006, 10:23:15 AM (18 years ago)

Author:

cmlenz

Comment:

--

MarkupStream

@@ -66 +66 @@
 }}}
 
-Both methods can be passed a `method` parameter that determines how exactly the events are serialzed to text. This parameter can be either “xml” (the default) or “html”, or a subclass of the `markup.output.Serializer` class:
+Both methods can be passed a `method` parameter that determines how exactly the events are serialzed to text. This parameter can be either “xml” (the default), “xhtml”, “html”, or a subclass of the `markup.output.Serializer` class:
 
 {{{
@@ -89 +89 @@
 }}}
 
-Often, streams cannot be reused: in the above example, the sub-stream is based on a generator. Once it has been serialized, it will have been fully consumed, and cannot be rendered again. To work around this, you can wrap such a “read-once” stream in a `list`:
+Often, streams cannot be reused: in the above example, the sub-stream is based on a generator. Once it has been serialized, it will have been fully consumed, and cannot be rendered again. To work around this, you can wrap such a  stream in a `list`:
 
 {{{