I forgot to add, if you want a nice TOC that hyperlinks, add the attribute -a toc:
asciidoctor-pdf -a toc ./user_guide/wsjtx-main.adoc -o wsjtx-devel-v1.7.0.pdf The document is 55 pages, but could use some additional page breaks. 73's Greg, KI7MT On 11/19/2015 15:07, Greg Beam wrote: > Hi Bill, Joe > > If we're not going to ship a PDF with the package, Asccidoctor has a > module that can be installed via gem to generate PDF's. It's > implementation is not 100% yet, but it's working for v1.7.0. This > "should" also work for the v1.6.0-RC version. > > To install / test: > > * open JTSDK-QT > gem install --pre asciidoctor-pdf > > Then to build a PDF, you can either call asciidoctor or asciidoctor-pdf: > > Examples: > > asciidoctor -r asciidoctor-pdf -b pdf ./user_guide/wsjtx-main.adoc -o > wsjtx-devel-v1.7.0.pdf > > or > > asciidoctor-pdf ./user_guide/wsjtx-main.adoc -o wsjtx-devel-v1.7.0.pdf > > > I built the current v1.7.0 user-guide, it look OK to me, and I did not > see any broken syntax. > > Obviously, building directly will not perform the variable expansion > that CmakeList.txt provides, but it is a method for quick looks and things. > > > 73's > Greg, KI7MT > > > On 11/19/2015 14:43, Bill Somerville wrote: >> On 19/11/2015 14:24, Joe Taylor wrote: >>> The default font size is considerably larger than the one used in our >>> previous Asciidoc builds. I think it's too big. >>> >>> One measure: as formatted for printing, the User guide is now 71 pages >>> compared with 42 pages with Asciidoc. Some of this may be a result of >>> having made better page breaks, thus leaving more empty space at bottom >>> of some pages. But I'd like to see how it looks with somewhat smaller >>> fonts. >> Hi Joe, >> >> there are no absolute font sizes in the style sheet, nor were there with >> the old asciidoc style sheet. All the font sizes are relative to the >> body element font which itself is specified as 100%. That means the >> browser defaults are actually controlling the rendered font sizes. >> >> When you say "formatted for printing" do you mean using your browser's >> print function? If I do that in Firefox using CutePDF writer as an >> output device I get awful font rendering. The PDFs you have posted are a >> bit better but the fonts still look pretty poor. If we want a PDF >> rendering of the User Guide it would be better to have the build script >> use asciidoctor to generate a DocBook XML file and feed that to a decent >> DocBook XML to PDF converter, that way we would have a working TOC etc.. >> >> I have changed the controlling font size to 90%, here is a sample >> (includes a few tweks to get better PDF formatting): >> >> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.html >> >> I have also sorted out proper PDF generation in the CMake script, it is >> optional and only works when the relevant tools are installed >> (asciidoc-fopub). Here is a sample: >> >> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.pdf >> >> I envisage generating a PDF version of the User Guide for access from >> the project web site rather then shipping it with the application. >> >> Comments? >> >> 73 >> Bill >> G4WJS. >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
