summaryrefslogtreecommitdiff
path: root/doc/running.but (unfollow)
Commit message (Collapse)Author
2017-05-13New output mode to write CHM files directly.Simon Tatham
I became aware a few months ago that enough is known about CHM files that free software _can_ write them without benefit of the MS HTML Help compiler - in particular there's a thing called 'chmcmd' in the Free Pascal Compiler software distribution which is more or less a drop-in replacement for hhc.exe itself. But although depending on chmcmd would be a bit nicer than depending on hhc.exe, Halibut has always preferred to do the whole job itself if it can. So here's my own from-scratch code to generate CHM directly from Halibut source. The new output mode is presented as a completely separate top-level thing independent of HTML mode. Of course, in reality, the two back ends share all of the HTML-generation code, differing only in a few configuration defaults and the minor detail of what will be _done_ with each chunk of HTML as it's generated (this is what the recent refactoring in b3db1cce3 was in aid of). But even so, the output modes are properly independent from a user-visible-behaviour perspective: they use parallel sets of config directives rather than sharing the same ones (you can set \cfg{html-foo} and \cfg{chm-foo} independently, for a great many values of 'foo'), and you can run either or neither or both as you choose in a given run of Halibut. The old HTML Help support, in the form of some config directives for HTML mode to output the auxiliary files needed by hhc.exe, is still around and should still work the same as it always did. I have no real intention of removing it, partly for the reasons stated in the manual (someone might find it useful to have Halibut generate the .HHP file once and then make manual adjustments to it, so that they can change styling options that the direct CHM output doesn't permit), and mostly because it wouldn't save a great deal of code or complexity in any case - the big two of the three auxiliary files (the HHC and HHK) have to be generated _anyway_ to go inside the .CHM, so all the code would have to stay around regardless.
2014-09-24Remove Subversion expanded keywords everywhere.Simon Tatham
The \versionids in the docs are now added by the bob script; the one in inputs/test.but has been replaced by fixed text (it didn't matter what it contained anyway, of course, for test purposes), and the one in misc/halibut.vim has simply been removed (it wasn't actually expanded by svn anyway - it still had its old CVS value). [originally from svn r10253]
2007-02-13Make quite a lot of hyphens into non-breaking ones. This gives ratherBen Harris
nicer output. [originally from svn r7282]
2007-02-13Add a --list-fonts option, since getting PostScript names out of TrueTypeBen Harris
fonts is difficult. [originally from svn r7281]
2006-12-11Support for the MS HTML Help system in the HTML back end. As yet ISimon Tatham
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]
2006-12-09This somehow got missed in my "put PDF before PostScript" sweep.Ben Harris
[originally from svn r6976]
2005-02-18Update the documentation of the HTML backend to match reality.Jacob Nevins
[originally from svn r5346]
2005-02-18Add a `--list-charsets' option to Halibut to enumerate canonical names of knownJacob Nevins
character sets. (Also make libcharset `return_in_enum' values saner.) [originally from svn r5341] [this svn revision also touched charset,filter,timber]
2005-02-18Indexing tweaks for recent changes.Jacob Nevins
[originally from svn r5339]
2005-02-17Add \versionid.Jacob Nevins
[originally from svn r5338]
2005-02-17Changes/additions to input character set handling:Jacob Nevins
- 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]
2004-06-19Minor correction to --ps and --pdf descriptions.Jacob Nevins
[originally from svn r4296]
2004-04-14After printing out the PDF manual and reading it through, here's aSimon Tatham
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]
2004-04-14... oh, except that minimal documentation might be helpful.Simon Tatham
[originally from svn r4075]
2004-04-10Add documentation for the info backend.Simon Tatham
[originally from svn r4052]
2004-04-01Forgot to mention the default behaviour is to run all backends.Simon Tatham
[originally from svn r4027]
2004-04-01Having done all these command-line options and new \cfg directives,Simon Tatham
I'd better document them... [originally from svn r4024]
2004-03-30The manual is now fully indexed.Simon Tatham
[originally from svn r3999]
2004-03-25First instalment of a manual for Halibut. This lot covers theSimon Tatham
(nearly nonexistent) invocation syntax and the input format. [originally from svn r3979]