emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: jman <emacs-orgmode@city17.xyz>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Re: Understanding Publish (ox-publish.el)
Date: Mon, 14 Oct 2024 12:02:01 +0200	[thread overview]
Message-ID: <878qurm292.fsf@web.de> (raw)
In-Reply-To: <871q0j3iv2.fsf@city17.xyz> (jman's message of "Sun, 13 Oct 2024 21:25:53 +0200")

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

jman <emacs-orgmode@city17.xyz> writes:
> I'm trying to learn more about the publish export option or Org mode.
> Specifically I am using the function `org-latex-publish-to-pdf` to
> export Orgmode files into PDF.
>
> Since this export backend is transparently using Latex, there is stuff
> going on behind my back that makes it a bit difficult debugging or
> customizing the formatting.

As a general hint when debugging PDF export: when you hit an error, then
first export to LaTeX and convert the file to PDF with pdflatex
(following the commands defined in the variable org-latex-pdf-process).

You can then fix it directly in LaTeX-side and afterwards bring the
change into the org-mode document.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

      parent reply	other threads:[~2024-10-14 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 19:25 Understanding Publish (ox-publish.el) jman
2024-10-14  8:37 ` Christian Moe
2024-10-14 15:40   ` jman
2024-10-14 18:47     ` jman
2024-10-14 21:06       ` Christian Moe
2024-10-15  7:13         ` jman
2024-10-15  8:11           ` Christian Moe
2024-10-15 11:54             ` Rens Oliemans
2024-10-20 13:04         ` Ihor Radchenko
2024-10-21  7:07           ` Christian Moe
2024-10-26 17:38             ` Ihor Radchenko
2024-10-14 10:02 ` Dr. Arne Babenhauserheide [this message]

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=878qurm292.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=emacs-orgmode@city17.xyz \
    --cc=emacs-orgmode@gnu.org \
    /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).