public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
* pdf-engine pdflatex not known - windows, miktex portable
@ 2018-01-03 12:03 'K' via pandoc-discuss
       [not found] ` <54e1c2fd-4777-4f44-b956-0dcc73c2b832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: 'K' via pandoc-discuss @ 2018-01-03 12:03 UTC (permalink / raw)
  To: pandoc-discuss


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

Hi,

I'm using portable Versions of pandoc and miktex on a Windows System. With 
pandoc 1.19.2.1 converting a markdown-File to PDF runs fine - the used 
commandline looks like this:

D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf --latex-engine=D:\
LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc docs\file.md

After upgrading pandoc to 2.0.6 I have to change the parameter 
--latex-engine to --pdf-engine. The new commandline that would be used was 
this:

D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf --pdf-engine=D:\LaTeX\
MiKTeX_2.9\miktex\bin\pdflatex.exe --toc docs\file.md

Following is the response I get:

pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known

I have updated Miktex, but the result is the same. With 1.19.2.1 the PDF 
will be created.

Thanks for any helpfull advice.
Greetings
Karsten


-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/54e1c2fd-4777-4f44-b956-0dcc73c2b832%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: pdf-engine pdflatex not known - windows, miktex portable
       [not found] ` <54e1c2fd-4777-4f44-b956-0dcc73c2b832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
@ 2018-01-03 18:42   ` John MACFARLANE
  2018-01-04  7:29     ` 'K' via pandoc-discuss
  0 siblings, 1 reply; 6+ messages in thread
From: John MACFARLANE @ 2018-01-03 18:42 UTC (permalink / raw)
  To: 'K' via pandoc-discuss

Generally this would happen if the program is not found
when pandoc tries to run the process. I'm not sure why that
would be.

Try just using --pdf-engine=pdflatex and putting the
relevant directory in your path (perhaps temporarily).

+++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]:
>   Hi,
>   I'm using portable Versions of pandoc and miktex on a Windows System.
>   With pandoc 1.19.2.1 converting a markdown-File to PDF runs fine - the
>   used commandline looks like this:
>   D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf
>   --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
>   docs\file.md
>   After upgrading pandoc to 2.0.6 I have to change the parameter
>   --latex-engine to --pdf-engine. The new commandline that would be used
>   was this:
>   D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf
>   --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
>   docs\file.md
>   Following is the response I get:
>   pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known
>   I have updated Miktex, but the result is the same. With 1.19.2.1 the
>   PDF will be created.
>   Thanks for any helpfull advice.
>   Greetings
>   Karsten
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/54e1c2fd-4777-4f44-
>   b956-0dcc73c2b832%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/54e1c2fd-4777-4f44-b956-0dcc73c2b832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: pdf-engine pdflatex not known - windows, miktex portable
  2018-01-03 18:42   ` John MACFARLANE
@ 2018-01-04  7:29     ` 'K' via pandoc-discuss
       [not found]       ` <0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: 'K' via pandoc-discuss @ 2018-01-04  7:29 UTC (permalink / raw)
  To: pandoc-discuss


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

Thanks for your response.
Because of using it in a batch-file I could temporary change the 
path-variable without a problem and after that it runs smoothly. 
Is pandoc 2 searching for ( / needing) supporting-files from miktex / 
pdflatex? (and version 1.x doesn't do that?)
But that workaround is good enough for me.
Thanks for your quick help.

Am Mittwoch, 3. Januar 2018 19:42:23 UTC+1 schrieb John MacFarlane:
>
> Generally this would happen if the program is not found 
> when pandoc tries to run the process. I'm not sure why that 
> would be. 
>
> Try just using --pdf-engine=pdflatex and putting the 
> relevant directory in your path (perhaps temporarily). 
>
> +++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]: 
> >   Hi, 
> >   I'm using portable Versions of pandoc and miktex on a Windows System. 
> >   With pandoc 1.19.2.1 converting a markdown-File to PDF runs fine - the 
> >   used commandline looks like this: 
> >   D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf 
> >   --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc 
> >   docs\file.md 
> >   After upgrading pandoc to 2.0.6 I have to change the parameter 
> >   --latex-engine to --pdf-engine. The new commandline that would be used 
> >   was this: 
> >   D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf 
> >   --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc 
> >   docs\file.md 
> >   Following is the response I get: 
> >   pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known 
> >   I have updated Miktex, but the result is the same. With 1.19.2.1 the 
> >   PDF will be created. 
> >   Thanks for any helpfull advice. 
> >   Greetings 
> >   Karsten 
> > 
>
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/0fa916f1-8d06-41ca-9d2a-18ca616c37f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: pdf-engine pdflatex not known - windows, miktex portable
       [not found]       ` <0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
@ 2018-01-04 16:27         ` John MacFarlane
       [not found]           ` <20180104162711.GD15709-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: John MacFarlane @ 2018-01-04 16:27 UTC (permalink / raw)
  To: 'K' via pandoc-discuss

