public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mouse Mousevich <uri-OVIABD91gjs3uPMLIKxrzw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting Rust-book to PDF fails
Date: Wed, 1 Feb 2023 13:31:03 -0800 (PST)	[thread overview]
Message-ID: <14cb0323-74ae-4368-b843-2fd8831b6e2cn@googlegroups.com> (raw)
In-Reply-To: <e52155b1-2b00-4cee-8816-53906072ede7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2669 bytes --]

xelatex gives a bit more meaningful message - though I still don't 
understand how to remedy this:

[13]

! Missing number, treated as zero.

<to be read again> 

                   (

l.306 \begin

            {minipage}[b]{\linewidth}\raggedright

?

On Wednesday, February 1, 2023 at 4:22:05 PM UTC-5 Mouse Mousevich wrote:

> pandoc-2.19.2, pdflatex from TeXLive-2022.
> Rust-book set of .md files from 
> https://github.com/killercup/trpl-ebook.git (version from 2016).
>
> Conversion to LaTeX seems to succeed, but subsequent invocation of 
> pdflatex fails.
>
> I printed out arguments passed to pandoc:
>
> pandoc args: 
> --from=markdown+smart+grid_tables+pipe_tables-simple_tables+raw_html+implicit_figures+footnotes+intraword_underscores+auto_identifiers-inline_code_attributes 
> --embed-resources --standalone --highlight-style=tango 
> --top-level-division=chapter --table-of-contents 
> --template=lib/template.tex --pdf-engine=pdflatex --to=latex 
> --pdf-engine-opt=--interaction=nonstopmode --variable papersize=letterpaper 
> --output=dist/trpl-2019-05-04.letter.pdf; plus book itself
>
> Error message from pdflatex:
>
> Error producing PDF.
>
> ! Missing number, treated as zero.
>
> <to be read again> 
>
>                    (
>
> l.306 \begin
>
>
> This is what the (apparently) relevant fragment of the LaTeX file looks 
> like:
>
> 299   │ \begin{longtable}[]{@{}
>
>  300   │   >{\raggedright\arraybackslash}p{(\columnwidth - 8\tabcolsep) * 
> \real{0.4189}}
>
>  301   │   >{\raggedright\arraybackslash}p{(\columnwidth - 8\tabcolsep) * 
> \real{0.0676}}
>
>  302   │   >{\raggedright\arraybackslash}p{(\columnwidth - 8\tabcolsep) * 
> \real{0.0676}}
>
>  303   │   >{\raggedright\arraybackslash}p{(\columnwidth - 8\tabcolsep) * 
> \real{0.0676}}
>
>  304   │   >{\raggedright\arraybackslash}p{(\columnwidth - 8\tabcolsep) * 
> \real{0.3784}}@{}}
>
>  305   │ \toprule()
>
>  306   │ \begin{minipage}[b]{\linewidth}\raggedright
>
>  307   │ Target
>
>  308   │ \end{minipage} & \begin{minipage}[b]{\linewidth}\raggedright
>
>  309   │ std
>
>  310   │ \end{minipage} & \begin{minipage}[b]{\linewidth}\raggedright
>
>
>

-- 
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/14cb0323-74ae-4368-b843-2fd8831b6e2cn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3643 bytes --]

  parent reply	other threads:[~2023-02-01 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 21:22 Mouse Mousevich
     [not found] ` <e52155b1-2b00-4cee-8816-53906072ede7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-01 21:31   ` Mouse Mousevich [this message]
     [not found]     ` <14cb0323-74ae-4368-b843-2fd8831b6e2cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-01 22:40       ` Duncan Murdoch
2023-02-01 23:02   ` John MacFarlane
     [not found]     ` <746F5C2D-BD17-4509-9EB5-3B2D5646AD73-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-02 18:56       ` Mouse Mousevich
     [not found]         ` <9a28d0fa-22da-49b8-a284-731a960473e9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-02 19:35           ` Mouse Mousevich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14cb0323-74ae-4368-b843-2fd8831b6e2cn@googlegroups.com \
    --to=uri-oviabd91gjs3upmlikxrzw@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).