From 36729bdb2a121206f8049bb72edc1fed62f7803c Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Thu, 22 May 2008 15:26:58 -0700 Subject: [PATCH] Reduce headers by one level --- src/cairo/a_chain_of_bugs.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/cairo/a_chain_of_bugs.mdwn b/src/cairo/a_chain_of_bugs.mdwn index 10dd287..8b52b69 100644 --- a/src/cairo/a_chain_of_bugs.mdwn +++ b/src/cairo/a_chain_of_bugs.mdwn @@ -11,7 +11,7 @@ like. I recently received a bug report that Firefox 3 (using cairo reveals at least three independent problems that conspire to give the bad results. -# Bug 1: Firefox+cairo uses image fallbacks for table borders +## Bug 1: Firefox+cairo uses image fallbacks for table borders First, here's the simplest web page I was able to construct to show the problem, (nothing more than a single-cell table with a border): @@ -35,7 +35,7 @@ Also, note that when cairo puts the fallback images into the PDF file it uses a "knockout group" to do so. This is a particular PDF construct that I'll discuss later. -# Bug 2: Poppler+cairo expands knockout groups to full-page fallbacks +## Bug 2: Poppler+cairo expands knockout groups to full-page fallbacks Next, we can use the poppler library, (with evince or a pdf2ps utility), to read the PDF file and use cairo to generate a PostScript @@ -68,7 +68,7 @@ fix poppler to recognize this case and ask for the simple thing from cairo's PostScript backend so that we don't get this full-page fallback explosion. -# Bug 3: Cairo uses the wrong resolution for fallback images (in groups) +## Bug 3: Cairo uses the wrong resolution for fallback images (in groups) If it were only for those first two bugs, the intermediate file sizes would have been larger than normal, but the final result would have -- 2.43.0