I'm not sure why there'd be a difference btw pandoc 1 and 2.
I've looked at the code and nothing is jumping out at me.

+++ 'K' via pandoc-discuss [Jan 03 18 23:29 ]:
>   Thanks for your response.
>   Because of using it in a batch-file I could temporary change the
>   path-variable without a problem and after that it runs smoothly.
>   Is pandoc 2 searching for ( / needing) supporting-files from miktex /
>   pdflatex? (and version 1.x doesn't do that?)
>   But that workaround is good enough for me.
>   Thanks for your quick help.
>   Am Mittwoch, 3. Januar 2018 19:42:23 UTC+1 schrieb John MacFarlane:
>
>     Generally this would happen if the program is not found
>     when pandoc tries to run the process. I'm not sure why that
>     would be.
>     Try just using --pdf-engine=pdflatex and putting the
>     relevant directory in your path (perhaps temporarily).
>     +++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]:
>     >   Hi,
>     >   I'm using portable Versions of pandoc and miktex on a Windows
>     System.
>     >   With pandoc 1.19.2.1 converting a markdown-File to PDF runs fine
>     - the
>     >   used commandline looks like this:
>     >   D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf
>     >   --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
>     >   docs\[1]file.md
>     >   After upgrading pandoc to 2.0.6 I have to change the parameter
>     >   --latex-engine to --pdf-engine. The new commandline that would
>     be used
>     >   was this:
>     >   D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf
>     >   --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
>     >   docs\[2]file.md
>     >   Following is the response I get:
>     >   pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known
>     >   I have updated Miktex, but the result is the same. With 1.19.2.1
>     the
>     >   PDF will be created.
>     >   Thanks for any helpfull advice.
>     >   Greetings
>     >   Karsten
>     >
>
>   --
>   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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [5]https://groups.google.com/d/msgid/pandoc-discuss/0fa916f1-8d06-41ca-
>   9d2a-18ca616c37f2%40googlegroups.com.
>   For more options, visit [6]https://groups.google.com/d/optout.
>
>References
>
>   1. http://file.md/
>   2. http://file.md/
>   3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   5. https://groups.google.com/d/msgid/pandoc-discuss/0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   6. https://groups.google.com/d/optout


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: pdf-engine pdflatex not known - windows, miktex portable
       [not found]           ` <20180104162711.GD15709-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
@ 2018-01-05  7:57             ` 'K' via pandoc-discuss
       [not found]               ` <47a53a1e-9098-459f-b88f-618c6ded03e4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: 'K' via pandoc-discuss @ 2018-01-05  7:57 UTC (permalink / raw)
  To: pandoc-discuss


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

Thanks for caring ... as I see in the posts, the problem is not Windows 
exclusive.
For me the solution with temporary updating the path, is enough. 
It seems, i can't help anymore, because the parameter --trace, 
--log=file.log, --verbose didn't seem to work for me (at least in my 
batch-file), so i can't provide any more information. :(

Thanks for this incredible piece of software.

Am Donnerstag, 4. Januar 2018 17:27:27 UTC+1 schrieb John MacFarlane:
>
> I'm not sure why there'd be a difference btw pandoc 1 and 2. 
> I've looked at the code and nothing is jumping out at me. 
>
> +++ 'K' via pandoc-discuss [Jan 03 18 23:29 ]: 
> >   Thanks for your response. 
> >   Because of using it in a batch-file I could temporary change the 
> >   path-variable without a problem and after that it runs smoothly. 
> >   Is pandoc 2 searching for ( / needing) supporting-files from miktex / 
> >   pdflatex? (and version 1.x doesn't do that?) 
> >   But that workaround is good enough for me. 
> >   Thanks for your quick help. 
> >   Am Mittwoch, 3. Januar 2018 19:42:23 UTC+1 schrieb John MacFarlane: 
> > 
> >     Generally this would happen if the program is not found 
> >     when pandoc tries to run the process. I'm not sure why that 
> >     would be. 
> >     Try just using --pdf-engine=pdflatex and putting the 
> >     relevant directory in your path (perhaps temporarily). 
> >     +++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]: 
> >     >   Hi, 
> >     >   I'm using portable Versions of pandoc and miktex on a Windows 
> >     System. 
> >     >   With pandoc 1.19.2.1 converting a markdown-File to PDF runs fine 
> >     - the 
> >     >   used commandline looks like this: 
> >     >   D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf 
> >     >   --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc 
> >     >   docs\[1]file.md 
> >     >   After upgrading pandoc to 2.0.6 I have to change the parameter 
> >     >   --latex-engine to --pdf-engine. The new commandline that would 
> >     be used 
> >     >   was this: 
> >     >   D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf 
> >     >   --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc 
> >     >   docs\[2]file.md 
> >     >   Following is the response I get: 
> >     >   pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known 
> >     >   I have updated Miktex, but the result is the same. With 1.19.2.1 
> >     the 
> >     >   PDF will be created. 
> >     >   Thanks for any helpfull advice. 
> >     >   Greetings 
> >     >   Karsten 
> >     > 
>
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/47a53a1e-9098-459f-b88f-618c6ded03e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: pdf-engine pdflatex not known - windows, miktex portable
       [not found]               ` <47a53a1e-9098-459f-b88f-618c6ded03e4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
