emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Timothy <tecosaur@gmail.com>
To: Zhuohua Li <lizhuohua1994@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: `org-babel-latex-preamble' should not hardcode `pgfsysdriver' [9.4.4 (release_9.4.4 @ /home/n/.emacs.d/elpa/28.0/develop/org-mode/lisp/)]
Date: Thu, 30 Dec 2021 17:24:44 +0800	[thread overview]
Message-ID: <87pmpeqw28.fsf@gmail.com> (raw)
In-Reply-To: <CALdQSHsFYAZNaOb9TRrHV78=UvzfBeJcRWeJUi3AGzpkFWPXhg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]

Hi Zhuohua,

Thanks for the bug report, and sorry it’s taken so long for someone to look at
it (the maintainers have had a busy year).

I’ve just had a look, and indeed see `\\def\\pgfsysdriver{pgfsys-tex4ht.def}'
hardcoded at `ob-latex.el:185'. However, this is inside a `(string= "html"
extension)' check, so tex4ht seem like the right driver to use here. There is
also a TODO just before it though,

┌────
│ 	  ;; TODO: this is a very different way of generating the
│ 	  ;; frame latex document than in the pdf case.  Ideally, both
│ 	  ;; would be unified.  This would prevent bugs creeping in
│ 	  ;; such as the one fixed on Aug 16 2014 whereby :headers was
│ 	  ;; not included in the SVG/HTML case.
└────

I think a patch which implements this could also allow you to change this
hardcoded string, and would be most welcome if someone were to give it a shot.

All the best,
Timothy

[-- Attachment #1.2: Type: text/html, Size: 7040 bytes --]

     prev parent reply	other threads:[~2021-12-30  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  7:02 Bug: `org-babel-latex-preamble' should not hardcode `pgfsysdriver' [9.4.4 (release_9.4.4 @ /home/n/.emacs.d/elpa/28.0/develop/org-mode/lisp/)] Zhuohua Li
2021-12-30  9:24 ` Timothy [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=87pmpeqw28.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lizhuohua1994@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

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).