public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Ulrich Hasecke <juh+pandoc-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to Use a LaTeX Document Class?
Date: Wed, 28 Jan 2015 08:36:15 +0100	[thread overview]
Message-ID: <54C8916F.1020409@mailbox.org> (raw)
In-Reply-To: <d463db95-5f44-4417-835d-9dfd4c91e574-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Am 28.01.2015 um 02:44 schrieb Dylan Kinnett:
> I am also using the default template.latex file

> This is what the error says:
> 
> |
> !Fileended whilescanning useof \UL@on.
> <inserted text>
>                 \par
> <*>...r_6595rnn9lm0000gp/T/tex2pdf.1962/input.tex
>                                                  
> ! ==>Fatalerror occurred,nooutput PDF file produced!
> |
> 
> Is anyone else able to reproduce these results or point to a possible cause?

I get an error messages with sffms too. The macro seems to be broken. I
can only generate the sample from the sffms website.

\documentclass[submission]{sffms}
    \title{The Hobbit}
    \author{J. R. R. Tolkien}
    \begin{document}
    Your story goes here.
    \end{document}


I can insert a \chapter but when I insert a first \section I get this
error.

Runaway argument?
{{\@hangfrom {\hskip \z@ \relax \@svsec }\interlinepenalty \@M
Hallo\@@par \ETC
.
! File ended while scanning use of \UL@on.
<inserted text>
                \par
<*> manuscript.tex

You should contact the author of sffms.

For submissions you can try the package stdpage which creates a similar
submission style document.
http://www.ctan.org/pkg/stdpage

HTH
juh


-- 
Software-Dokumentation mit Sphinx
http://www.amazon.de/dp/1497448689/
Paperback: 224 Seiten


  parent reply	other threads:[~2015-01-28  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 16:51 Dylan Kinnett
     [not found] ` <6a173c76-af1b-4e01-988d-bcb6372ea422-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-24 17:48   ` Matthew Pickering
2015-01-25  4:09   ` lukshuntim-Re5JQEeQqe8AvxtiuMwx3w
2015-01-26  1:06   ` Dylan Kinnett
     [not found]     ` <20c5629f-c551-41d4-859c-af7c5c58a346-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-26 14:40       ` lukshuntim-Re5JQEeQqe8AvxtiuMwx3w
2015-01-26 18:54         ` Dylan Kinnett
     [not found]           ` <CAByu3gFAqFSTL1dniZVPfxRTZGY43Dn6sNqsQsLzayvGMUGb2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-27 13:17             ` lukshuntim-Re5JQEeQqe8AvxtiuMwx3w
     [not found]               ` <54C79004.6090108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-28  1:44                 ` Dylan Kinnett
     [not found]                   ` <d463db95-5f44-4417-835d-9dfd4c91e574-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-28  7:36                     ` Jan Ulrich Hasecke [this message]
     [not found]                       ` <54C8916F.1020409-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2015-01-28  8:05                         ` Joost Kremers
2015-02-11  1:20                           ` Dylan Kinnett

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=54C8916F.1020409@mailbox.org \
    --to=juh+pandoc-cl+vpiynx/1afugrpc6u6w@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).