Mixing
Why is pdflatex outing itself as pdftex?
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I'm running latexmk -pdf in my GitLab-CI environment to render *.tex files into a PDF.
As I checked the outputs I found, that latexmk is calling pdftex instead of pdflatex:
Checking out d4c1eceb as testing-latexmk...
Skipping Git submodules setup
$ latexmk -pdf $DOCUMENT.tex
Latexmk: This is Latexmk, John Collins, 21 September 2018, version: 4.60.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex -recorder "Concept-of-Realization.tex"'
------------
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
Now I check what pdflatex was doing before I switched to latexmk:
Checking out ffb7336b as v0.1...
Skipping Git submodules setup
$ pdflatex $DOCUMENT.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
To my suprise, both runs call themselfes pdftex instead of pdflatex.
Questions:
- Why is
pdflatexcalling himselfpdftex? - Where is the difference?
pdftex latexmk
asked 2 hours ago
Paebbels
74114
add a comment |Â
up vote
3
down vote
favorite
I'm running latexmk -pdf in my GitLab-CI environment to render *.tex files into a PDF.
As I checked the outputs I found, that latexmk is calling pdftex instead of pdflatex:
Checking out d4c1eceb as testing-latexmk...
Skipping Git submodules setup
$ latexmk -pdf $DOCUMENT.tex
Latexmk: This is Latexmk, John Collins, 21 September 2018, version: 4.60.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex -recorder "Concept-of-Realization.tex"'
------------
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
Now I check what pdflatex was doing before I switched to latexmk:
Checking out ffb7336b as v0.1...
Skipping Git submodules setup
$ pdflatex $DOCUMENT.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
To my suprise, both runs call themselfes pdftex instead of pdflatex.
Questions:
- Why is
pdflatexcalling himselfpdftex? - Where is the difference?
pdftex latexmk
asked 2 hours ago
Paebbels
74114
7
pdftexis the engine.pdflatexis the format.
– Johannes_B
2 hours ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm running latexmk -pdf in my GitLab-CI environment to render *.tex files into a PDF.
As I checked the outputs I found, that latexmk is calling pdftex instead of pdflatex:
Checking out d4c1eceb as testing-latexmk...
Skipping Git submodules setup
$ latexmk -pdf $DOCUMENT.tex
Latexmk: This is Latexmk, John Collins, 21 September 2018, version: 4.60.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex -recorder "Concept-of-Realization.tex"'
------------
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
Now I check what pdflatex was doing before I switched to latexmk:
Checking out ffb7336b as v0.1...
Skipping Git submodules setup
$ pdflatex $DOCUMENT.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
To my suprise, both runs call themselfes pdftex instead of pdflatex.
Questions:
- Why is
pdflatexcalling himselfpdftex? - Where is the difference?
pdftex latexmk
asked 2 hours ago
Paebbels
74114
I'm running latexmk -pdf in my GitLab-CI environment to render *.tex files into a PDF.
As I checked the outputs I found, that latexmk is calling pdftex instead of pdflatex:
Checking out d4c1eceb as testing-latexmk...
Skipping Git submodules setup
$ latexmk -pdf $DOCUMENT.tex
Latexmk: This is Latexmk, John Collins, 21 September 2018, version: 4.60.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex -recorder "Concept-of-Realization.tex"'
------------
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
Now I check what pdflatex was doing before I switched to latexmk:
Checking out ffb7336b as v0.1...
Skipping Git submodules setup
$ pdflatex $DOCUMENT.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./Concept-of-Realization.tex
LaTeX2e <2018-04-01> patch level 5
To my suprise, both runs call themselfes pdftex instead of pdflatex.
Questions:
- Why is
pdflatexcalling himselfpdftex? - Where is the difference?
pdftex latexmk
pdftex latexmk
asked 2 hours ago
Paebbels
74114
asked 2 hours ago
Paebbels
74114
asked 2 hours ago
Paebbels
74114
asked 2 hours ago
Paebbels
74114
asked 2 hours ago
Paebbels
74114
74114
7
pdftexis the engine.pdflatexis the format.
– Johannes_B
2 hours ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago
add a comment |Â
7
pdftexis the engine.pdflatexis the format.
– Johannes_B
2 hours ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago
7
7
pdftex is the engine. pdflatex is the format.– Johannes_B
2 hours ago
pdftex is the engine. pdflatex is the format.– Johannes_B
2 hours ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
In a Linux terminal on /usr/local/texlive/2018/bin/x86_64-linux directory:
$ file pdflatex
pdflatex: symbolic link to pdftex
But with pdftex:
$ file pdftex
pdftex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=f304a4bff8b70b6e1693666cfe3a966599c1f918, stripped
Thas is, pdftex is always the engine, pdflatex is only a link to pdftexbut not load it with the same options. This is the output of pdflatex and pdftext:
$ pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
$ pdftex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdftex)
restricted write18 enabled.
**
As you can see, there are different preloaded format, that match with the apparent command name. The same happen if you try with latex. How can latex and pdflatex be both symbolic links to same executable (pdftex) and not behave the same? Well, in sort, because pdftex will take as format option the name of the symbolic link, whatever it is, so for the link "foo":
~ $ ln -s /usr/local/texlive/2018/bin/x86_64-linux/pdftex foo
~ $ ./foo
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=foo)
restricted write18 enabled.
**
But if you use both commands with the -ini option, no format is loaded, and then is exactly the same stuff:
$ pdflatex -ini ## (or pdftex -ini)
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
restricted write18 enabled.
**
And of course, you can use pdftex(or pdflatex) command but load the pdflatex (or pdftex) format:
$ pdftex -fmt pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
In summary: pdflatex only call to pdftex -fmt pdflatex
answered 1 hour ago
Fran
49.1k6110172
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
In a Linux terminal on /usr/local/texlive/2018/bin/x86_64-linux directory:
$ file pdflatex
pdflatex: symbolic link to pdftex
But with pdftex:
$ file pdftex
pdftex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=f304a4bff8b70b6e1693666cfe3a966599c1f918, stripped
Thas is, pdftex is always the engine, pdflatex is only a link to pdftexbut not load it with the same options. This is the output of pdflatex and pdftext:
$ pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
$ pdftex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdftex)
restricted write18 enabled.
**
As you can see, there are different preloaded format, that match with the apparent command name. The same happen if you try with latex. How can latex and pdflatex be both symbolic links to same executable (pdftex) and not behave the same? Well, in sort, because pdftex will take as format option the name of the symbolic link, whatever it is, so for the link "foo":
~ $ ln -s /usr/local/texlive/2018/bin/x86_64-linux/pdftex foo
~ $ ./foo
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=foo)
restricted write18 enabled.
**
But if you use both commands with the -ini option, no format is loaded, and then is exactly the same stuff:
$ pdflatex -ini ## (or pdftex -ini)
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
restricted write18 enabled.
**
And of course, you can use pdftex(or pdflatex) command but load the pdflatex (or pdftex) format:
$ pdftex -fmt pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
In summary: pdflatex only call to pdftex -fmt pdflatex
answered 1 hour ago
Fran
49.1k6110172
add a comment |Â
up vote
5
down vote
accepted
In a Linux terminal on /usr/local/texlive/2018/bin/x86_64-linux directory:
$ file pdflatex
pdflatex: symbolic link to pdftex
But with pdftex:
$ file pdftex
pdftex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=f304a4bff8b70b6e1693666cfe3a966599c1f918, stripped
Thas is, pdftex is always the engine, pdflatex is only a link to pdftexbut not load it with the same options. This is the output of pdflatex and pdftext:
$ pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
$ pdftex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdftex)
restricted write18 enabled.
**
As you can see, there are different preloaded format, that match with the apparent command name. The same happen if you try with latex. How can latex and pdflatex be both symbolic links to same executable (pdftex) and not behave the same? Well, in sort, because pdftex will take as format option the name of the symbolic link, whatever it is, so for the link "foo":
~ $ ln -s /usr/local/texlive/2018/bin/x86_64-linux/pdftex foo
~ $ ./foo
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=foo)
restricted write18 enabled.
**
But if you use both commands with the -ini option, no format is loaded, and then is exactly the same stuff:
$ pdflatex -ini ## (or pdftex -ini)
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
restricted write18 enabled.
**
And of course, you can use pdftex(or pdflatex) command but load the pdflatex (or pdftex) format:
$ pdftex -fmt pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
In summary: pdflatex only call to pdftex -fmt pdflatex
answered 1 hour ago
Fran
49.1k6110172
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
In a Linux terminal on /usr/local/texlive/2018/bin/x86_64-linux directory:
$ file pdflatex
pdflatex: symbolic link to pdftex
But with pdftex:
$ file pdftex
pdftex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=f304a4bff8b70b6e1693666cfe3a966599c1f918, stripped
Thas is, pdftex is always the engine, pdflatex is only a link to pdftexbut not load it with the same options. This is the output of pdflatex and pdftext:
$ pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
$ pdftex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdftex)
restricted write18 enabled.
**
As you can see, there are different preloaded format, that match with the apparent command name. The same happen if you try with latex. How can latex and pdflatex be both symbolic links to same executable (pdftex) and not behave the same? Well, in sort, because pdftex will take as format option the name of the symbolic link, whatever it is, so for the link "foo":
~ $ ln -s /usr/local/texlive/2018/bin/x86_64-linux/pdftex foo
~ $ ./foo
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=foo)
restricted write18 enabled.
**
But if you use both commands with the -ini option, no format is loaded, and then is exactly the same stuff:
$ pdflatex -ini ## (or pdftex -ini)
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
restricted write18 enabled.
**
And of course, you can use pdftex(or pdflatex) command but load the pdflatex (or pdftex) format:
$ pdftex -fmt pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
In summary: pdflatex only call to pdftex -fmt pdflatex
answered 1 hour ago
Fran
49.1k6110172
In a Linux terminal on /usr/local/texlive/2018/bin/x86_64-linux directory:
$ file pdflatex
pdflatex: symbolic link to pdftex
But with pdftex:
$ file pdftex
pdftex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=f304a4bff8b70b6e1693666cfe3a966599c1f918, stripped
Thas is, pdftex is always the engine, pdflatex is only a link to pdftexbut not load it with the same options. This is the output of pdflatex and pdftext:
$ pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
$ pdftex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdftex)
restricted write18 enabled.
**
As you can see, there are different preloaded format, that match with the apparent command name. The same happen if you try with latex. How can latex and pdflatex be both symbolic links to same executable (pdftex) and not behave the same? Well, in sort, because pdftex will take as format option the name of the symbolic link, whatever it is, so for the link "foo":
~ $ ln -s /usr/local/texlive/2018/bin/x86_64-linux/pdftex foo
~ $ ./foo
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=foo)
restricted write18 enabled.
**
But if you use both commands with the -ini option, no format is loaded, and then is exactly the same stuff:
$ pdflatex -ini ## (or pdftex -ini)
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (INITEX)
restricted write18 enabled.
**
And of course, you can use pdftex(or pdflatex) command but load the pdflatex (or pdftex) format:
$ pdftex -fmt pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex)
restricted write18 enabled.
**
In summary: pdflatex only call to pdftex -fmt pdflatex
answered 1 hour ago
Fran
49.1k6110172
edited 18 mins ago
answered 1 hour ago
Fran
49.1k6110172
answered 1 hour ago
Fran
49.1k6110172
answered 1 hour ago
Fran
49.1k6110172
49.1k6110172
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f457174%2fwhy-is-pdflatex-outing-itself-as-pdftex%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
7
pdftexis the engine.pdflatexis the format.– Johannes_B
2 hours ago
latex is written in tex and in that case is using the pdftex tex implementation.
– David Carlisle
1 hour ago