| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
|
|
|
| |
complaints, it would probably help if I arranged that those things
had been _allocated_ in all cases, otherwise we merely exchange a
memory leak for a core dump. Duh.
[originally from svn r1916]
|
| |
|
|
|
|
|
| |
thingy, which seems moderately cool and has reported a few very
small memory leaks. Now apparently fixed.
[originally from svn r1863]
|
| |
|
|
|
|
|
|
| |
way as bk_text already does it (you can choose to have or not have
the "Section" at the start, and you can configure the suffix between
number and title).
[originally from svn r1839]
|
| |
|
|
|
|
| |
before the section title (the ": " in "Section 1: Introduction").
[originally from svn r1838]
|
| |
|
|
|
|
|
| |
blank-line separators (config directives visually _want_ to be in a
single chunk).
[originally from svn r1837]
|
| |
|
|
|
|
| |
failed to be decreased to compensate for the additional indent.
[originally from svn r1834]
|
| |
|
|
|
|
| |
output from running Halibut on a test input file.
[originally from svn r1833]
|
| |
|
|
| |
[originally from svn r1832]
|
| |
|
|
|
|
|
|
| |
which case the whole of the HTML output will be in a single file,
currently called Manual.html in the absence of configurability).
This includes the index, if present.
[originally from svn r1831]
|
| |
|
|
| |
[originally from svn r1800]
|
| |
|
|
|
|
|
| |
Windows is tricky otherwise, since Index.html clashes with
index.html. Bah).
[originally from svn r1575]
|
| |
|
|
|
|
|
| |
Contents entries are now, eg, "Chapter 1: Introduction" rather than just
"Introduction".
[originally from svn r1552]
|
| |
|
|
|
|
|
|
| |
poorly; mostly it just treated \r as whitespace, and the only time
it actually suffered was at the end of a line in a code paragraph).
Should now be fixed.
[originally from svn r1492]
|
| |
|
|
| |
[originally from svn r1490]
|
| |
|
|
|
|
|
|
| |
heapsort. This makes the code much simpler for a start, but the main
reason is so that we can spot duplicate keywords as we go along
rather than having to wait until the end of input processing.
[originally from svn r1489]
|
| |
|
|
| |
[originally from svn r1488]
|
| |
|
|
| |
[originally from svn r1475]
|
| |
|
|
|
|
|
|
|
| |
top-level leaf nodes simply can't be done, because you can't lower
the level of the node to 0 to compensate for the bug because the
parser rejects it). A different workaround is now in place for those
cases.
[originally from svn r1465]
|
| |
|
|
|
|
|
|
|
|
| |
sections. Useful if another program needs to jump to a particular
topic. (Really we should support the proper CTXOMAP / HELP_WM_HELP
system for doing this, but I don't like numeric IDs; you'd have to
parse a bunch of #defines in order to sensibly synchronise the IDs
between help file and code.)
[originally from svn r1457]
|
| |
|
|
|
|
|
|
|
| |
deliberately incorrect, to compensate for a bug in WinHelp. With any
luck MS will never fix the bug and this .CNT will continue to work
forever. Since WinHelp is theoretically obsolete, this sounds
reasonably likely.)
[originally from svn r1456]
|
| |
|
|
|
|
|
| |
terms and section titles. They were unfortunately screwing up index
sorting, so they had to go.
[originally from svn r1455]
|
| |
|
|
|
|
| |
strikethrough on bullets. *boggle*
[originally from svn r1454]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
liking, as planned. In bk_whlp.c, this has now allowed me to stop
emphasis and code from looking silly in section titles, and also
allowed me to implement an ersatz horizontal rule in the form of
eighty centred nonbreaking spaces in a strike-through font. I know
it's vile, but better suggestions are welcome.
I think the Windows Help backend is now pretty much Go: I was
getting intermittent screwups earlier but I think those were Samba
cache persistence problems rather than evil segfaults. All that's
really missing now is external context references.
[originally from svn r1453]
|
| |
|
|
| |
[originally from svn r1452]
|
| |
|
|
|
|
| |
menus at the bottom of help topics. Now fixed. What a cool bug :-)
[originally from svn r1451]
|
| |
|
|
| |
[originally from svn r1450]
|
| |
|
|
|
|
|
| |
near-complete functionality. All that's missing now is indexing and
horizontal rules.
[originally from svn r1449]
|
| |
|
|
|
|
|
| |
attributes to default values right at the start of the file. We
don't want the title on the very first page being 1000 pixels high!
[originally from svn r1448]
|
| |
|
|
|
|
|
|
|
|
| |
hierarchical topic navigation (menus at the bottom of non-leaf
topics, and the Up button) and index support; also I want to give
users the ability to specify context IDs for particular topics. Oh,
and I haven't found a plausible way to express a horizontal rule in
either .RTF or .HLP format. But everything else appears to be there.
[originally from svn r1447]
|
| |
|
|
|
| |
[originally from svn r1446]
[this svn revision also touched putty]
|
| |
|
|
|
|
| |
and _then_ setting x = x->next!).
[originally from svn r1445]
|
| |
|
|
|
|
| |
tree234 routines; they will be useful in the WinHelp stuff at least.
[originally from svn r1444]
|
| |
|
|
|
|
|
|
| |
that this module doesn't leak like a sieve with the mesh missing. I
think this code is now mature enough for the Buttress back end to be
written. Woo.
[originally from svn r1443]
|
| |
|
|
|
|
|
|
| |
hyphens off the todo list, because I've found out that NBS is just
done using good old \xA0 (Winterhoff's analysis appears wrong) and
hyphens are _all_ nonbreaking. Shame, but you can't have everything.
[originally from svn r1442]
|
| |
|
|
| |
[originally from svn r1441]
|
| |
|
|
| |
[originally from svn r1440]
|
| |
|
|
| |
[originally from svn r1438]
|
| |
|
|
| |
[originally from svn r1437]
|
| |
|
|
|
|
|
|
|
| |
files. This is not a Buttress back end as such; it's a piece of
portable, reusable code handling HLP output. I will then have to
write bk_whlp.c as glue between the Buttress internal data format
and the API provided by this code.
[originally from svn r1436]
|
| |
|
|
|
|
|
|
|
|
|
| |
versionids. I thought it might be nice to include only the
versionid(s) from the .but file(s) that gave rise to a particular
chapter file, but actually this is very badly defined (that
information is thrown away very early on in the front end) and in
any case thanks to cross-references every file _does_ depend on its
fellows. Better to put them all in throughout.
[originally from svn r1417]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
`question' or so on, using the syntax
\S{mysection}{example} An example of foobar
so that in cross-references it will be referred to as `example
5.1.2' instead of `section 5.1.2'. NOTE WELL: until now Buttress has
supported multiple section keywords using the same syntax, so that
you could xref the above section as \k{mysection} _or_ \k{example}
with the same effect. This behaviour is now revoked because I don't
think anyone was using it; if you suddenly find you're getting
undefined-keyword errors this may be why.
[originally from svn r1408]
|
| |
|
|
|
|
| |
implementation is inside out for part of it).
[originally from svn r1331]
|
| |
|
|
|
|
| |
Fixed again.
[originally from svn r1330]
|
| |
|
|
|
|
|
|
|
|
| |
user doesn't skip a heading level (\H before any \C or \A, or \S
straight after \C with no intervening \H). The precise criterion is
that when creating section a.b.c.d, sections a.b.c, a.b and a should
already exist. This ensures the section tree really is a properly
formed tree with no missing nodes.
[originally from svn r1329]
|
| |
|
|
| |
[originally from svn r1328]
|
| |
|
|
|
|
| |
sorted out the HTML truncated-contents bug.
[originally from svn r1327]
|
| |
|
|
| |
[originally from svn r1325]
|
| |
|
|
|
|
|
| |
like a typographical Bad Plan, but they work OK in some types of
document such as a FAQ.)
[originally from svn r1324]
|
| |
|
|
| |
[originally from svn r1323]
|
| |
|
|
|
|
|
|
| |
its line. Real typesetters in practice don't appear to care much
about this, and the lengths the algorithm has to go to to avoid it
tend to end up looking even uglier.
[originally from svn r1322]
|