Change behavior with binary format output to stdout.

Previously, for binary formats, output to stdout was disabled
unless we could detect that the output was being piped (and not
sent to the terminal).  Unfortunately, such detection is not
possible on Windows, leaving windows users no way to pipe binary
output.  So we have changed the behavior in the following way:

* If the -o option is not used, binary output is never sent
  to stdout by default; instead, an error is raised.
* IF '-o -' is used, binary output is sent to stdout, regardless
  of whether it is being piped. This works on Windows too.

1 files changed, 4 insertions, 4 deletions

diff --git a/MANUAL.txt b/MANUAL.txt
index e2d68b86b..e106af052 100644
--- a/MANUAL.txt
+++ b/MANUAL.txt
@@ -110,8 +110,8 @@ If no *input-file* is specified, input is read from *stdin*.
 Otherwise, the *input-files* are concatenated (with a blank
 line between each) and used as input.  Output goes to *stdout* by
 default (though output to *stdout* is disabled for the `odt`, `docx`,
-`epub2`, and `epub3` output formats).  For output to a file, use the
-`-o` option:
+`epub2`, and `epub3` output formats, unless it is forced using
+`-o -`).  For output to a file, use the `-o` option:
 
     pandoc -o output.html input.txt
 
@@ -328,8 +328,8 @@ General options
 `-o` *FILE*, `--output=`*FILE*
 
 :   Write output to *FILE* instead of *stdout*.  If *FILE* is
-    `-`, output will go to *stdout*.  (Exception: if the output
-    format is `odt`, `docx`, `epub`, or `epub3`, output to stdout is disabled.)
+    `-`, output will go to *stdout*, even if a non-textual format
+    (`docx`, `odt`, `epub2`, `epub3`) is specified.
 
 `--data-dir=`*DIRECTORY*