Hi Bill, On 11/10/2015 11:40 AM, Bill Somerville wrote: > On 10/11/2015 18:13, KI7MT wrote: >> Hi Bill, > Hi Greg, >> >> I've run into a couple snags as well. On 14.04, the repo version of >> Asciidoctor is v1.4.1. The gem version is v1.5.3. >> >> * First snag >> 1.4.1 does not generate the manpages, where 1.5.3 does, but 1.5.3 does >> does not like the multiple manpage spawning. e.g. 3 or 4 manpages from >> one. Asciidoc handled that no problem. I didn't see this at first as I >> installed via the gem method initially while following their install >> instructions. > Yes the .so or multiple manpages from a single source seems to be a > complete omission from asciidoc :( That is a bit of a nuisance but I > could duplicate the manpages as a brute force fix but see below. >> >> * Second snag >> v1.4.1 does not support LaTeX math ( :stem: latexmath ) or even >> asciimath. Reading the their release notes, that looks to have been >> added at the 1.5.x version time frame. > The stem support is probably not that serious for WSJT-X although I > suspect that some formulae may be nice in the appendices as the document > matures.
Yes, agreed, just thought it would be nice for Joe, as he's used expressions in other PDF's he generated. >> >> Ubuntu 14.04 and 15.04 have v1.4.1 in the repo package >> Ubuntu 15.10 and 16.05 have 1.5.3 >> >> * To install the gem, for resting: >> sudo apt-get remove asciidoctor >> sudo gem install asciidoctor >> exec $SHELL -l >> >> The last command just refreshes the shell, closing / re-opening would do >> the same thing. > That's fine for testing but given that the main manpage requirement is > for build hosts we seem to be screwed. Yup. Worst case, I can create a PPA for v1.5.x for Trusty and Vivid, then require the PPA for builds. >> >> I think it's worth the change as well, but, it may be wise to hold off >> the formal switch until after the v1.6.0 release, unless of course, the >> repo version in Ubunto gets updated to v1.5, or I can use the Wily >> packport some how. > How about we stick with a2x for the manpages for now and switch to > asciidoctor for the User Guide, at least that way we can have better > book generation until the next LTS Ubuntu release when we can drop 14.04 > support. By then the asciidoctor manpage back end might be more capable. Works for me, we only need manpages for *Nix anyway. and that would resolve the Python2 / Python3 situation for Windows at least, which is a real PITA. I like Python, but really hate the Py3 / Py2 incompatability. >> >> Everything seems to be working OK on Windows, that's because the Gem >> version installed was v1.5.3 right out the gate. > For WSJT-X builds on Windows the manpage generation is not done so there > is no show stopper there that I see at present. We do build the manpages > on OS X with aa2x but at least there we have the latest asciidoctor > available. Yeah, that sounds good to me too. I'm not sure about Mac and what version of Asciidoctor it's using, may or may not be a problem for them, but I think sticking with A2x manpage generation is probably the best bet for for now. I can do a similar thing for WSJT / WSPR docs. I may just generate the manpages manually for them and overt the whole generation process, as they don't get much attention anyway, but I really want to "get divorced from Python2" :-) >> >> >> 73's >> Greg, KI7MT > 73 > Bill > G4WJS. 73's Greg, KI7MT >> >> >> On 11/10/2015 05:13 AM, Bill Somerville wrote: >>> On 08/11/2015 19:18, Greg Beam wrote: >>>> you use the same name to build man pages >>>> also ( asciidoctor -b manpage 12345.1.txt ). >>> Hi Greg, >>> >>> I am doing the necessary changes to use asciidoctor with WSJT-X. It is >>> not quite as seamless as it should be but the benefits definitely seem >>> worth the pain. >>> >>> I am finding that asciidoctor manpage backend available in the Ubuntu >>> 14.04 LTS is not working so I don't think using it for manpages is yet >>> feasible. What version of asciidoctor are you using to get manpage >>> generation? >>> >>> Currently I am holding off committing my changes as I know Joe is busy >>> doing User Guide updates and I do not want to disrupt that. >>> >>> 73 >>> Bill >>> G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
