diff options
| author | Simon Tatham <anakin@pobox.com> | 2013-03-10 16:58:01 +0000 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2013-03-10 16:58:01 +0000 |
| commit | dcf080aa0e011de37a154e9e8a97dd7546a4a1b1 (patch) | |
| tree | 891d703334a6d4f4899f058234c52d56cb7bdb3b /inputs | |
| parent | 1489dc15967970576d08f3f2b22c6e1c939bcbcf (diff) | |
| download | halibut-dcf080aa0e011de37a154e9e8a97dd7546a4a1b1.zip halibut-dcf080aa0e011de37a154e9e8a97dd7546a4a1b1.tar.gz halibut-dcf080aa0e011de37a154e9e8a97dd7546a4a1b1.tar.bz2 halibut-dcf080aa0e011de37a154e9e8a97dd7546a4a1b1.tar.xz | |
Add \s for 'strong' text, i.e. bold rather than italics. I've missed
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]
Diffstat (limited to 'inputs')
| -rw-r--r-- | inputs/test.but | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/inputs/test.but b/inputs/test.but index dddc2dd..751ec1b 100644 --- a/inputs/test.but +++ b/inputs/test.but @@ -48,7 +48,7 @@ chapter title I can write before feeling silly. This is a para\#{another{} comment}graph of text. It has line\#{yet another one} breaks in between words, multiple - spaces (ignored), and \e{emphasised text} as well as \c{code + spaces (ignored), \e{emphasised text} and \s{strong text} as well as \c{code fragments}. \#{This is an inline comment alone in a paragraph.} @@ -248,8 +248,9 @@ u ú û ü ù _ v w x y ý ÿ ¥ z \u017e 0 \cfg{input-charset}{ASCII} -Testing ligatures in normal (fi), empasised (\e{fi}), code (\c{fi}) and -weak code (\cw{fi}). The latter two should not be ligated. +Testing ligatures in normal (fi), emphasised (\e{fi}), strong +(\s{fi}), code (\c{fi}) and weak code (\cw{fi}). The latter two should +not be ligated. \c Also in a code paragraph (fi) with bold (fi) and italic (fi). \e bb ii @@ -278,6 +279,11 @@ Similarly, we should support things like hyperlinks and \e{in the \W{http://www.tartarus.org/}{middle} of them}, and also \e{at the \W{http://home.att.net/~cecw/lastpage.htm}{end}}. +Try that all over against with \c{\\s}: hyperlinks +\s{\W{http://www.tartarus.org/}{at the beginning} of strong sections}, +and \s{in the \W{http://www.tartarus.org/}{middle} of them}, and also +\s{at the \W{http://home.att.net/~cecw/lastpage.htm}{end}}. + Here's a hyperlink containing some special characters: \W{http://a<b&c>d/}{here}. (Not that it'll \e{work}, but you can at least determine that it's been correctly escaped by inspection of |