From: simon <simon@cda61777-01e9-0310-a592-d414129be87e>
Date: Tue, 13 Apr 2004 16:51:52 +0000 (+0000)
Subject: Fix the TODO comments up a bit.
X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/halibut/commitdiff_plain/a8070b46d85897508eb9059a8ff572f1a34dddf4

Fix the TODO comments up a bit.


git-svn-id: svn://svn.tartarus.org/sgt/halibut@4062 cda61777-01e9-0310-a592-d414129be87e
---

diff --git a/bk_paper.c b/bk_paper.c
index cc7e761..2ee6a2c 100644
--- a/bk_paper.c
+++ b/bk_paper.c
@@ -12,6 +12,21 @@
 /*
  * To be done:
  * 
+ *  - tune the page breaking algorithm to impose penalties on
+ *    various things
+ *     * breaking in the middle of a code paragraph
+ *     * breaking one line from the start or end of a paragraph
+ *     * breaking immediately after a heading of any kind (or
+ * 	 indeed within one)
+ *     * we may also need to impose a limit on the amount by which
+ * 	 we can _stretch_ a page; after a certain point we may
+ * 	 prefer just to unapologetically leave space at the bottom.
+ * 
+ *  - implement some simple graphics
+ *     * I had an underline below chapter headings in the original
+ * 	 Perl version, and I thought it looked rather nice
+ *     * also we need para_Rule.
+ * 
  *  - set up contents section now we know what sections begin on
  *    which pages
  * 
@@ -19,6 +34,9 @@
  * 
  *  - index
  * 
+ *  - header/footer? Page numbers at least would be handy. Fully
+ *    configurable footer can wait, though.
+ * 
  * That should bring us to the same level of functionality that
  * original-Halibut had, and the same in PDF plus the obvious
  * interactive navigation features. After that, in future work:
@@ -85,7 +103,6 @@ void *paper_pre_backend(paragraph *sourceform, keywordlist *keywords,
     int base_width = paper_width - left_margin - right_margin;
     int page_height = paper_height - top_margin - bottom_margin;
 
-    IGNORE(keywords);		       /* FIXME */
     IGNORE(idx);		       /* FIXME */
 
     /*
@@ -1027,10 +1044,7 @@ static int render_text(page_data *page, para_data *pdata, line_data *ldata,
 	  case word_IndexRef:
 	    goto nextword;
 	    /*
-	     * FIXME: we should do something with all of these!
-	     * Hyperlinks and xrefs have meaning in PDF, and this
-	     * is probably the right place to nail down the index
-	     * references too.
+	     * FIXME: we should do something with this.
 	     */
 	}