emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Use dvisvgm to preview latex fragments
Date: Fri, 13 May 2016 11:01:29 +0200	[thread overview]
Message-ID: <87lh3enxg6.fsf@gmx.us> (raw)
In-Reply-To: 3f4ffa54.95fa.154a8dbadfb.Coremail.tumashu@163.com

Hi tumashu,

tumashu <tumashu@163.com> writes:

> I find a new tool: dvisvgm (https://github.com/mgieseki/dvisvgm)
> ,which we can use it to preview latex fregments, it can deal with
> xetex's xdv file as well (it will available in texlive2016).

That looks very cool.  Thanks for the pointer!

Will you be working on a patch for supporting dvisvg?

> The questions are:
> 1.  which path we should use:   "dvi/xdv -> svg" or "dvi/xdv -> svg -> png" ?

Depends on which format Emacs supports.  If it’s compiled with svg support
I’d guess it’s better since it’s vector graph and potentially could scale
nicer when increasing font size.  But I don’t know how easy it would be to
incorporate inlined svg display.  At the very minimum you will have to
look at e.g. org-create-formula-image and "surrounding" functions, which
will bark at "dvisvg" ATM.

It might also be nice to make it possible to incorporate svg images for
math in odt where formula support is a bit lackluster.

> 2. if we use the first path, how to deal with
> org-latex-preview-ltxpng-directory?  should we rename it to
> org-latex-preview-ltximg-directory or
>    org-latex-preview-ltxpic-directory ?

If you provide a patch that enables svg support you can change the default
value.

Rasmus

-- 
I hear there's rumors on the, uh, Internets. . .

      reply	other threads:[~2016-05-16 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  6:44 Use dvisvgm to preview latex fragments tumashu
2016-05-13  9:01 ` Rasmus [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=87lh3enxg6.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).