halibut/bk_whlp.c, branch master My halibut tree Add \s for 'strong' text, i.e. bold rather than italics. I've missed 2013-03-10T16:58:01+00:00 Simon Tatham anakin@pobox.com 2013-03-10T16:58:01+00:00 dcf080aa0e011de37a154e9e8a97dd7546a4a1b1 this a couple of times in Halibut markup recently (in particular, it's handy to have a typographical distinction between 'this term is emphasised because it's new' and 'this term is emphasised because I want you to pay attention to it'), so here's an implementation, basically parallel to \e. One slight oddity is that strong text in headings will not be distinguished in some output formats, since they already use bolded text for their headings. [originally from svn r9772] 
this a couple of times in Halibut markup recently (in particular, it's
handy to have a typographical distinction between 'this term is
emphasised because it's new' and 'this term is emphasised because I
want you to pay attention to it'), so here's an implementation,
basically parallel to \e.

One slight oddity is that strong text in headings will not be
distinguished in some output formats, since they already use bolded
text for their headings.

[originally from svn r9772]
Revamp of the Halibut error handling mechanism. 2012-08-29T18:13:11+00:00 Simon Tatham anakin@pobox.com 2012-08-29T18:13:11+00:00 1489dc15967970576d08f3f2b22c6e1c939bcbcf I'm not quite sure why I ever thought it was a good idea to have a central variadic error() function taking an integer error code followed by some list of arguments that depend on that code. It now seems obvious to me that it's a much more sensible idea to have a separate function per error, so that we can check at compile time that the arguments to each error call are of the right number and type! So I've done that instead. A side effect is that the errors are no longer formatted into a fixed-size buffer before going to stderr, so I can remove all the %.200s precautions in the format strings. [originally from svn r9639] 
I'm not quite sure why I ever thought it was a good idea to have a
central variadic error() function taking an integer error code
followed by some list of arguments that depend on that code. It now
seems obvious to me that it's a much more sensible idea to have a
separate function per error, so that we can check at compile time that
the arguments to each error call are of the right number and type! So
I've done that instead.

A side effect is that the errors are no longer formatted into a
fixed-size buffer before going to stderr, so I can remove all the
%.200s precautions in the format strings.

[originally from svn r9639]
Introduce global (cross-backend) \cfg{contents} and \cfg{index} 2006-06-02T19:19:12+00:00 Simon Tatham anakin@pobox.com 2006-06-02T19:19:12+00:00 9e8ca006788e2148154711e1e67b88f495d94e26 commands, allowing the fixed words "Contents" and "Index" generated in various output formats to be reconfigured into other languages. [originally from svn r6724] 
commands, allowing the fixed words "Contents" and "Index" generated
in various output formats to be reconfigured into other languages.

[originally from svn r6724]
Missing error handling: the HTML and WinHelp back ends would both 2006-05-18T08:38:41+00:00 Simon Tatham anakin@pobox.com 2006-05-18T08:38:41+00:00 c28de5a4ca45ed1d78ae2e3d610175cf7752703c segfault if they were unable to open their output files. [originally from svn r6704] 
segfault if they were unable to open their output files.

[originally from svn r6704]
Failed to initialise state.curr_topic early enough, causing 2004-07-13T08:40:20+00:00 Simon Tatham anakin@pobox.com 2004-07-13T08:40:20+00:00 a5e910448b26d9d77af462c0634ab34b0a465d0d uninitialised-memory references and a segfault. Quite why this never happened when I tested it at home, I have no idea! [originally from svn r4326] 
uninitialised-memory references and a segfault. Quite why this never
happened when I tested it at home, I have no idea!

[originally from svn r4326]
nit: s/case-sensitive/case-insensitive/ in comment about nasty indexing 2004-06-21T00:28:44+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2004-06-21T00:28:44+00:00 765012cad1a36c9bb3094c66d055a3b612e4c3a2 hack. [originally from svn r4311] 
hack.

[originally from svn r4311]
Moderately nasty workaround for the fact that Windows Help's index 2004-06-19T16:04:39+00:00 Simon Tatham anakin@pobox.com 2004-06-19T16:04:39+00:00 88cfb9065852d17c763d025c4f720f356c313259 mechanism is case-insensitive with respect to sorting the list of index entries. We now append nonbreaking spaces to the ends of some index terms to ensure they are considered distinct. (Nasty, but it seems to work.) [originally from svn r4294] 
mechanism is case-insensitive with respect to sorting the list of
index entries. We now append nonbreaking spaces to the ends of some
index terms to ensure they are considered distinct. (Nasty, but it
seems to work.)

[originally from svn r4294]
Switch the memory allocation macros from the Halibut ones 2004-06-12T20:31:03+00:00 Simon Tatham anakin@pobox.com 2004-06-12T20:31:03+00:00 a5d800d080a9eb557082042216636ac872eac7ec (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] 
(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]
Character-set-isation and configurability in the WinHelp backend. 2004-05-23T13:20:27+00:00 Simon Tatham anakin@pobox.com 2004-05-23T13:20:27+00:00 2c2cc2260f9302ed2a32d5cd6116d7e7a2f097cf Newly configurable things are: bullet and quote characters as usual, the ": " that goes between a section number and its title, the "." coming after numbered-list item numbers, and the text "Title page" that appears at the top of the .cnt file. [originally from svn r4248] 
Newly configurable things are: bullet and quote characters as usual,
the ": " that goes between a section number and its title, the "."
coming after numbered-list item numbers, and the text "Title page"
that appears at the top of the .cnt file.

[originally from svn r4248]
Kurt Jung points out that nav menus ought to be WHLP_PARA_SCROLL, 2004-05-16T14:18:24+00:00 Simon Tatham anakin@pobox.com 2004-05-16T14:18:24+00:00 8cb73f279cc311f22c2c3ff82358f42ed13420a4 not _NONSCROLL. [originally from svn r4228] 
not _NONSCROLL.

[originally from svn r4228]