@ 2018-06-20  7:56                 ` Giacomo Lanza
  0 siblings, 0 replies; 6+ messages in thread
From: Giacomo Lanza @ 2018-06-20  7:56 UTC (permalink / raw)
  To: pandoc-discuss


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

Hallo everybody,

my case is related, but the behaviour is different.

A conversion to PDF via PDFLaTeX works regardless of the engine being 
installed at a different hard disk partition than my work directory.

A conversion to PDF using other suggested engines (I tried Prince and 
wkhtmltopdf) does not work.

On my computer, all programs are installed in the C:\ partition, whereas my 
work directory is under P:\.

The argument --pdf-engine= does not accept one full path: just the name of 
the engine.

For security reasons I am not allowed to write inside a folder higher than 
C:\Program files\.

Has anybody a clue, where the problem lies?

Thanks in advance.

Best greetings

Giacomo

Il giorno venerdì 5 gennaio 2018 08:57:29 UTC+1, K ha scritto:
>
> Thanks for caring ... as I see in the posts, the problem is not Windows 
> exclusive.
> For me the solution with temporary updating the path, is enough. 
> It seems, i can't help anymore, because the parameter --trace, 
> --log=file.log, --verbose didn't seem to work for me (at least in my 
> batch-file), so i can't provide any more information. :(
>
> Thanks for this incredible piece of software.
>
> Am Donnerstag, 4. Januar 2018 17:27:27 UTC+1 schrieb John MacFarlane:
>>
>> I'm not sure why there'd be a difference btw pandoc 1 and 2. 
>> I've looked at the code and nothing is jumping out at me. 
>>
>> +++ 'K' via pandoc-discuss [Jan 03 18 23:29 ]: 
>> >   Thanks for your response. 
>> >   Because of using it in a batch-file I could temporary change the 
>> >   path-variable without a problem and after that it runs smoothly. 
>> >   Is pandoc 2 searching for ( / needing) supporting-files from miktex / 
>> >   pdflatex? (and version 1.x doesn't do that?) 
>> >   But that workaround is good enough for me. 
>> >   Thanks for your quick help. 
>> >   Am Mittwoch, 3. Januar 2018 19:42:23 UTC+1 schrieb John MacFarlane: 
>> > 
>> >     Generally this would happen if the program is not found 
>> >     when pandoc tries to run the process. I'm not sure why that 
>> >     would be. 
>> >     Try just using --pdf-engine=pdflatex and putting the 
>> >     relevant directory in your path (perhaps temporarily). 
>> >     +++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]: 
>> >     >   Hi, 
>> >     >   I'm using portable Versions of pandoc and miktex on a Windows 
>> >     System. 
>> >     >   With pandoc 1.19.2.1 converting a markdown-File to PDF runs 
>> fine 
>> >     - the 
>> >     >   used commandline looks like this: 
>> >     >   D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf 
>> >     >   --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe 
>> --toc 
>> >     >   docs\[1]file.md 
>> >     >   After upgrading pandoc to 2.0.6 I have to change the parameter 
>> >     >   --latex-engine to --pdf-engine. The new commandline that would 
>> >     be used 
>> >     >   was this: 
>> >     >   D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf 
>> >     >   --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc 
>> >     >   docs\[2]file.md 
>> >     >   Following is the response I get: 
>> >     >   pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not 
>> known 
>> >     >   I have updated Miktex, but the result is the same. With 
>> 1.19.2.1 
>> >     the 
>> >     >   PDF will be created. 
>> >     >   Thanks for any helpfull advice. 
>> >     >   Greetings 
>> >     >   Karsten 
>> >     > 
>>
>>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e1f959b2-de75-4cbe-bcf6-7a1bcfb02ce5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2018-06-20  7:56 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-03 12:03 pdf-engine pdflatex not known - windows, miktex portable 'K' via pandoc-discuss
     [not found] ` <54e1c2fd-4777-4f44-b956-0dcc73c2b832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-03 18:42   ` John MACFARLANE
2018-01-04  7:29     ` 'K' via pandoc-discuss
     [not found]       ` <0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-04 16:27         ` John MacFarlane
     [not found]           ` <20180104162711.GD15709-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-01-05  7:57             ` 'K' via pandoc-discuss
     [not found]               ` <47a53a1e-9098-459f-b88f-618c6ded03e4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-06-20  7:56                 ` Giacomo Lanza

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).