Re: pdfroff invalid argument on cygwin

["jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

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



On Tuesday, 24 November 2020 at 12:03:08 UTC-6 John MacFarlane wrote:

> "jlr..." <jlr...> writes: 
>
> > --verbose reports, on -t ms 
> > 
> > [makePDF] Command line: 
> > pdfroff "-ms" "-mpdfmark" "-mspdf" "-e" "-t" "-k" "-KUTF-8" "-i" 
> > 
> > while on -t latex 
> > 
> > [makePDF] Command line: 
> > pdflatex "-halt-on-error" "-interaction" "nonstopmode" 
> "-output-directory" 
> > "./tex2pdf.-573d55defdd5e31a" "./tex2pdf.-573d55defdd5e31a/input.tex" 
> > 
> > So somehow the command line seems to be incomplete for the -ms option: 
> it 
> > does not point to the input source. 
>
> It's functioning as a pipe in this case; pandoc sends the text 
> of the source file to stdin in the process. 
>
> These options are exactly what I see, and it works fine for me. 
> So I'm at a loss. 
>
>
 After a bit of research, it seems that indeed the problem is the call to 
the system to process pandoc's output through stdin: windoze is infamous 
for that; since the other processors go through temporary files, the output 
call proceeds flawlessly, as the cmd shell has an input file to find.

So perhaps the only solution, not the workaround, is to ask pdfroff to 
process a tmp file generated by pandoc, as other pdf-engines do. Not as 
elegant as calling the pipe, but probably more portable.

With my apologies,

-- 
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/8db6b0f8-d31c-451f-8ada-0abdbc240474n%40googlegroups.com.

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