summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Introduce \. as a NOP command. The purpose of this is to act as aSimon Tatham2004-03-25
| | | | | | | | | zero-width delimiter between a macro invocation and text beyond it, so that you can define (say) a macro which expands to a Euro sign and then write `\eur\.2500' to avoid having space between the Euro sign and the number. [originally from svn r3982]
* Obsoleted the `\preamble' command. Preamble text is now taken to beSimon Tatham2004-03-25
| | | | | | | | | | any ordinary displayable paragraph(s) appearing before the first chapter heading, meaning in particular that you can put lists, code paragraphs etc in preambles. Of course, `\preamble' is still supported for backwards compatibility, but it's now a zero-effect paragraph marker. [originally from svn r3981]
* First instalment of a manual for Halibut. This lot covers theSimon Tatham2004-03-25
| | | | | | (nearly nonexistent) invocation syntax and the input format. [originally from svn r3979]
* Add a \quote{...} directive, working like <blockquote> in HTML.Simon Tatham2004-03-25
| | | | [originally from svn r3978]
* Apparently we must include the .TH directive in a man page even whenSimon Tatham2004-03-25
| | | | | | there's nothing to go in it. [originally from svn r3977]
* Cleanups to complete the man page backend. Also, an additional newSimon Tatham2004-03-24
| | | | | | | | | | | | | markup feature: a \c line in a code paragraph can now be followed by an optional \e line indicating emphasised bits of its preceding \c. This allows discretionary bolding and (italic/underline) emphasis within code paragraphs, but without introducing an escape character or breaking any existing input files. Users are warned that not all backends are required to actually render these hints, and so they should avoid depending on them 100% to convey semantic information unless they know they're writing for a restricted range of backends. [originally from svn r3965]
* Oops, nearly forgot. Nesting one numbered list inside another shouldSimon Tatham2004-03-23
| | | | | | not break the numbering of the outer one! [originally from svn r3955]
* Man-page back end for Halibut. Also, a couple of additional markupSimon Tatham2004-03-23
| | | | | | | | | features commonly used in man pages: (a) the ability to nest paragraph breaks, code paragraphs and other lists inside list items, and (b) description lists as normally used in man pages to describe command-line options. [originally from svn r3954]
* WinHelp backend segfaults when it finds a nonexistent cross-Simon Tatham2003-01-09
| | | | | | | | reference. (The broken link will already have been reported in the mid-end, but this won't inhibit output generation, so the onus is still on us to at the very least not go *crash*.) [originally from svn r2507]
* Of course, when I start freeing things in response to valgrind'sSimon Tatham2002-09-03
| | | | | | | | complaints, it would probably help if I arranged that those things had been _allocated_ in all cases, otherwise we merely exchange a memory leak for a core dump. Duh. [originally from svn r1916]
* Just had a play with this newfangled `valgrind' memory debuggerSimon Tatham2002-08-23
| | | | | | | thingy, which seems moderately cool and has reported a few very small memory leaks. Now apparently fixed. [originally from svn r1863]
* Add configurability for section heading formats, in much the sameSimon Tatham2002-08-12
| | | | | | | | way as bk_text already does it (you can choose to have or not have the "Section" at the start, and you can configure the suffix between number and title). [originally from svn r1839]
* Add configurability for the suffix after the section number andSimon Tatham2002-08-12
| | | | | | before the section title (the ": " in "Section 1: Introduction"). [originally from svn r1838]
* Arrange for multiple \cfg, \IM and \BR paragraphs to not requireSimon Tatham2002-08-12
| | | | | | | blank-line separators (config directives visually _want_ to be in a single chunk). [originally from svn r1837]
* Fix the bug in the text back end whereby bulletted paragraphs' widthSimon Tatham2002-08-11
| | | | | | failed to be decreased to compensate for the additional indent. [originally from svn r1834]
* Add `topclean' target to the top-level Makefile, to remove theSimon Tatham2002-08-11
| | | | | | output from running Halibut on a test input file. [originally from svn r1833]
* Slightly improve the handling of headings in HTML single-file mode.Simon Tatham2002-08-11
| | | | [originally from svn r1832]
* Upgrade to Halibut xhtml backend, to allow leaf_level to be zero (inSimon Tatham2002-08-11
| | | | | | | | which case the whole of the HTML output will be in a single file, currently called Manual.html in the absence of configurability). This includes the index, if present. [originally from svn r1831]
* Rename Buttress to Halibut. I _think_ I've caught everything in this pass.Simon Tatham2002-08-05
| | | | [originally from svn r1800]
* Rename Index.html to IndexPage.html (storing Buttress output onSimon Tatham2002-03-06
| | | | | | | Windows is tricky otherwise, since Index.html clashes with index.html. Bah). [originally from svn r1575]
* xhtml-navigation-attributes config option (try {align='center'} for instance.James Aylett2002-01-29
| | | | | | | Contents entries are now, eg, "Chapter 1: Introduction" rather than just "Introduction". [originally from svn r1552]
* Buttress was dealing poorly with \r in input files (though not _too_Simon Tatham2001-12-14
| | | | | | | | poorly; mostly it just treated \r as whitespace, and the only time it actually suffered was at the end of a line in a code paragraph). Should now be fixed. [originally from svn r1492]
* Update the gratuitous hyperlink in the test document :-)Simon Tatham2001-12-14
| | | | [originally from svn r1490]
* Keywords are now collected using a B-tree rather than an array withSimon Tatham2001-12-14
| | | | | | | | heapsort. This makes the code much simpler for a start, but the main reason is so that we can spot duplicate keywords as we go along rather than having to wait until the end of input processing. [originally from svn r1489]
* Update the Buttress Jed mode for the renamed DFA functions.Simon Tatham2001-12-14
| | | | [originally from svn r1488]
* Add a LICENCE fileSimon Tatham2001-12-12
| | | | [originally from svn r1475]
* The .CNT workaround didn't work in all cases (specifically,Simon Tatham2001-12-10
| | | | | | | | | top-level leaf nodes simply can't be done, because you can't lower the level of the node to 0 to compensate for the bug because the parser rejects it). A different workaround is now in place for those cases. [originally from svn r1465]
* Allow the user to specify the Help topic ID string for particularSimon Tatham2001-12-06
| | | | | | | | | | sections. Useful if another program needs to jump to a particular topic. (Really we should support the proper CTXOMAP / HELP_WM_HELP system for doing this, but I don't like numeric IDs; you'd have to parse a bunch of #defines in order to sensibly synchronise the IDs between help file and code.) [originally from svn r1457]
* Create a .CNT contents file alongside the .HLP. (The .CNT file isSimon Tatham2001-12-06
| | | | | | | | | deliberately incorrect, to compensate for a bug in WinHelp. With any luck MS will never fix the bug and this .CNT will continue to work forever. Since WinHelp is theoretically obsolete, this sounds reasonably likely.) [originally from svn r1456]
* Remove the text-mode trappings (_emphasis_ and `code') in the indexSimon Tatham2001-12-04
| | | | | | | terms and section titles. They were unfortunately screwing up index sorting, so they had to go. [originally from svn r1455]
* Oops - missed out a set_font call which was bizarrely causingSimon Tatham2001-12-04
| | | | | | strikethrough on bullets. *boggle* [originally from svn r1454]
* In winhelp.c: allowed user to configure the Font section to theirSimon Tatham2001-12-04
| | | | | | | | | | | | | | liking, as planned. In bk_whlp.c, this has now allowed me to stop emphasis and code from looking silly in section titles, and also allowed me to implement an ersatz horizontal rule in the form of eighty centred nonbreaking spaces in a strike-through font. I know it's vile, but better suggestions are welcome. I think the Windows Help backend is now pretty much Go: I was getting intermittent screwups earlier but I think those were Samba cache persistence problems rather than evil segfaults. All that's really missing now is external context references. [originally from svn r1453]
* Bah, and update the todo at the top of the file. :-)Simon Tatham2001-12-04
| | | | [originally from svn r1452]
* *giggle* Index terms were getting processed even in the navigationSimon Tatham2001-12-04
| | | | | | menus at the bottom of help topics. Now fixed. What a cool bug :-) [originally from svn r1451]
* Indexing in the Help backend now seems to work! Woo!Simon Tatham2001-12-04
| | | | [originally from svn r1450]
* This update should bring the Windows Help back end up toSimon Tatham2001-12-04
| | | | | | | near-complete functionality. All that's missing now is indexing and horizontal rules. [originally from svn r1449]
* Well, nearly working, that is. Remember to clear all paragraphSimon Tatham2001-12-04
| | | | | | | attributes to default values right at the start of the file. We don't want the title on the very first page being 1000 pixels high! [originally from svn r1448]
* Most of a Windows Help back end now appears to work. Missing areSimon Tatham2001-12-04
| | | | | | | | | | hierarchical topic navigation (menus at the bottom of non-leaf topics, and the Up button) and index support; also I want to give users the ability to specify context IDs for particular topics. Oh, and I haven't found a plausible way to express a horizontal rule in either .RTF or .HLP format. But everything else appears to be there. [originally from svn r1447]
* Oops - replacement section types should be capitalisedSimon Tatham2001-12-04
| | | | | [originally from svn r1446] [this svn revision also touched putty]
* Fix memory management error (don't free a linked list by freeing xSimon Tatham2001-12-04
| | | | | | and _then_ setting x = x->next!). [originally from svn r1445]
* Replace Buttress's old tree23 routines with my shiny new countedSimon Tatham2001-12-04
| | | | | | tree234 routines; they will be useful in the WinHelp stuff at least. [originally from svn r1444]
* Add tabstops, and also add proper cleaning up in whlp_abandon() soSimon Tatham2001-12-04
| | | | | | | | that this module doesn't leak like a sieve with the mesh missing. I think this code is now mature enough for the Buttress back end to be written. Woo. [originally from svn r1443]
* More cleanups. In particular I've taken non-breaking spaces andSimon Tatham2001-12-03
| | | | | | | | hyphens off the todo list, because I've found out that NBS is just done using good old \xA0 (Winterhoff's analysis appears wrong) and hyphens are _all_ nonbreaking. Shame, but you can't have everything. [originally from svn r1442]
* Code cleanupSimon Tatham2001-12-03
| | | | [originally from svn r1441]
* Add indexing support. Wow, that was unexpectedly easy.Simon Tatham2001-12-03
| | | | [originally from svn r1440]
* Implement browse sequence supportSimon Tatham2001-12-03
| | | | [originally from svn r1438]
* Update the todo list at the top of the file.Simon Tatham2001-12-03
| | | | [originally from svn r1437]
* Check in the first draft of a module that writes out Windows .HLPSimon Tatham2001-12-03
| | | | | | | | | files. This is not a Buttress back end as such; it's a piece of portable, reusable code handling HLP output. I will then have to write bk_whlp.c as glue between the Buttress internal data format and the API provided by this code. [originally from svn r1436]
* Improve handling of versionids - now every HTML file contains allSimon Tatham2001-11-25
| | | | | | | | | | | versionids. I thought it might be nice to include only the versionid(s) from the .but file(s) that gave rise to a particular chapter file, but actually this is very badly defined (that information is thrown away very early on in the front end) and in any case thanks to cross-references every file _does_ depend on its fellows. Better to put them all in throughout. [originally from svn r1417]
* Introduce the ability to relabel a section as an `example' orSimon Tatham2001-11-24
| | | | | | | | | | | | | | `question' or so on, using the syntax \S{mysection}{example} An example of foobar so that in cross-references it will be referred to as `example 5.1.2' instead of `section 5.1.2'. NOTE WELL: until now Buttress has supported multiple section keywords using the same syntax, so that you could xref the above section as \k{mysection} _or_ \k{example} with the same effect. This behaviour is now revoked because I don't think anyone was using it; if you suddenly find you're getting undefined-keyword errors this may be why. [originally from svn r1408]
generated by cgit v1.1 at 2026-05-19 19:55:14 +0000