| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
from its command-line option (`--text=foo.txt') and automatically
convert it into one or more notional \cfg directives. In the HTML
case this mechanism enables single-file mode as well as setting the
filename.
[originally from svn r4018]
|
| |
|
|
|
|
| |
name (or name schema, in HTML).
[originally from svn r4017]
|
| |
|
|
| |
[originally from svn r4011]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r3978]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r1800]
|
| |
|
|
|
|
|
|
|
| |
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]
|
|
|
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]
|