From: adam <ahcnz@orcon.net.nz>
To: Eric S Fraga <esflists@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: newbie which LaTeX for PDF publish
Date: Mon, 03 Sep 2018 09:32:14 +1200 [thread overview]
Message-ID: <1535923934.31400.20.camel@orcon.net.nz> (raw)
In-Reply-To: <871saccj0z.fsf@gmail.com>
On Sun, 2018-09-02 at 11:04 +0100, Eric S Fraga wrote:
> On Saturday, 1 Sep 2018 at 22:12, adam wrote:
> >
> > Am on Ubuntu 16.04, org-version is 8.2.10
> >
> > Export to PDF C-c C-e l o is working.
> > However I wish finer grain LaTeX control.
> >
> >
> > For Export to PDF to work, I needed pdftex
> But org exports to LaTeX, not TeX. I.e. it exports to TeX with the
> assumption that the LaTeX macros are all available.
>
> Am I missing something?
>
> What finer grain control would you like that you cannot achieve using
> org directions such as #+latex: and #+begin_export latex?
>
I require management of TeX (TeX Live) for export to PDF (LaTeX).
The Tex Live manager (tlmgr) displays available fonts, loads and removes fonts and other
packages.
https://www.tug.org/texlive/doc/tlmgr.html
Sure, pdftex (from texlive-latex-extra) enables org-mode export to PDF, however the
fonts available are opaque within the TexLive environment without tlmgr.
Navigation of TexLive customizations, set with install-tl are opaque without tlmgr.
packages for Ubuntu 16.04 LTS can be seen here,
https://packages.ubuntu.com/search?keywords=texlive
using the TexLive installer install-tl can be seen here,
https://tex.stackexchange.com/questions/1092/how-to-install-vanilla-texlive-on-debian-or-u
buntu
In other words, org-mode export to PDF assumes a pdftex, and the tex/texlive/LaTex
environment is up to the user to simply provide a pdftex.
next prev parent reply other threads:[~2018-09-02 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 10:12 newbie which LaTeX for PDF publish adam
2018-09-01 12:34 ` Robert Klein
2018-09-02 7:58 ` adam
2018-09-26 2:05 ` Adrian Bradd
2018-09-02 10:04 ` Eric S Fraga
2018-09-02 21:32 ` adam [this message]
2018-09-03 5:28 ` Eric S Fraga
2018-09-03 5:48 ` Robert Klein
2018-09-03 12:28 ` Joseph Vidal-Rosset
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1535923934.31400.20.camel@orcon.net.nz \
--to=ahcnz@orcon.net.nz \
--cc=emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).