| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
--html, --winhelp and --man (plus spelling variations :-), which
allow you to choose to run only a subset of backends.
[originally from svn r4012]
|
| |
|
|
| |
[originally from svn r4011]
|
| |
|
|
|
|
|
|
| |
rather than merely HTML, I thought it might be instructive to run it
through the W3C's XHTML validator. Consequent changes in this
checkin...
[originally from svn r4010]
|
| |
|
|
| |
[originally from svn r4007]
|
| |
|
|
|
|
|
|
|
| |
a single newline) immediately after their opening brace; this was
causing a normal paragraph to be started, thus making it fiddly and
annoying to arrange the first paragraph of a \lcont to be a code
para or anything else special. Now fixed.
[originally from svn r4005]
|
| |
|
|
| |
[originally from svn r4004]
|
| |
|
|
| |
[originally from svn r4003]
|
| |
|
|
| |
[originally from svn r4002]
|
| |
|
|
|
|
|
|
|
| |
the preamble: \copyright paragraphs are now treated identically to
normal paragraphs (so they appear precisely where they're put
instead of in a fixed location), _except_ that the Windows Help
backend also copies their text into the help file's copyright slot.
[originally from svn r4001]
|
| |
|
|
|
|
| |
so. It's restorable using \IM.
[originally from svn r4000]
|
| |
|
|
| |
[originally from svn r3999]
|
| |
|
|
|
|
|
| |
Jacob points out that I didn't specify whether inline formatting
commands can surround line breaks (they can).
[originally from svn r3994]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
section title (which is not remotely unreasonable) got index
references added to them not only when the section title was
processed as part of its section, but also when it was processed as
part of contents navigation displays - in which situation it tended
to cause a link to, for example, the last section in the _previous_
file. Now we keep constant track of whether or not we're supposed to
be indexing things as we process text.
[originally from svn r3991]
|
| |
|
|
|
|
|
|
| |
I _think_ the manual now contains all the information a user should
need, even if not yet in an optimal order for a beginner to learn
from.
[originally from svn r3989]
|
| |
|
|
|
|
|
|
|
| |
zero-width delimiter between a macro invocation and text beyond it,
so that you can define (say) a macro which expands to a Euro sign
and then write `\eur\.2500' to avoid having space between the Euro
sign and the number.
[originally from svn r3982]
|
| |
|
|
|
|
|
|
|
|
| |
any ordinary displayable paragraph(s) appearing before the first
chapter heading, meaning in particular that you can put lists, code
paragraphs etc in preambles. Of course, `\preamble' is still
supported for backwards compatibility, but it's now a zero-effect
paragraph marker.
[originally from svn r3981]
|
| |
|
|
|
|
| |
(nearly nonexistent) invocation syntax and the input format.
[originally from svn r3979]
|
| |
|
|
| |
[originally from svn r3978]
|
| |
|
|
|
|
| |
there's nothing to go in it.
[originally from svn r3977]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
markup feature: a \c line in a code paragraph can now be followed by
an optional \e line indicating emphasised bits of its preceding \c.
This allows discretionary bolding and (italic/underline) emphasis
within code paragraphs, but without introducing an escape character
or breaking any existing input files. Users are warned that not all
backends are required to actually render these hints, and so they
should avoid depending on them 100% to convey semantic information
unless they know they're writing for a restricted range of backends.
[originally from svn r3965]
|
| |
|
|
|
|
| |
not break the numbering of the outer one!
[originally from svn r3955]
|
| |
|
|
|
|
|
|
|
| |
features commonly used in man pages: (a) the ability to nest
paragraph breaks, code paragraphs and other lists inside list items,
and (b) description lists as normally used in man pages to describe
command-line options.
[originally from svn r3954]
|
| |
|
|
|
|
|
|
| |
reference. (The broken link will already have been reported in the
mid-end, but this won't inhibit output generation, so the onus is
still on us to at the very least not go *crash*.)
[originally from svn r2507]
|
| |
|
|
|
|
|
|
| |
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]
|