| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
look less as if they're the _only_ config options.
[originally from svn r8842]
|
| |
|
|
| |
[originally from svn r7178]
|
| |
|
|
|
|
|
| |
commands, allowing the fixed words "Contents" and "Index" generated
in various output formats to be reconfigured into other languages.
[originally from svn r6724]
|
| |
|
|
|
|
|
|
|
| |
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 r5338]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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]
|
| |
|
|
|
|
|
| |
the practice of using \dt and \dd in anything other than the obvious
interleaving.
[originally from svn r4417]
|
| |
|
|
|
|
| |
shorthand command \cq{foo}.
[originally from svn r4327]
|
| |
|
|
|
|
| |
can't be changed partway through. Also, add a cross-reference from \q{}.
[originally from svn r4298]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- \cfg{quotes}
- text, info, man, and winhelp backends:
- charset
- quotes and bullets
- various WinHelp miscellanea
Could stand some rearrangement and expansion, plus I've yet to address the
paper or HTML backends.
[originally from svn r4295]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 r4278]
|
| |
|
|
|
|
| |
better remove the one too-long code line in the manual :-)
[originally from svn r4129]
|
| |
|
|
| |
[originally from svn r4106]
|
| |
|
|
|
|
|
| |
8859-*, UTF-8, or a variety of more fun encodings including various
multibyte ones.
[originally from svn r4095]
|
| |
|
|
|
|
|
|
| |
Halibut is now capable of reading the old NASM manual with only
minor modifications, and probably doing a much better job of
formatting it than rdsrc.pl ever did. (Certainly much _faster_!)
[originally from svn r4081]
|
| |
|
|
|
|
|
|
| |
collection of minor edits for clarity, and also quite a few intended
to keep down the length of lines in code paragraphs (because Courier
is not just a thoroughly ugly font but is also WAY TOO WIDE).
[originally from svn r4076]
|
| |
|
|
|
|
| |
manual. Added them.
[originally from svn r4038]
|
| |
|
|
|
|
|
| |
consistently in the documentation than to confuse matters by saying
`back end'. One rogue back end removed.
[originally from svn r4028]
|
| |
|
|
|
|
|
|
|
| |
the preamble: \copyright paragraphs are now treated identically to
normal paragraphs (so they appear precisely where they're put
instead of in a fixed location), _except_ that the Windows Help
backend also copies their text into the help file's copyright slot.
[originally from svn r4001]
|
| |
|
|
|
|
| |
so. It's restorable using \IM.
[originally from svn r4000]
|
| |
|
|
| |
[originally from svn r3999]
|
| |
|
|
|
|
|
| |
Jacob points out that I didn't specify whether inline formatting
commands can surround line breaks (they can).
[originally from svn r3994]
|
| |
|
|
|
|
|
|
| |
I _think_ the manual now contains all the information a user should
need, even if not yet in an optimal order for a beginner to learn
from.
[originally from svn r3989]
|
| |
|
|
|
|
|
|
|
| |
zero-width delimiter between a macro invocation and text beyond it,
so that you can define (say) a macro which expands to a Euro sign
and then write `\eur\.2500' to avoid having space between the Euro
sign and the number.
[originally from svn r3982]
|
| |
|
|
|
|
|
|
|
|
| |
any ordinary displayable paragraph(s) appearing before the first
chapter heading, meaning in particular that you can put lists, code
paragraphs etc in preambles. Of course, `\preamble' is still
supported for backwards compatibility, but it's now a zero-effect
paragraph marker.
[originally from svn r3981]
|
|
|
(nearly nonexistent) invocation syntax and the input format.
[originally from svn r3979]
|
