Re: pdf-engine pdflatex not known - windows, miktex portable

[Giacomo Lanza <nuovog6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- 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 --]