summaryrefslogtreecommitdiff
path: root/doc/output.but (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]
* 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]
* 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 no index is generated by the text backend.Jacob Nevins2004-06-19
| | | | [originally from svn r4297]
* 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]
* 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]
* General configurability upgrade for the info back end.Simon Tatham2004-04-23
| | | | [originally from svn r4131]
* 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]
* 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]
* Add documentation for the info backend.Simon Tatham2004-04-10
| | | | [originally from svn r4052]
* Having done all these command-line options and new \cfg directives,Simon Tatham2004-04-01
| | | | | | I'd better document them... [originally from svn r4024]
* The manual is now fully indexed.Simon Tatham2004-03-30
| | | | [originally from svn r3999]
* 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]