From c478f3d9469c09773097eba89342c311ee70a319 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Mon, 5 Aug 2002 10:31:35 +0000 Subject: Rename Buttress to Halibut. I _think_ I've caught everything in this pass. [originally from svn r1800] --- bk_xhtml.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'bk_xhtml.c') diff --git a/bk_xhtml.c b/bk_xhtml.c index 0005f6b..2016e10 100644 --- a/bk_xhtml.c +++ b/bk_xhtml.c @@ -1,5 +1,5 @@ /* - * xhtml backend for Buttress + * xhtml backend for Halibut * (initial implementation by James Aylett) * * Still to do: @@ -23,13 +23,13 @@ * top-level file not being normal, probably not even having a valid * section level, and stuff like that. I question whether this is an * issue, frankly; small manuals that fit on one page should probably - * not be written in buttress at all. + * not be written in halibut at all. */ #include #include #include -#include "buttress.h" +#include "halibut.h" struct xhtmlsection_Struct { struct xhtmlsection_Struct *next; /* next sibling (NULL if split across files) */ @@ -328,7 +328,7 @@ void xhtml_fixup_layout(xhtmlfile* file) * Note that you _can_ have 1.1.1.1 followed by 1.2 - you can change * more than one level at a time. Lots of asserts, and probably part of * the algorithm here, rely on this being true. (It currently isn't - * enforced by buttress, however.) + * enforced by halibut, however.) * * File splitting makes this harder. For instance, say we added at (3) * above and now need to add another section. We are splitting at level @@ -1098,7 +1098,7 @@ static void xhtml_doheader(FILE *fp, word *title) else xhtml_para(fp, title); fprintf(fp, "\n"); - fprintf(fp, "\n", version); + fprintf(fp, "\n", version); if (conf.author) fprintf(fp, "\n", conf.author); if (conf.description) -- cgit v1.1