From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/29688 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" Newsgroups: gmane.text.pandoc Subject: Re: How is --toc supposed to work with ms output? Date: Sun, 5 Dec 2021 22:11:41 -0800 (PST) Message-ID: References: <087f1f46-16b4-480b-ad78-0b50cabac705n@googlegroups.com> <67a01480-0d92-4846-bb35-e5f49a80ebb5n@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_8804_1929060741.1638771101960" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="660"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBDX2TPNZVQNBBH6TW2GQMGQETD4KPWY-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mon Dec 06 07:11:46 2021 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oi1-f191.google.com ([209.85.167.191]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mu7E1-000AcM-TY for gtp-pandoc-discuss@m.gmane-mx.org; Mon, 06 Dec 2021 07:11:45 +0100 Original-Received: by mail-oi1-f191.google.com with SMTP id s8-20020aca5e08000000b002b3dd17652csf7473362oib.3 for ; Sun, 05 Dec 2021 22:11:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=OY2nOEEQA8moVbq3BHs1CwbDthAkRCW0LXQHyEHsx/s=; b=GuzBF7Jn9Ixj7mCy47WrMBMBZLzM1Cy1pSBA42DOvof4e4sK918XwCWbL1aRTmMhbu qgWZqhX+b/kwdMLtO25XxSCsVlOJICGW83kUN94rH3hx90iravspH+ndiaABMDqEsI7U bMU0iFYz0/H55vaofmMAHGydZD/qG556pRqeaWwL3W8dDa84p3Pd9qhLVPBnnEKIysQf y2f/CQN/LakVQchR33k6uOVCii4fQh+qc2JUL9PxNlHSmKxbyqcm9vgdYyrrtgZ6QSQ9 gAWR8P/eQx8srdVeb0uW/YteIGdke8D7l+vh1Dfdv9nqTDJibZn8XqI06aQRZGAfkGeZ 0Ggw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=OY2nOEEQA8moVbq3BHs1CwbDthAkRCW0LXQHyEHsx/s=; b=eigADbJYrUJbVmhKwvT2VqGsXu29GFgGCDePOBTVe5Aws1GCO4nKq+AvSbtW/xHV7v oPZ89ZIIgWrpkLCUym7u5Xua2Lhldx1ACFZnnFjd82WCeslpKsFBKrZ0yHhCIk7pijGV axw7mkpfgV854ngFDF6jjMZ6iY0Oyfny6EJoFimc4HnyUC2Hz+TRy+1E9y+/hrkYY4Qt t+dHMGuhYATQ6N7l1okArLSSSYD53q1rTnGwtwYeOh8AVIdqjrtoFZeOGuapw0so+zdX hTdNoeX0Q+xgz/4Mecw2SlR/+o/NuQ+QMwbnaayI+FCLP6zxTtU2MigNeUk1agHQGPav fUNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=OY2nOEEQA8moVbq3BHs1CwbDthAkRCW0LXQHyEHsx/s=; b=utBsuzdrC68c8WXfOdj/PDFOyd41NhXSiBMq6KjlCEN5AmUshR9Vi47RP7/tC4sFBu +AdnCKzxTD4yI7LRG1U4OKFmdyecwarzah4Lz4g1UHQPI06dg7ktee3fvGe2EfnrP4DC U0lKZQZ1Cd+1E1J9LJV6YXh2EZ75PVuOnQBQ20OQiy8/8ffQlckTHNPJZQbTBsIYpBSj NoAUlLt8WhhUBbz1xoPvH+EMX4fZghHuLMBky+rnmAPwq7c/OVTW7RY4TVqr945KmiTj jObRfFfdJDlyLKOVMJ3FPvze4uEpq+tOAt8qZ1W/nK4ppfWzLf74L6NZLOVpKvAU292i /qrQ== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AOAM532Xn39aZ45JuOKlaYJyREc35rTA9ceo9vwr/IJEhf6O1ye4dWJL q1fIdEx7HN14zPDTT6AZjK8= X-Google-Smtp-Source: ABdhPJy+laacSaoP7P+P4ToIRRc4yW5yINRC94Rj+6toly2+REw12My3TNBcrbf0SyjsxoO6/QkhnA== X-Received: by 2002:a05:6808:114f:: with SMTP id u15mr4933969oiu.74.1638771104496; Sun, 05 Dec 2021 22:11:44 -0800 (PST) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:6830:3499:: with SMTP id c25ls5355924otu.4.gmail; Sun, 05 Dec 2021 22:11:42 -0800 (PST) X-Received: by 2002:a9d:490c:: with SMTP id e12mr28027409otf.90.1638771102615; Sun, 05 Dec 2021 22:11:42 -0800 (PST) In-Reply-To: X-Original-Sender: jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:29688 Archived-At: ------=_Part_8804_1929060741.1638771101960 Content-Type: multipart/alternative; boundary="----=_Part_8805_2011098641.1638771101960" ------=_Part_8805_2011098641.1638771101960 Content-Type: text/plain; charset="UTF-8" Il giorno sabato 4 dicembre 2021 alle 14:46:44 UTC-6 tkur...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ha scritto: > The pdfroff program is supposed to handle multiple passes of groff to > produce and combine table of contents and body text in the order expected > by those not familiar with groff (and troff), that is contents first, then > body text. For those not familiar with troff, by itself doesn't do > multiple passes when building the document, so it traditionally produced > the table of contents at the end of the document, after it had collected > all the section titles and their page numbers. Since output primarily to > paper originally, it was easy to manually move the piece or pieces of paper > with the table of contents up to the right spot in the document. > > It occurred to me that the way to avoid this weird behavior was to use the documented option to disable the double pass mechanism, and it worked. pandoc -t ms --pdf-engine-opt --no-toc-relocation -No manual.pdf manual.txt I guess the other behavior was designed with titlepages in mind, while the default document type in pdf/groff puts titles on the first document page. So it seems to me that this switch must be added to the command line call to pdfgroff to produce an output consistent with standard groff. Besides, there may be a way to add or remove support for titlepages, just as in *LaTeX. I may try to do that to the ms template in a couple of days in a fork. > I've not used pdfroff myself (despite having used troff extensively from > before there was a groff), so I wasn't sure what the combination of pandoc > and groff were supposed to produce in this case, but found the blank page > and the two pages being numbered 1 surprising, and thought someone might > know off hand what to expect here. > > I think I just have figured it out. > I should at some point read the pdfroff man page in detail and figure out > what it's normal use produces and then figure out what is happening in this > case with the pandoc output, but I'm suffering from an extreme lack of > round tuits, though not interest, right now. > > I have a working hypothesis it -_o Cheers! -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ba4cdd48-2209-4951-a61a-5f200593fab0n%40googlegroups.com. ------=_Part_8805_2011098641.1638771101960 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I= l giorno sabato 4 dicembre 2021 alle 14:46:44 UTC-6 tkur...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ha sc= ritto:
The pdfroff program is supposed to handle multiple passes of grof= f to produce and combine table of contents and body text in the order expec= ted by those not familiar with groff (and troff), that is contents first, t= hen body text.   For those not familiar with troff, by itself doe= sn't do multiple passes when building the document, so it traditionall= y produced the table of contents at the end of the document, after it = had collected all the section titles and their page numbers.  Since ou= tput primarily to paper originally, it was easy to manually move the piece = or pieces of paper with the table of contents up to the right spot in the d= ocument.


It occurred t= o me that the way to avoid this weird behavior was to use the documented op= tion to disable the double pass mechanism, and it worked.

pandoc -t ms --pdf-engine-opt --no-toc-relocation -No manual.pdf ma= nual.txt

I guess the other behavior was designed w= ith titlepages in mind, while the default document type in pdf/groff puts t= itles on the first document page.

So it seems to m= e that this switch must be added to the command line call to pdfgroff to pr= oduce an output consistent with standard groff.

Be= sides, there may be a way to add or remove support for titlepages, just as = in *LaTeX. I may try to do that to the ms template in a couple of days in a= fork.
 
I've not used pdfroff myself (despite = having used troff extensively from before there was a groff), so I wasn't s= ure what the combination of pandoc and groff were supposed to produce in th= is case, but found the blank page and the two pages being numbered 1 surpri= sing, and thought someone might know off hand what to expect here.


I think I just hav= e figured it out.
 
I should at some poin= t read the pdfroff man page in detail and figure out what it's normal use p= roduces and then figure out what is happening in this case with the pandoc = output, but I'm suffering from an extreme lack of round tuits, though not i= nterest, right now.

I have a working hypothesis i= t  -_o

Cheers!

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d= /msgid/pandoc-discuss/ba4cdd48-2209-4951-a61a-5f200593fab0n%40googlegroups.= com.
------=_Part_8805_2011098641.1638771101960-- ------=_Part_8804_1929060741.1638771101960--