summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Harris <bjh21@bjh21.me.uk>2007-01-06 16:05:28 +0000
committerBen Harris <bjh21@bjh21.me.uk>2007-01-06 16:05:28 +0000
commit405e47cacdc61ac61b421591dfb92434ebffaeb9 (patch)
treec2296699b5b15a532dccf25489f0a5f7ac74d886
parent7fad3e54e8eb9fd3e894208b8b8ba2db982bf77a (diff)
downloadhalibut-405e47cacdc61ac61b421591dfb92434ebffaeb9.zip
halibut-405e47cacdc61ac61b421591dfb92434ebffaeb9.tar.gz
halibut-405e47cacdc61ac61b421591dfb92434ebffaeb9.tar.bz2
halibut-405e47cacdc61ac61b421591dfb92434ebffaeb9.tar.xz
I've worked out why ligation was being (correctly) suppressed in code
paragraphs and found some cases where it isn't. Add test cases for these to remind me to deal with them later. [originally from svn r7060]
-rw-r--r--inputs/test.but7
1 files changed, 7 insertions, 0 deletions
diff --git a/inputs/test.but b/inputs/test.but
index 72f8719..04ac8e6 100644
--- a/inputs/test.but
+++ b/inputs/test.but
@@ -244,6 +244,13 @@ 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.
+
+\c Also in a code paragraph (fi) with bold (fi) and italic (fi).
+\e bb ii
+\c There should be no ligation there.
+
\S{subhead} First subheading
So here's a \I{subheading}\I{subsection}subsection. Just