Changed 'putStrLn' to 'putStr' in Main.hs, and modified some

of the readers to make spacing at end of output more consistent.
Modified tests accordingly.


git-svn-id: https://pandoc.googlecode.com/svn/trunk@201 788f1e2b-df1e-0410-8736-df70ead52e1b

1 files changed, 16 insertions, 45 deletions

diff --git a/TODO b/TODO
index 9f72a0f04..ee710a070 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,19 @@
 # TODO
 
+*   Fix bug in latex reader?  "... gets converted the wrong way.
+
+*   Use XHTML library for HTML writer?
+
 *   Revisions for building with windows under cygwin:
     Cabal under windows produces 'pandoc.exe', and some of the scripts
-    expect 'pandoc'.
+    expect 'pandoc'.  (See if this has now been fixed by Makefile change.)
+
+*   Windows binary distribution:  pandoc.exe.  Work this into the website
+    target.
+
+*   Consider allowing 'a.', 'b.', etc. to mark ordered lists.  Perhaps
+    also '(a)', '(1)', 'a)', '1)', etc., as in rst.  This does depart from
+    markdown syntax.
 
 *   Consider making section headers block titles rather than blocks.
     Instead of:  [Header 1 "My title", Block1, Block2, Block3],
@@ -10,6 +21,10 @@
     This seems cleaner and would facilitate a docbook writer.
     It might also simplify the rst reader.
 
+*   Consider merging changes in pandoc-wrappers (symlinks rather than
+    wrapper scripts, except web2markdown and markdown2pdf).  This also
+    needs documentation.
+
 *   pandoc's HTML output fails to validate completely (w3c).
     There are a few quirks:
     + HTML doesn't like the \> at the end of <meta tags.
@@ -41,47 +56,3 @@
     Disadvantage:  Perhaps slightly harder to read.  (But HTML and LaTeX
     output will still be easy to read.)
 
-*   Consider scrapping most of the wrapper scripts in favor of having
-    symlinks to pandoc.  Modify pandoc so that it changes its defaults
-    depending on the name of the calling program (getProgName).
-    This would eliminate a lot of complexity and allow better handling
-    of options (eliminating the need for a separation between wrapper
-    and pandoc options, for example).
-
-    If we do this, we should change option parsing in pandoc to allow
-    options after arguments.  This will preserve backward-compatibility
-    with the present wrapper system.  We'd also want to add an -o
-    option to pandoc (output file).  When -o foo is specified, pandoc
-    should print "Created foo" to stderr on success (unless --quiet
-    is specified).
-
-    A disadvantage is that we'd lose iconv conversion.  But maybe this
-    isn't needed anymore; UTF-8 seems to be standard on most systems now. 
-
-    The tricky wrappers to replace are markdown2pdf and html2markdown.
-
-    markdown2pdf: 
-
-        save working_directory
-        create tempdir
-        if markdown2latex "$@" >tempdir/output 2>tempdir/logfile; then
-           extract output-file from logfile (this will be foo.pdf)
-           if output-file found:
-              mv foo.pdf tempdir/foo.tex
-            else:
-              mv tempdir/output tempdir/foo.tex
-           cd tempdir
-           run pdflatex on foo.tex to produce foo.pdf
-           mv foo.pdf working_directory/foo.pdf     
-        else:
-           display logfile to inform user
-        on exit:
-           get rid of tempdir
- 
-    html2markdown:  needs to run the HTML through tidy (mainly because
-    pandoc's html parser requires closing tags, etc.)  So we probably
-    need something like the existing wrapper script here.  roktas
-    suggests perhaps keeping html2markdown simple and using a separate
-    script, web2markdown.   note:  we also need iconv here, since web
-    pages may not be in UTF8.
-