| Commit message (Collapse) | Author |
|---|
|
them either.
[originally from svn r7219]
|
|
winhelp.c which uses all my new library code to import an arbitrary
PNG and embed it into the test help file.
[originally from svn r6984]
|
|
files. Halibut does not make use of this feature, but I hope that
one day it might.
[originally from svn r6980]
|
|
in future, add `-ansi -pedantic' to the Halibut default compile
options and fix the few resulting warnings (mostly signed/unsigned
char mismatches and commas at the ends of enums). The one remaining
warning I'm still seeing is `missing initializer' for the big table
in charset/iso2022.c, but I think the code genuinely is more
readable this way, and I haven't found a gcc option to disable that
specific warning.
[originally from svn r6458]
|
|
[originally from svn r4399]
|
|
of `unsigned long'. Should help Debian build problems (bug#259504).
[originally from svn r4377]
|
|
(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]
|
|
[originally from svn r1800]
|
|
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]
|
|
near-complete functionality. All that's missing now is indexing and
horizontal rules.
[originally from svn r1449]
|
|
attributes to default values right at the start of the file. We
don't want the title on the very first page being 1000 pixels high!
[originally from svn r1448]
|
|
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]
|
|
that this module doesn't leak like a sieve with the mesh missing. I
think this code is now mature enough for the Buttress back end to be
written. Woo.
[originally from svn r1443]
|
|
hyphens off the todo list, because I've found out that NBS is just
done using good old \xA0 (Winterhoff's analysis appears wrong) and
hyphens are _all_ nonbreaking. Shame, but you can't have everything.
[originally from svn r1442]
|
|
[originally from svn r1441]
|
|
[originally from svn r1440]
|
|
[originally from svn r1438]
|
|
[originally from svn r1437]
|
|
files. This is not a Buttress back end as such; it's a piece of
portable, reusable code handling HLP output. I will then have to
write bk_whlp.c as glue between the Buttress internal data format
and the API provided by this code.
[originally from svn r1436]
|
