On Thu, Sep 26, 2013 at 8:59 AM, Steve Rowe <sar...@gmail.com> wrote: > > I'll try to do them all myself, but if it looks like it's going to take more > than one day, I'll ask for help. >
OK, let me know. > > I'll take a look at the CSS - this is the one, right?: > <https://cwiki.apache.org/confluence/spaces/flyingpdf/viewpdfstyleconfig.action?key=solr> > > About the interim HTML, I found this description of how to get it: > <https://confluence.atlassian.com/display/CONF35/Exporting+Confluence+Pages+and+Spaces+to+HTML>. My first reaction was that it wouldn't work: The HTML export exports the selected pages into a .zip file of HTML files (one file for each wiki page). The interim-HTML for the PDF is one big single HTML file. They're different exports, using different stylesheets. However, it would make sense if the HTML was similar, so I took a look with my own Confluence instance and the two exports use many of the same divs for the same elements. It's not 1:1, but you could at least figure out what the right divs are. The big difference will be heading levels - the PDF flattens them all depending on the page hierarchy. There are also CSS' in place that you don't see and default rules that are applied if you haven't overridden them. And then I also think there are some styles put into the HTML itself that would override anything in the CSS. A few weeks ago I was working on a number of possible changes to the PDF, the formatting of code samples being one of them, but after two days working on it, I gave up for now. It really isn't fun to work on. > >>> 1. Pg 2: The section links from the TOC all take you to the previous page, >>> rather than to the top of the page where the section starts. (Same >>> behavior on OS X Preview, and under Windows, on Firefox's built-in PDF >>> viewer and on Adobe Reader.) This looks like a general problem - see e.g. >>> #34. >> >> CT: This is essentially a known problem (see my comment: >> https://issues.apache.org/jira/browse/SOLR-4886?focusedCommentId=13703660#comment-13703660, >> last bullet point). The way the PDF is created is that Confluence >> creates the entire document in an HTML page, which include bookmark >> tags right before the different heading levels. When the PDF is then >> generated, a rule is applied to insert a page-break before all h2 >> headings. That leaves the bookmark orphaned on the previous page. I >> have never found a solution to this problem - you can't edit the HTML >> and you don't have any control over where the bookmark tags in the >> HTML are put before the HTML is converted to PDF. The only solution is >> to never have page breaks, which I think severely diminishes >> readability. > > Thanks for the explanation. I agree about page breaks being more important > than off-by-one-page link targets. I wonder if there is some CSS trick to > put the page break before the target <a> instead of the <h2> section. > >>> 2. Pg 68: Stray asterisks in the <analyzer> tags in the <fieldType> example >>> under "Analysis Phases", apparently to make the surrounded text bold (which >>> also didn't happen). >> >> CT: BTW, it never will - code examples are rendered verbatim, without >> any of the styling normally applied. > > Hmm, so there's no way to apply any formatting at all? That's too bad. You can apply syntax formatting based on the language of the example, but not inline formatting to highlight specific lines - one way I've gotten around that in other places is to enable line numbers to display in the example, and then call out the line numbers in the text. Cassandra --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
