emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Huszagh <huszaghmatt@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: patch: add custom latex->html conversion command
Date: Sun, 16 Feb 2020 16:12:01 -0800	[thread overview]
Message-ID: <CA+X8ke7DzwvygDBF3MYu45HLvZFfyMCvsFVHL5-BHnXZbimWtw@mail.gmail.com> (raw)
In-Reply-To: <87ftfahyau.fsf@gnu.org>

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

Bastien,

Thanks for the reply. I’ll look into it. However, I’d initially ruled that
out because the final output is meant to be an image. So, to get just text
insertion into the html output I imagine would be a bit of a hack. For
instance what to set image-converter to etc.

Matt

On Sun, Feb 16, 2020 at 4:06 PM Bastien <bzg@gnu.org> wrote:

> Hi Matt,
>
> Matt Huszagh <huszaghmatt@gmail.com> writes:
>
> > The patch below allow's you to provide your own shell command the
> > generates HTML from a latex fragment and places the output directly in
> > the exported HTML file.
>
> Can you get the same output by configuring a new symbol in
> `org-preview-latex-process-alist' then setting `org-html-with-latex'
> to this new symbol?
>
> I've not tested it, so perhaps it does not work.
>
> But any patch about adding latexmlc support should surely look in this
> direction first.
>
> HTH,
>
> --
>  Bastien
>

[-- Attachment #2: Type: text/html, Size: 1443 bytes --]

  reply	other threads:[~2020-02-17  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  2:49 patch: add custom latex->html conversion command Matt Huszagh
2020-02-17  0:06 ` Bastien
2020-02-17  0:12   ` Matt Huszagh [this message]
2020-02-17  0:19     ` Bastien
2020-02-17  0:23 ` Bastien
2020-02-17  1:06   ` Matt Huszagh
2020-02-17  1:10     ` Bastien
2020-02-17  1:11       ` Matt Huszagh
2020-02-24 10:27     ` Bastien

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=CA+X8ke7DzwvygDBF3MYu45HLvZFfyMCvsFVHL5-BHnXZbimWtw@mail.gmail.com \
    --to=huszaghmatt@gmail.com \
    --cc=bzg@gnu.org \
    --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).