| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
| |
The \versionids in the docs are now added by the bob script; the one
in inputs/test.but has been replaced by fixed text (it didn't matter
what it contained anyway, of course, for test purposes), and the one
in misc/halibut.vim has simply been removed (it wasn't actually
expanded by svn anyway - it still had its old CVS value).
[originally from svn r10253]
|
| |
|
|
| |
[originally from svn r9774]
|
| |
|
|
|
|
|
| |
\cfg{paper-contents-margin}. Also correct the spelling of the
former.
[originally from svn r8424]
|
| |
|
|
|
|
|
| |
in the Info backend, with the defaults chosen to match what Emacs
recognises and renders prettily.
[originally from svn r7452]
|
| |
|
|
|
|
| |
in a Roman font. Follow suit.
[originally from svn r7450]
|
| |
|
|
| |
[originally from svn r7284]
|
| |
|
|
|
|
| |
fonts is difficult.
[originally from svn r7281]
|
| |
|
|
|
|
|
|
| |
(This doesn't affect any of the source texts I know about.)
Also add <link rel="up">, even in the cases where it's just the same as
<link rel="ToC">. (This does.)
[originally from svn r7193]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Off by default for now, but I don't intend that it should stay this way; they
seem useful and harmless. I just want to check a few more browsers to ensure
they don't do anything obnoxious with them.
So far I've only seen lynx and links do something with them (provide toolbars).
iCab and some Mozilla derivatives/extensions are also alleged to do this; Opera
is said to allow PgDn type browsing through the entire set of pages; and
Mozilla is rumoured to use the "next" link for prefetching.
[originally from svn r7177]
|
| |
|
|
|
|
|
|
| |
don't know how to write out a .CHM directly, but I am at least able
to have the HTML back end write out the three auxiliary files which
enable a .CHM to be generated using the MS HTML Help compiler.
[originally from svn r6991]
|
| |
|
|
| |
[originally from svn r6977]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
load font metrics dynamically, we're restricted to the fonts whose metrics
are compiled into Halibut. Font structures aren't reused when the same
font is specified twice, nor are unused fonts removed from the output.
Finally, the default configuration overflows lines in the manual, but this
would need a change to Halibut's grammar to fix.
Still, what's there works.
[originally from svn r6667]
|
| |
|
|
| |
[originally from svn r6663]
|
| |
|
|
| |
[originally from svn r5349]
|
| |
|
|
| |
[originally from svn r5347]
|
| |
|
|
| |
[originally from svn r5346]
|
| |
|
|
|
|
|
|
|
| |
character sets.
(Also make libcharset `return_in_enum' values saner.)
[originally from svn r5341]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
| |
[originally from svn r5339]
|
| |
|
|
| |
[originally from svn r5338]
|
| |
|
|
|
|
| |
put an AppleTitle tag in only one of a set of output HTML files.
[originally from svn r5192]
|
| |
|
|
|
|
| |
shorthand command \cq{foo}.
[originally from svn r4327]
|
| |
|
|
|
|
|
|
|
| |
Contains many FIXMEs, both for incomplete documentation and incomplete
code.
Couple of other minor tweaks elsewhere.
[originally from svn r4304]
|
| |
|
|
|
|
| |
directives.
[originally from svn r4302]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
terms (intentionally) differing only in case, which were being
silently folded into one by the case-insensitive index tag
comparison. Halibut now warns in this situation (but then folds them
anyway, which I think is better than silently generating an index
containing many case-distinct forms of the same word - I imagine
it's very easy to do that by mistake). The manual has been fixed to
explicitly define distinct keywords (in the case I spotted and in
five other cases picked up by the new warning!), and also documents
this issue and how to work with it.
[originally from svn r4279]
|
| |
|
|
| |
[originally from svn r4131]
|
| |
|
|
|
|
|
|
|
|
|
| |
configurable emphasis characters, various other configurable bits
which have been marked FIXME in the code for a while, and also to
warn when a code paragraph line is too long (because that was the
only other thing labelled FIXME). Fallback options are implemented,
and defaults set accordingly. A UTF-8 text output file now looks
like proper UTF-8.
[originally from svn r4128]
|
| |
|
|
|
|
|
| |
8859-*, UTF-8, or a variety of more fun encodings including various
multibyte ones.
[originally from svn r4095]
|
| |
|
|
| |
[originally from svn r4052]
|
| |
|
|
|
|
| |
manual. Added them.
[originally from svn r4038]
|
| |
|
|
|
|
| |
I'd better document them...
[originally from svn r4024]
|
|
|
[originally from svn r4007]
|