summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Fine-tuned the page breaking algorithm by adding penalties andSimon Tatham2004-04-13
| | | | | | | | bonuses for breaking in particular places. (For example, it's especially bad to break just after a heading, and especially good to break just before one.) [originally from svn r4064]
* I wrote the info backend _days_ ago. About time the manpage stoppedSimon Tatham2004-04-13
| | | | | | listing its absence as a bug :-) [originally from svn r4063]
* Fix the TODO comments up a bit.Simon Tatham2004-04-13
| | | | [originally from svn r4062]
* Implemented all the missing rendering features (such as differentSimon Tatham2004-04-13
| | | | | | | | font selection in headings, mentioning section numbers, bullets, list item numbers, code paragraphs etc). The PS/PDF output now actually looks like the document it's supposed to be :-) [originally from svn r4061]
* Implement PDF link annotations: both internal hyperlinks within theSimon Tatham2004-04-13
| | | | | | | document, and references to external URLs for which acroread will start a web browser. [originally from svn r4060]
* Aha, _that's_ why paragraphs weren't properly justified. ConfusionSimon Tatham2004-04-13
| | | | | | | of semantics as to whether a `last' pointer pointed to the last relevant thing in a list, or the one beyond that. Oops. [originally from svn r4059]
* Initial work on PS and PDF output. Because these two backends shareSimon Tatham2004-04-13
| | | | | | | | | | | | | | | | | | | an enormous amount of preprocessing and differ only in their final output form, I've introduced a new type of layer called a `pre-backend' (bk_paper.c is one). This takes all the information passed to a normal backend and returns an arbitrary void *, which is cached by the front end and passed on to any backend(s) which state a desire for the output of that particular pre-backend. Thus, all the page layout is done only once, and the PS and PDF backends process the same data structures into two output files. Note that these backends are _very_ unfinished; all sorts of vital things such as section numbers, list markers, and title formatting are missing, the paragraph justification doesn't quite work, and advanced stuff like indexes and PDF interactive features haven't even been started. But this basic framework generates valid output files and is a good starting point, so I'm checking it in. [originally from svn r4058]
* Yikes! Stack trash I'd never noticed before. Oops.Simon Tatham2004-04-12
| | | | [originally from svn r4056]
* Forgot to mention the info backend in the command-line help. Oops.Simon Tatham2004-04-12
| | | | [originally from svn r4055]
* Forgot to mention the info backend in the man page.Simon Tatham2004-04-10
| | | | [originally from svn r4054]
* The Emacs and Jed info readers don't like my index format: Info menuSimon Tatham2004-04-10
| | | | | | | | | | | | | | | items of the form `* stuff: Section 1.2.' are parsed by standalone info as `Section 1.2' followed by a period, but are parsed by other readers as `Section 1' followed by a period and then some spare text. Therefore, I've changed strategy, and the index is now full of *Note cross-references rather than menu items. On the plus side, this means there are no longer any special characters which we can't tolerate in an index entry; on the minus side, my shiny new infrastructure for tracking the filepos of index entries is now rendered pointless. I'll leave it in, though, since it may come in handy again. [originally from svn r4053]
* Add documentation for the info backend.Simon Tatham2004-04-10
| | | | [originally from svn r4052]
* Info backend now takes care to avoid magic characters in node namesSimon Tatham2004-04-10
| | | | | | | | | | and index terms (the Info format doesn't like them). In the course of this I've had to introduce some infrastructure for carrying a filepos forward from the definition of every RHS index term so that a particular backend can provide a usefully localised report of which index term had a problem. [originally from svn r4051]
* It would probably help to add a test of the INFO-DIR-ENTRY mechanismSimon Tatham2004-04-09
| | | | | | to the test file. Ahem. [originally from svn r4050]
* Add a config directive to generate the INFO-DIR-ENTRY things thatSimon Tatham2004-04-09
| | | | | | appear to be used to automatically construct /usr/info/dir. [originally from svn r4049]
* Why hadn't I got round to creating a .cvsignore in the main sourceSimon Tatham2004-04-09
| | | | | | directory before? Silly me. [originally from svn r4048]
* Added an info(1) backend, which constructs .info files directlySimon Tatham2004-04-09
| | | | | | | without going through the .texi source stage. A few things left to do, notably documentation, but the basics all seem to be there. [originally from svn r4047]
* Ahem; let's have all the man page headings at the same level!Simon Tatham2004-04-08
| | | | [originally from svn r4045]
* Add a horrid md5sum manifest mechanism similar to the one I used inSimon Tatham2004-04-08
| | | | | | | the Unix PuTTY archive, to automatically generate version numbers for Halibut release builds. [originally from svn r4044]
* Add installation instructions.Simon Tatham2004-04-08
| | | | [originally from svn r4043]
* Add a man page.Simon Tatham2004-04-08
| | | | [originally from svn r4042]
* Jacob pointed out various important facts missing from the HalibutSimon Tatham2004-04-04
| | | | | | manual. Added them. [originally from svn r4038]
* Limit unicode hex to 4 digitsJacob Nevins2004-04-02
| | | | [originally from svn r4036]
* Stop \n clobbering \nocite (etc)Jacob Nevins2004-04-01
| | | | | | Comments [originally from svn r4035]
* Add stuff to butCmd para so that constructs like \c don't break insideJacob Nevins2004-04-01
| | | | | | \quote{...} [originally from svn r4034]
* Restrict characters allowed in commands -- deals with "\date)."Jacob Nevins2004-04-01
| | | | | | Comments [originally from svn r4033]
* Oops, fix bracing comment stuff.Jacob Nevins2004-04-01
| | | | [originally from svn r4032]
* Inline comments respect escaped braces.Jacob Nevins2004-04-01
| | | | | | | | | Special handling for \U so that it works. Tweak \title. Make butTextArg transparent so that emphasis (e.g. in a header) shows through. Comment tweaks. [originally from svn r4031]
* typoJacob Nevins2004-04-01
| | | | [originally from svn r4030]
* GCC 3.0 doesn't like you not including <string.h> if you use things in it.James Aylett2004-04-01
| | | | | | We do, so let's. [originally from svn r4029]
* For some reason I decided it was better to say `output format'Simon Tatham2004-04-01
| | | | | | | consistently in the documentation than to confuse matters by saying `back end'. One rogue back end removed. [originally from svn r4028]
* Forgot to mention the default behaviour is to run all backends.Simon Tatham2004-04-01
| | | | [originally from svn r4027]
* Help and usage messages.Simon Tatham2004-04-01
| | | | [originally from svn r4026]
* Make the command-line --licence option do something useful.Simon Tatham2004-04-01
| | | | [originally from svn r4025]
* Having done all these command-line options and new \cfg directives,Simon Tatham2004-04-01
| | | | | | I'd better document them... [originally from svn r4024]
* Homogenise the licence, and bring it up to date.Simon Tatham2004-04-01
| | | | [originally from svn r4023]
* Now I've got a mechanism for formatting HTML file names to aSimon Tatham2004-04-01
| | | | | | | | | | parametric template, reuse the same mechanism to allow the <a name="..."> markers on each section to be parametrised as well. That way, any user who so desires can arrange for everything in a section URL to be constructed from internal keywords, making it pretty robust against section numbering changes. [originally from svn r4019]
* Arrange a mechanism whereby each backend can be passed a filenameSimon Tatham2004-04-01
| | | | | | | | | from its command-line option (`--text=foo.txt') and automatically convert it into one or more notional \cfg directives. In the HTML case this mechanism enables single-file mode as well as setting the filename. [originally from svn r4018]
* Add \cfg / -C directives to allow the user to choose the output fileSimon Tatham2004-04-01
| | | | | | name (or name schema, in HTML). [originally from svn r4017]
* Fix a couple of memory leaks in backends.Simon Tatham2004-04-01
| | | | [originally from svn r4016]
* Oops, appendices.Jacob Nevins2004-04-01
| | | | [originally from svn r4015]
* Initial revisionJacob Nevins2004-04-01
| | | | [originally from svn r4014]
* Add the -C command-line option, which allows arbitrary \cfgSimon Tatham2004-03-31
| | | | | | directives to be supplied on the Halibut command line. [originally from svn r4013]
* Make a start on command-line options. Here I introduce --text,Simon Tatham2004-03-31
| | | | | | | --html, --winhelp and --man (plus spelling variations :-), which allow you to choose to run only a subset of backends. [originally from svn r4012]
* Oops; uninitialised variable.Simon Tatham2004-03-31
| | | | [originally from svn r4011]
* After so much fuss was made about this being an _XHTML_ back endSimon Tatham2004-03-31
| | | | | | | | rather than merely HTML, I thought it might be instructive to run it through the W3C's XHTML validator. Consequent changes in this checkin... [originally from svn r4010]
* Bah, there's always one. Missing file.Simon Tatham2004-03-30
| | | | [originally from svn r4007]
* \lcont and \quote were being confused by whitespace (in particular,Simon Tatham2004-03-30
| | | | | | | | | a single newline) immediately after their opening brace; this was causing a normal paragraph to be started, thus making it fiddly and annoying to arrange the first paragraph of a \lcont to be a code para or anything else special. Now fixed. [originally from svn r4005]
* Fix index sorting so that it collates in a sensible order.Simon Tatham2004-03-30
| | | | [originally from svn r4004]
* Make \ii work!Simon Tatham2004-03-30
| | | | [originally from svn r4003]
generated by cgit v1.1 at 2026-05-25 14:41:38 +0000