| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
| |
(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]
|
| |
|
|
|
|
|
| |
\cfg{html-rellinks}, and it generally seems to be a Good Thing, so I've
turned it on by default. (The lurkers support me in u2u.)
[originally from svn r7188]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CHM, and added the toolbar buttons for this.
Also rationalised the other options a bit:
- added Forward button (since we have Back);
- removed Locate/Sync (since we have auto-sync enabled for the ToC);
- removed Stop and Refresh (mostly a waste of space for help, but still
available from the Options menu if users really want them);
- enabled advanced facilities on the Search tab (search within results, etc).
All this seems to have had no obvious ill effects (tested on Win98), although
the resulting CHM file is slightly bigger (~3kbyte, <1%).
[originally from svn r7176]
|
| |
|
|
|
|
| |
any, I reckon.
[originally from svn r6994]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
commands, allowing the fixed words "Contents" and "Index" generated
in various output formats to be reconfigured into other languages.
[originally from svn r6724]
|
| |
|
|
|
|
| |
segfault if they were unable to open their output files.
[originally from svn r6704]
|
| |
|
|
|
|
|
| |
`anonfrag' should be a char[] rather than a char *, or else lenof()
will give the wrong answer.
[originally from svn r5477]
|
| |
|
|
|
|
|
|
|
| |
conceptually const but not declared as such. Halibut is now back to
the practically-speaking-pointless but rather satisfying status of
having no global writable data whatsoever :-)
[originally from svn r5476]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Halibut will output fragment names in all specified formats. (I forget now
precisely why I thought this was necessary, but it seems potentially useful.)
Also ensure that legal fragment names are generated even if none of the
characters from the original turn out to be legal (e.g., %k with an entirely
numeric keyword), and correct an untruth I inserted in the documentation of
this.
(This commit hits more than just the HTML backend as I've generalised an error
message, and fixed a fault in the info backend's error handling while there.)
[originally from svn r5457]
|
| |
|
|
|
|
|
|
|
| |
all HTML flavours).
Also add newlines to the contents output so that the source is vaguely
legible.
Couple of extra comments in the code.
[originally from svn r5453]
|
| |
|
|
| |
[originally from svn r5350]
|
| |
|
|
| |
[originally from svn r5348]
|
| |
|
|
|
|
| |
name.
[originally from svn r5336]
|
| |
|
|
|
|
| |
sections looking for local configuration data.
[originally from svn r5196]
|
| |
|
|
|
|
| |
put an AppleTitle tag in only one of a set of output HTML files.
[originally from svn r5192]
|
| |
|
|
|
|
| |
have any real effect).
[originally from svn r4401]
|
| |
|
|
| |
[originally from svn r4321]
|
| |
|
|
|
|
| |
an integer charset ID.
[originally from svn r4317]
|
| |
|
|
| |
[originally from svn r4316]
|
| |
|
|
| |
[originally from svn r4315]
|
| |
|
|
|
|
| |
HTML backend.
[originally from svn r4314]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
HTML backend. After an argument with James in which it transpired
that we each thought it was absolutely obvious which one
\cfg{html-charset} ought to map to, and each of us was thinking of a
different one, I've decided that this implies it _isn't_ obvious,
and hence there is no single \cfg{html-charset} directive at all.
Instead, we have \cfg{html-restrict-charset} and \cfg{html-output-
charset}, and any naive user who `just wants to change character
set' is just going to have to RTFM and figure out which one they
mean.
[originally from svn r4313]
|
| |
|
|
| |
[originally from svn r4308]
|
| |
|
|
|
|
|
| |
fiddle with various small aspects of the output so that it actually
validates in all supported flavours.
[originally from svn r4307]
|
| |
|
|
|
|
| |
bibliography entries.
[originally from svn r4305]
|
| |
|
|
|
|
|
|
|
| |
their anchors generated. Index bugs of this type can be terribly
subtle and go unnoticed for ages; I'm lucky Jacob spotted the first
one of the type, but I'm now going to be careful to avoid any
further ones.
[originally from svn r4293]
|
| |
|
|
|
|
| |
titles. Ahem.
[originally from svn r4292]
|
| |
|
|
|
|
| |
fragment name twice for any reason.
[originally from svn r4291]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(mknew/mknewa/resize) to the PuTTY ones (snew/snewn/sresize). snewn
and mknewa have their arguments opposite ways round; this may make
the change initially painful but in the long term will free me of a
nasty context switch every time I move between codebases. Also
sresize takes an explicit type operand which is used to cast the
return value from realloc, thus enforcing that it must be correct,
and arranging that if anyone tries to compile Halibut with a C++
compiler there should be a lot less pain.
[originally from svn r4276]
|
|
|
end. There's a lot more _potentiality_ for new features than there
are actual new features just yet, but future highlights include:
configurable flavour of HTML (3.2, 4, XHTML Transitional or Strict),
proper character set support (this is half way there already), and
more flexible allocation of sections between multiple HTML files.
Meanwhile, immediate benefits include correct handling of special
characters within `author' and `description' strings, omission of
the filename part in hyperlinks within the same HTML file (in
particular, this means a single output file is now totally
independent of its filename), and hyperlinks to the index from the
top-level contents page (I'm amazed nobody has complained at the
lack of this yet!). There are no doubt some shiny new bugs as well,
but I'll never find them unless people start using the thing...
[originally from svn r4275]
|