summaryrefslogtreecommitdiff
path: root/doc (follow)
Commit message (Collapse)AuthorAge
* Bump copyright dates, and change the one at the start of the manual to beBen Harris2007-01-01
| | | | | | a range rather than a single year. [originally from svn r7047]
* Actually, the separator in the "NAME" section really ought to be anBen Harris2006-12-11
| | | | | | EN DASH, falling back to MINUS and then HYPHEN-MINUS. Make it so. [originally from svn r6992]
* Support for the MS HTML Help system in the HTML back end. As yet ISimon Tatham2006-12-11
| | | | | | | | don't know how to write out a .CHM directly, but I am at least able to have the HTML back end write out the three auxiliary files which enable a .CHM to be generated using the MS HTML Help compiler. [originally from svn r6991]
* Just noticed that Ben missed another PostScript/PDF inversion.Simon Tatham2006-12-11
| | | | [originally from svn r6990]
* Fix amusing cut-and-paste error in section keywords :-)Simon Tatham2006-12-11
| | | | [originally from svn r6989]
* Update copyright dates.Ben Harris2006-12-09
| | | | [originally from svn r6979]
* Some documentation of Halibut's font-embedding support, now that it works.Ben Harris2006-12-09
| | | | [originally from svn r6977]
* This somehow got missed in my "put PDF before PostScript" sweep.Ben Harris2006-12-09
| | | | [originally from svn r6976]
* Mention PDF before PostScript everywhere, partly because PDF is theBen Harris2006-12-09
| | | | | | | | | dominant format for print-oriented documents, but mostly because it's hard to mention pdfmark without having mentioned PDF already. Also mention pdfmark. [originally from svn r6975]
* I've just noticed some unacceptably long lines in code paragraphs inSimon Tatham2006-12-07
| | | | | | | | | | | | | | | the Halibut manual. They turn out to be \cfg directives with multiple braced sections after them. The obvious thing to do for legibility would be to wrap those sections by putting newlines between } and {, but that isn't legal in the Halibut syntax. Therefore, it is now :-) For paragraph types which don't have any body text (such as \cfg), we are now lenient about whitespace between multiple keywords. So I can fix the docs so they don't go over the limit, and be confident that the fixed version is still technically accurate. [originally from svn r6970]
* Two of the bugs listed in the man page are out of date: Unicode andSimon Tatham2006-12-04
| | | | | | | | | character set support, and the HTML back end, have both been extensively revamped since that section was written, and I think neither of them is shoddy enough to warrant this sort of self-disparagement any more. [originally from svn r6959]
* Paging through the newly compressed PDF manual to make sure itSimon Tatham2006-12-04
| | | | | | | | worked, I happened to notice this typo. I think Wikipedia might have permanently removed my ability to read any document for any purpose without spotting at least one error in it. [originally from svn r6958]
* Explicitly explain the meaning of each HTML variant.Ben Harris2006-11-18
| | | | [originally from svn r6913]
* Introduce global (cross-backend) \cfg{contents} and \cfg{index}Simon Tatham2006-06-02
| | | | | | | commands, allowing the fixed words "Contents" and "Index" generated in various output formats to be reconfigured into other languages. [originally from svn r6724]
* 297mm is closer to 842pt than to 841pt, and the former seems to be theBen Harris2006-05-09
| | | | | | | accepted length of A4 paper in the PostScript/PDF world, so use it as our default. [originally from svn r6669]
* Add font-selection mechanism to the paper backend. Since we have no way toBen Harris2006-05-08
| | | | | | | | | | | | load font metrics dynamically, we're restricted to the fonts whose metrics are compiled into Halibut. Font structures aren't reused when the same font is specified twice, nor are unused fonts removed from the output. Finally, the default configuration overflows lines in the manual, but this would need a change to Halibut's grammar to fix. Still, what's there works. [originally from svn r6667]
* Now that I've found the core AFMs, I notice that they have a perfectlyBen Harris2006-05-08
| | | | | | | good free licence. Abide by its terms even though I'm not sure Halibut is a derived work in law. [originally from svn r6666]
* It's conventional to use a minus sign rather than a hyphen to separateBen Harris2006-05-08
| | | | | | | the description from the name in the NAME section of a manpage. Halibut can do that now, so make use of that ability. [originally from svn r6664]
* New configuration directives need new aliases in the index too.Ben Harris2006-05-07
| | | | [originally from svn r6663]
* Improve rule generation in the "man" backend so that if the outputBen Harris2006-05-06
| | | | | | | is processed by nroff, the rule is made up of \cfg{man-rule} characters (same defaults as \cfg{text-rule}). [originally from svn r6651]
* It's a new year.Jacob Nevins2006-01-08
| | | | | [originally from svn r6513] [this svn revision also touched putty,putty-website,puzzles]
* Ability to specify multiple arguments to \cfg{html-template-fragment};Jacob Nevins2005-03-08
| | | | | | | | | | | | | | | Halibut will output fragment names in all specified formats. (I forget now precisely why I thought this was necessary, but it seems potentially useful.) Also ensure that legal fragment names are generated even if none of the characters from the original turn out to be legal (e.g., %k with an entirely numeric keyword), and correct an untruth I inserted in the documentation of this. (This commit hits more than just the HTML backend as I've generalised an error message, and fixed a fault in the info backend's error handling while there.) [originally from svn r5457]
* Move contact details inside <address> to make validator.w3.org happy.Jacob Nevins2005-03-07
| | | | [originally from svn r5454]
* Oops, overzealous search-and-replaceJacob Nevins2005-02-18
| | | | [originally from svn r5349]
* Missing index modifiersJacob Nevins2005-02-18
| | | | [originally from svn r5347]
* Update the documentation of the HTML backend to match reality.Jacob Nevins2005-02-18
| | | | [originally from svn r5346]
* Add a `--list-charsets' option to Halibut to enumerate canonical names of knownJacob Nevins2005-02-18
| | | | | | | | | character sets. (Also make libcharset `return_in_enum' values saner.) [originally from svn r5341] [this svn revision also touched charset,filter,timber]
* Indexing tweaks for recent changes.Jacob Nevins2005-02-18
| | | | [originally from svn r5339]
* Add \versionid.Jacob Nevins2005-02-17
| | | | [originally from svn r5338]
* It's been a new year for a while.Jacob Nevins2005-02-17
| | | | [originally from svn r5337]
* Note that we'd appreciate help re charsets in WinHelpJacob Nevins2005-02-17
| | | | [originally from svn r5334]
* Note visibly that HTML docs are out of date.Jacob Nevins2005-02-17
| | | | [originally from svn r5333]
* Changes/additions to input character set handling:Jacob Nevins2005-02-17
| | | | | | | | | | | | | | | | | - After discussion with Simon, change the default input charset back to ASCII, rather than trying to work it out from the locale, for the sake of promoting .but file portability. - Add a new command-line option "--input-charset=csname", which overrides the ASCII default for all input files (since there's no other way to use a non-ASCII-compatible input file). - Output a warning if -Cinput-charset:foo is specified that it has no effect. - Update the docs to match all this. Also try to clarify some other things in this area that caught me out. [originally from svn r5332]
* Added a new config directive `html-local-head', which permits me toSimon Tatham2005-01-24
| | | | | | put an AppleTitle tag in only one of a set of output HTML files. [originally from svn r5192]
* Remove .cvsignore files on all active branches.Simon Tatham2004-11-16
| | | | | [originally from svn r4788] [this svn revision also touched bmbm,caltrap,charset,enigma,filter,fonts,golem,grunge,html,lj,local,misc,polyhedra,putty,putty-website,putty-wishlist,puzzles,pycee,sdlgames,svn-tools,timber,tweak]
* 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]
generated by cgit v1.1 at 2026-05-14 23:09:51 +0000