From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Zenny <garbytrash@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Sanskrit/Devanagari fonts not exported to org-pdf output
Date: Thu, 21 Sep 2023 19:32:27 +0000 [thread overview]
Message-ID: <87fs37pbjo.fsf@posteo.net> (raw)
In-Reply-To: <CACuV5sCZBM3HJA7RpF7pOtKp5aFVRcBdZ25U_q3rFjK=A31UGQ@mail.gmail.com> (Zenny's message of "Thu, 21 Sep 2023 20:44:40 +0200")
Zenny writes:
> Here it comes:
>
> org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
>
> Its value is
> ("pdflatex -interaction nonstopmode -output-directory %o %f"
> "bibtex %b" "pdflatex -shell-escape -interaction nonstopmode -
> output-directory %o %f" "pdflatex -shell-escape -interaction
> nonstopmode -output-directory %o %f")
> Original value was
> ("latexmk -f -pdf -%latex -interaction=nonstopmode -
> output-directory=%o %f")
It seems that you have modified the original value. Besides, the
docstring says:
[...] %latex is the LaTeX compiler (see ‘org-latex-compiler’) [...]
If you put 'pdflatex ...', it will always compile with pdflatex.
I would recommend that you restore the original value of
org-latex-pdf-process, which uses latexmk (if it is installed, which
seems to be your case), which executes '%latex' (=
`org-latex-compiler'). latexmk is a perl script included in texlive that
is responsible for executing all the necessary compilations (including
the call to the bibliographic engine[1]).
[1] In some cases some configuration is required for latexmk via a
~/latexmkrc file, but by default everything should work fine.
next prev parent reply other threads:[~2023-09-21 19:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:46 Sanskrit/Devanagari fonts not exported to org-pdf output Zenny
2023-09-21 8:24 ` Juan Manuel Macías
2023-09-21 13:46 ` Zenny
2023-09-21 15:33 ` Juan Manuel Macías
2023-09-21 17:53 ` Zenny
2023-09-21 18:28 ` Juan Manuel Macías
2023-09-21 18:44 ` Zenny
2023-09-21 19:32 ` Juan Manuel Macías [this message]
2023-09-21 20:26 ` Zenny
2023-09-21 20:39 ` Zenny
2023-09-21 20:41 ` Zenny
2023-09-21 21:19 ` Juan Manuel Macías
2023-09-22 7:04 ` Zenny
2023-09-22 8:00 ` Juan Manuel Macías
2023-09-22 8:07 ` Zenny
2023-09-22 8:09 ` Zenny
2023-09-22 8:41 ` Juan Manuel Macías
2023-09-22 8:49 ` Zenny
2023-09-22 8:54 ` Zenny
2023-09-22 8:54 ` Juan Manuel Macías
2023-09-22 8:58 ` Zenny
2023-09-22 9:06 ` Juan Manuel Macías
2023-09-22 9:37 ` Zenny
2023-09-22 10:02 ` Juan Manuel Macías
2023-09-22 12:59 ` Zenny
2023-09-22 15:12 ` Juan Manuel Macías
2023-09-22 17:51 ` Zenny
2023-09-22 8:18 ` Juan Manuel Macías
2023-09-22 8:30 ` Zenny
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=87fs37pbjo.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=garbytrash@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).