| Commit message (Collapse) | Author |
|---|
|
[originally from svn r1800]
|
|
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]
|
|
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]
|
|
[originally from svn r1450]
|
|
near-complete functionality. All that's missing now is indexing and
horizontal rules.
[originally from svn r1449]
|
|
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]
|
|
tree234 routines; they will be useful in the WinHelp stuff at least.
[originally from svn r1444]
|
|
`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]
|
|
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]
|
|
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 r828]
|
|
[originally from svn r276]
|
|
[originally from svn r275]
|
|
[originally from svn r274]
|
|
[originally from svn r259]
|
|
[originally from svn r252]
|
|
[originally from svn r248]
|
|
between emphasis _like_ _this_ and _like this_
[originally from svn r245]
|
|
[originally from svn r242]
|
|
[originally from svn r240]
|
|
[originally from svn r238]
|
|
[originally from svn r237]
|
|
[originally from svn r220]
|
|
[originally from svn r214]
|
|
[originally from svn r200]
|
|
[originally from svn r193]
|
|
[originally from svn r187]
|
