| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
|
|
| |
without going through the .texi source stage. A few things left to
do, notably documentation, but the basics all seem to be there.
[originally from svn r4047]
|
| |
|
|
| |
[originally from svn r4045]
|
| |
|
|
|
|
|
| |
the Unix PuTTY archive, to automatically generate version numbers
for Halibut release builds.
[originally from svn r4044]
|
| |
|
|
| |
[originally from svn r4043]
|
| |
|
|
| |
[originally from svn r4042]
|
| |
|
|
|
|
| |
manual. Added them.
[originally from svn r4038]
|
| |
|
|
| |
[originally from svn r4036]
|
| |
|
|
|
|
| |
Comments
[originally from svn r4035]
|
| |
|
|
|
|
| |
\quote{...}
[originally from svn r4034]
|
| |
|
|
|
|
| |
Comments
[originally from svn r4033]
|
| |
|
|
| |
[originally from svn r4032]
|
| |
|
|
|
|
|
|
|
| |
Special handling for \U so that it works. Tweak \title.
Make butTextArg transparent so that emphasis (e.g. in a header) shows
through.
Comment tweaks.
[originally from svn r4031]
|
| |
|
|
| |
[originally from svn r4030]
|
| |
|
|
|
|
| |
We do, so let's.
[originally from svn r4029]
|
| |
|
|
|
|
|
| |
consistently in the documentation than to confuse matters by saying
`back end'. One rogue back end removed.
[originally from svn r4028]
|
| |
|
|
| |
[originally from svn r4027]
|
| |
|
|
| |
[originally from svn r4026]
|
| |
|
|
| |
[originally from svn r4025]
|
| |
|
|
|
|
| |
I'd better document them...
[originally from svn r4024]
|
| |
|
|
| |
[originally from svn r4023]
|
| |
|
|
|
|
|
|
|
|
| |
parametric template, reuse the same mechanism to allow the <a
name="..."> markers on each section to be parametrised as well. That
way, any user who so desires can arrange for everything in a section
URL to be constructed from internal keywords, making it pretty
robust against section numbering changes.
[originally from svn r4019]
|
| |
|
|
|
|
|
|
|
| |
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 r4016]
|
| |
|
|
| |
[originally from svn r4015]
|
| |
|
|
| |
[originally from svn r4014]
|
| |
|
|
|
|
| |
directives to be supplied on the Halibut command line.
[originally from svn r4013]
|
| |
|
|
|
|
|
| |
--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]
|