| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r1321]
|
| |
|
|
|
|
| |
optimal dynamic one used by the likes of TeX. Woo.
[originally from svn r1288]
|
| |
|
|
| |
[originally from svn r1159]
|
| |
|
|
|
|
| |
being incremented _past_ the NUL, so the rest of the string was lost.
[originally from svn r902]
|
| |
|
|
|
|
| |
without worry (oops)
[originally from svn r866]
|
| |
|
|
|
|
| |
* Frees up data structures
[originally from svn r835]
|
| |
|
|
| |
[originally from svn r834]
|
| |
|
|
| |
[originally from svn r833]
|
| |
|
|
| |
[originally from svn r828]
|
| |
|
|
| |
[originally from svn r811]
|
| |
|
|
| |
[originally from svn r810]
|
| |
|
|
| |
[originally from svn r809]
|
| |
|
|
|
|
| |
in text output. Now all aux fields are carefully zeroed when not used
[originally from svn r307]
|
| |
|
|
| |
[originally from svn r276]
|
| |
|
|
| |
[originally from svn r275]
|
| |
|
|
| |
[originally from svn r274]
|
| |
|
|
| |
[originally from svn r262]
|
| |
|
|
| |
[originally from svn r261]
|
| |
|
|
| |
[originally from svn r259]
|
| |
|
|
| |
[originally from svn r257]
|
| |
|
|
| |
[originally from svn r256]
|
| |
|
|
| |
[originally from svn r254]
|
| |
|
|
| |
[originally from svn r252]
|
| |
|
|
| |
[originally from svn r251]
|