halibut/doc/input.but, branch master My halibut tree Mention \s in a section title. 2016-01-22T00:21:26+00:00 Simon Tatham anakin@pobox.com 2016-01-22T00:21:26+00:00 a9363f975f0c5faf6767ee53df737c3cf3c40151 A user points out that that recently added markup feature is easy to miss because it's not as prominently documented as it should be. 
A user points out that that recently added markup feature is easy to
miss because it's not as prominently documented as it should be.
Remove Subversion expanded keywords everywhere. 2014-09-24T10:32:41+00:00 Simon Tatham anakin@pobox.com 2014-09-24T10:32:41+00:00 aa2709b2fdd600b9300c52eb534d13672a572239 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] 
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]
Index term tweaks in manual for \s to quell warnings when building, etc. 2013-03-23T19:46:15+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2013-03-23T19:46:15+00:00 6154b5b53a342d6cf1aa3fc38e28405975f64e00 [originally from svn r9774] 
[originally from svn r9774]
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]
Clarify the section about backend-generic config options to make it 2010-01-14T19:01:36+00:00 Simon Tatham anakin@pobox.com 2010-01-14T19:01:36+00:00 70c9bbe29108065fdf1449e8b7b8b989d9bde36b look less as if they're the _only_ config options. [originally from svn r8842] 
look less as if they're the _only_ config options.

[originally from svn r8842]
Use consistent capitalisation for HTML tags. 2007-01-28T18:42:50+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2007-01-28T18:42:50+00:00 64f71c43291cdb469d4fbe2d70dccc9b4b768537 [originally from svn r7178] 
[originally from svn r7178]
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]
Add a `--list-charsets' option to Halibut to enumerate canonical names of known 2005-02-18T13:17:28+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2005-02-18T13:17:28+00:00 1fa5a06bb8ef61eb1a736641138221b1dc16b49e character sets. (Also make libcharset `return_in_enum' values saner.) [originally from svn r5341] [this svn revision also touched charset,filter,timber] 
character sets.

(Also make libcharset `return_in_enum' values saner.)

[originally from svn r5341]
[this svn revision also touched charset,filter,timber]
Add \versionid. 2005-02-17T22:20:32+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2005-02-17T22:20:32+00:00 f832d3e02171bb43e3ba9e4330257e4e9de2128c [originally from svn r5338] 
[originally from svn r5338]
Changes/additions to input character set handling: 2005-02-17T19:00:48+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2005-02-17T19:00:48+00:00 45dd6bf764064c3b2a9f087d8206179f514638ac - After discussion with Simon, change the default input charset back to ASCII, rather than trying to work it out from the locale, for the sake of promoting .but file portability. - Add a new command-line option "--input-charset=csname", which overrides the ASCII default for all input files (since there's no other way to use a non-ASCII-compatible input file). - Output a warning if -Cinput-charset:foo is specified that it has no effect. - Update the docs to match all this. Also try to clarify some other things in this area that caught me out. [originally from svn r5332] 
 - After discussion with Simon, change the default input charset back to ASCII,
   rather than trying to work it out from the locale, for the sake of promoting
   .but file portability.

 - Add a new command-line option "--input-charset=csname", which overrides the
   ASCII default for all input files (since there's no other way to use a
   non-ASCII-compatible input file).

 - Output a warning if -Cinput-charset:foo is specified that it has no effect.

 - Update the docs to match all this. Also try to clarify some other things in
   this area that caught me out.

[originally from svn r5332]