public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joost Kremers <joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Missing Number, Treated As Zero
Date: Tue, 09 Jun 2020 01:08:30 +0200	[thread overview]
Message-ID: <87wo4hdukx.fsf@fastmail.fm> (raw)
In-Reply-To: <a9152437-f2b3-45f1-a758-40dec96551d0o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


On Tue, Jun 09 2020, Aaron Lopez wrote:
> Testing the conversion of .epub to pdf and not having much luck. 
> I 
> downloaded a random epub file to test with...
>
> pandoc -f epub -t latex -o mytest.pdf --pdf-engine=pdflatex 
> aliceDynamic.epub --verbose > epub.txt
>
> ! Missing number, treated as zero.
> <to be read again>
>                    \protect
> l.90 ...enter}\rule{0.5\linewidth}{\linethickness}
>                                                   \end{center}
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on C:\tex2pdf.-5080fd875f0b148b\input.log.
>
> Error producing PDF.
> ! Missing number, treated as zero.
> <to be read again>
>                    \protect
> l.90 ...enter}\rule{0.5\linewidth}{\linethickness}
>

The latex macro `\rule` requires two arguments, a length and a 
line thickness. The error message suggests that the macro 
`\linethickness` isn't defined. I'm not sure what could be the 
cause of that, though.

-- 
Joost Kremers
Life has its moments


  parent reply	other threads:[~2020-06-08 23:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 22:36 Aaron Lopez
     [not found] ` <a9152437-f2b3-45f1-a758-40dec96551d0o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-08 22:38   ` Aaron Lopez
2020-06-08 22:40   ` 'Oliver Demetz' via pandoc-discuss
     [not found]     ` <d59f6f6a-1686-4b78-8161-b4b3923be08co-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-08 23:12       ` Aaron Lopez
     [not found]         ` <4b053617-93c3-47c9-a576-607f2dd12942o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-08 23:21           ` Joost Kremers
     [not found]             ` <87o8ptdtz9.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2020-06-08 23:47               ` Aaron Lopez
     [not found]                 ` <939f4e71-b9a6-4d2b-9094-34409f13dcb9o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-09  0:06                   ` Aaron Lopez
     [not found]                     ` <a94be64e-976d-49fb-a805-67dfb4ccab7ao-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-09  0:22                       ` Joost Kremers
     [not found]                         ` <87h7vldr5z.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2020-06-09  6:02                           ` Aaron Lopez
2020-06-08 23:08   ` Joost Kremers [this message]
     [not found]     ` <87wo4hdukx.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2020-06-09  6:07       ` Albert Krewinkel
     [not found]         ` <87d068vkk9.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-06-09 17:22           ` Aaron Lopez

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=87wo4hdukx.fsf@fastmail.fm \
    --to=joostkremers-97jfqw80gc6171pxa8y+qa@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).