summaryrefslogtreecommitdiff
path: root/doc (follow)
Commit message (Collapse)AuthorAge
* Remove a \#{FIXME} comment in \cfg{paper-chapter-top-space}; the checkinJacob Nevins2004-08-09
| | | | | | | of bk_paper.c 1.29 [r4330] appears to have fixed this. [originally from svn r4432] [r4330 == 8aac8532019ac6cee701d48ceb35473280219a0e]
* Explicitly bless in the documentation, and fix in the man backend,Simon Tatham2004-08-06
| | | | | | | the practice of using \dt and \dd in anything other than the obvious interleaving. [originally from svn r4417]
* Right; I'm finally sick of typing \q{\cw{foo}}, so I've invented aSimon Tatham2004-07-16
| | | | | | shorthand command \cq{foo}. [originally from svn r4327]
* Minimal documentation of all the new paper backend \cfg{} directives.Jacob Nevins2004-06-20
| | | | | | | | | Contains many FIXMEs, both for incomplete documentation and incomplete code. Couple of other minor tweaks elsewhere. [originally from svn r4304]
* We seem to have ended up with duplicate documentation of --man. Gone.Jacob Nevins2004-06-19
| | | | [originally from svn r4303]
* Ensure that every \cfg{} directive documented so far has appropriate \IMJacob Nevins2004-06-19
| | | | | | directives. [originally from svn r4302]
* Fairly wholesale reorganisation of the \cfg{} documentation for the text,Jacob Nevins2004-06-19
| | | | | | | | WinHelp, man, and info backends, and organisation into sections (now that we have rather more directives documented). I've not changed the actual text much if at all. [originally from svn r4301]
* In the text backend, multiple characters can now be used for underlining.Jacob Nevins2004-06-19
| | | | [originally from svn r4300]
* The Unicode OVERLINE in the text backend documentation was probably supposedJacob Nevins2004-06-19
| | | | | | to be quoted. [originally from svn r4299]
* Note that \cfg{quotes} and friends apply to the output in its entirety andJacob Nevins2004-06-19
| | | | | | can't be changed partway through. Also, add a cross-reference from \q{}. [originally from svn r4298]
* Note that no index is generated by the text backend.Jacob Nevins2004-06-19
| | | | [originally from svn r4297]
* Minor correction to --ps and --pdf descriptions.Jacob Nevins2004-06-19
| | | | [originally from svn r4296]
* Initial rough documentation of some of the newer \cfg{} directives, namely:Jacob Nevins2004-06-19
| | | | | | | | | | | | - \cfg{quotes} - text, info, man, and winhelp backends: - charset - quotes and bullets - various WinHelp miscellanea Could stand some rearrangement and expansion, plus I've yet to address the paper or HTML backends. [originally from svn r4295]
* The Halibut manual contained at least one instance of two indexSimon Tatham2004-06-13
| | | | | | | | | | | | | | terms (intentionally) differing only in case, which were being silently folded into one by the case-insensitive index tag comparison. Halibut now warns in this situation (but then folds them anyway, which I think is better than silently generating an index containing many case-distinct forms of the same word - I imagine it's very easy to do that by mistake). The manual has been fixed to explicitly define distinct keywords (in the case I spotted and in five other cases picked up by the new warning!), and also documents this issue and how to work with it. [originally from svn r4279]
* Er, don't forget to document the disallowing of \q within \c. Ahem.Simon Tatham2004-06-12
| | | | [originally from svn r4278]
* Initial checkin of the shiny new rewritten-from-scratch HTML backSimon Tatham2004-06-12
| | | | | | | | | | | | | | | | | | end. There's a lot more _potentiality_ for new features than there are actual new features just yet, but future highlights include: configurable flavour of HTML (3.2, 4, XHTML Transitional or Strict), proper character set support (this is half way there already), and more flexible allocation of sections between multiple HTML files. Meanwhile, immediate benefits include correct handling of special characters within `author' and `description' strings, omission of the filename part in hyperlinks within the same HTML file (in particular, this means a single output file is now totally independent of its filename), and hyperlinks to the index from the top-level contents page (I'm amazed nobody has complained at the lack of this yet!). There are no doubt some shiny new bugs as well, but I'll never find them unless people start using the thing... [originally from svn r4275]
* rjk's `make install' patch.Simon Tatham2004-06-02
| | | | [originally from svn r4267]
* General configurability upgrade for the info back end.Simon Tatham2004-04-23
| | | | [originally from svn r4131]
* Oh, and now the text backend warns about too-long code lines, I'dSimon Tatham2004-04-23
| | | | | | better remove the one too-long code line in the manual :-) [originally from svn r4129]
* Enhance the text backend to support configurable quote characters,Simon Tatham2004-04-23
| | | | | | | | | | | configurable emphasis characters, various other configurable bits which have been marked FIXME in the code for a while, and also to warn when a code paragraph line is too long (because that was the only other thing labelled FIXME). Fallback options are implemented, and defaults set accordingly. A UTF-8 text output file now looks like proper UTF-8. [originally from svn r4128]
* Don't forget to mention the default setting for \cfg{input-charset}.Simon Tatham2004-04-20
| | | | [originally from svn r4106]
* Forgot to add *.ps and *.pdf to the `make clean' list!Simon Tatham2004-04-20
| | | | [originally from svn r4098]
* Support for \cfg{input-charset}. Input files can now be in ASCII,Simon Tatham2004-04-19
| | | | | | | 8859-*, UTF-8, or a variety of more fun encodings including various multibyte ones. [originally from svn r4095]
* Support the \W{...}\i\c{...} combination used in the NASM manual.Simon Tatham2004-04-15
| | | | | | | | Halibut is now capable of reading the old NASM manual with only minor modifications, and probably doing a much better job of formatting it than rdsrc.pl ever did. (Certainly much _faster_!) [originally from svn r4081]
* Administrivia: update a TODO and a .cvsignore.Simon Tatham2004-04-14
| | | | [originally from svn r4077]
* After printing out the PDF manual and reading it through, here's aSimon Tatham2004-04-14
| | | | | | | | collection of minor edits for clarity, and also quite a few intended to keep down the length of lines in code paragraphs (because Courier is not just a thoroughly ugly font but is also WAY TOO WIDE). [originally from svn r4076]
* ... oh, except that minimal documentation might be helpful.Simon Tatham2004-04-14
| | | | [originally from svn r4075]
* 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]
* Forgot to mention the info backend in the man page.Simon Tatham2004-04-10
| | | | [originally from svn r4054]
* Add documentation for the info backend.Simon Tatham2004-04-10
| | | | [originally from svn r4052]
* 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]
* 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 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]
* 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]
* 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]
* Bah, there's always one. Missing file.Simon Tatham2004-03-30
| | | | [originally from svn r4007]
* Simplify treatment of the copyright notice, now I've also simplifiedSimon Tatham2004-03-30
| | | | | | | | | the preamble: \copyright paragraphs are now treated identically to normal paragraphs (so they appear precisely where they're put instead of in a fixed location), _except_ that the Windows Help backend also copies their text into the help file's copyright slot. [originally from svn r4001]
* I always meant to remove emphasis in the index by default. Now I doSimon Tatham2004-03-30
| | | | | | so. It's restorable using \IM. [originally from svn r4000]
* The manual is now fully indexed.Simon Tatham2004-03-30
| | | | [originally from svn r3999]
* Couple of extra points: forgot about the \i\cw special case, andSimon Tatham2004-03-27
| | | | | | | Jacob points out that I didn't specify whether inline formatting commands can surround line breaks (they can). [originally from svn r3994]
* Second instalment of the manual: added a chapter on output formats.Simon Tatham2004-03-26
| | | | | | | | I _think_ the manual now contains all the information a user should need, even if not yet in an optimal order for a beginner to learn from. [originally from svn r3989]
* 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]
generated by cgit v1.1 at 2026-04-25 11:13:08 +0000