summaryrefslogtreecommitdiff
path: root/bk_html.c (follow)
Commit message (Collapse)AuthorAge
* Fix for an uninitialised structure member spotted by valgrind (probably didn'tJacob Nevins2004-08-04
| | | | | | have any real effect). [originally from svn r4401]
* Avoid generating an index section if there actually is no index.Simon Tatham2004-07-02
| | | | [originally from svn r4321]
* Sort out error handling everywhere a charset name is converted intoSimon Tatham2004-06-27
| | | | | | an integer charset ID. [originally from svn r4317]
* Free up all the data we allocated during the HTML backend.Simon Tatham2004-06-27
| | | | [originally from svn r4316]
* Support non-breaking spaces.Simon Tatham2004-06-27
| | | | [originally from svn r4315]
* Config directives for all the extra configurable things in the newSimon Tatham2004-06-27
| | | | | | HTML backend. [originally from svn r4314]
* Fix up the restrict_charset and output_charset configuration for theSimon Tatham2004-06-27
| | | | | | | | | | | | | | HTML backend. After an argument with James in which it transpired that we each thought it was absolutely obvious which one \cfg{html-charset} ought to map to, and each of us was thinking of a different one, I've decided that this implies it _isn't_ obvious, and hence there is no single \cfg{html-charset} directive at all. Instead, we have \cfg{html-restrict-charset} and \cfg{html-output- charset}, and any naive user who `just wants to change character set' is just going to have to RTFM and figure out which one they mean. [originally from svn r4313]
* Various HTML backend cleanups.Simon Tatham2004-06-20
| | | | [originally from svn r4308]
* Introduce a configurable option to select the HTML flavour. AlsoSimon Tatham2004-06-20
| | | | | | | fiddle with various small aspects of the output so that it actually validates in all supported flavours. [originally from svn r4307]
* Improve the naming of fragment IDs for numbered list elements andSimon Tatham2004-06-20
| | | | | | bibliography entries. [originally from svn r4305]
* Add a batch of assertions to ensure no more index terms fail to haveSimon Tatham2004-06-19
| | | | | | | | | their anchors generated. Index bugs of this type can be terribly subtle and go unnoticed for ages; I'm lucky Jacob spotted the first one of the type, but I'm now going to be careful to avoid any further ones. [originally from svn r4293]
* I had somehow managed to leave index entry anchors out of sectionSimon Tatham2004-06-19
| | | | | | titles. Ahem. [originally from svn r4292]
* Add a clash-checking mechanism to ensure we never generate the sameSimon Tatham2004-06-19
| | | | | | fragment name twice for any reason. [originally from svn r4291]
* Switch the memory allocation macros from the Halibut onesSimon Tatham2004-06-12
| | | | | | | | | | | | | (mknew/mknewa/resize) to the PuTTY ones (snew/snewn/sresize). snewn and mknewa have their arguments opposite ways round; this may make the change initially painful but in the long term will free me of a nasty context switch every time I move between codebases. Also sresize takes an explicit type operand which is used to cast the return value from realloc, thus enforcing that it must be correct, and arranging that if anyone tries to compile Halibut with a C++ compiler there should be a lot less pain. [originally from svn r4276]
* 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]