From: "Daniel J. Sinder" <djsinder@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Resolution of LaTeX fragments
Date: Fri, 01 Sep 2006 14:50:38 -0700 [thread overview]
Message-ID: <44F8AB2E.60606@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
I've encountered a problem with LaTeX fragments: the default
resolution that dvipng produces results in text (in the images)
which is too small. Of course, browsers (eg, firefox) can manipulate
font size from the client side, but that doesn't affect images (and
changing the relative size of the two). Monitor resolution is also a
factor. Uugh. I guess mixing text with images containing text is not
really ideal, but I'll put that aside for now.
I don't have a great solution for this, but I needed something to
make it usable. I've added a little hack that creates a variable,
org-export-LaTeX-fragments-resolution, that is used in the call to
dvipng. I've found that a setting of 150 is much easier on my eyes
than the default (which I've estimated to be ~86). I added something
to org-export-plist-vars for publishing too, but that doesn't seem
to work -- not sure why (I'm new to Elisp).
The patch is attached in case anyone else was looking for a fix for
this.
Dan
[-- Attachment #2: org-dvipng-resolution.patch --]
[-- Type: text/plain, Size: 1315 bytes --]
--- org-orig.el 2006-09-01 14:36:16.000000000 -0700
+++ org.el 2006-09-01 13:38:30.000000000 -0700
@@ -1985,6 +1985,12 @@
:group 'org-latex
:type 'boolean)
+(defcustom org-export-LaTeX-fragments-resolution 86
+ "Output resolution of images created by conversion of LaTeX fragments when exporting to HTML."
+ :group 'org-export-translation
+ :group 'org-latex
+ :type 'integer)
+
(defcustom org-export-with-fixed-width t
"Non-nil means, lines starting with \":\" will be in fixed width font.
This can be used to have pre-formatted text, fragments of code etc. For
@@ -13110,6 +13116,7 @@
(:sub-superscript . org-export-with-sub-superscripts)
(:TeX-macros . org-export-with-TeX-macros)
(:LaTeX-fragments . org-export-with-LaTeX-fragments)
+ (:LaTeX-resolution . org-export-LaTeX-fragments-resolution)
(:fixed-width . org-export-with-fixed-width)
(:timestamps . org-export-with-timestamps)
(:tables . org-export-with-tables)
@@ -15532,6 +15539,7 @@
(call-process "dvipng" nil nil nil
"-E" "-fg" fg "-bg" bg
"-x" scale "-y" scale "-T" "tight"
+ "-D" (number-to-string org-export-LaTeX-fragments-resolution)
"-o" pngfile
dvifile)
(if (not (file-exists-p pngfile))
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2006-09-01 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 21:50 Daniel J. Sinder [this message]
2006-09-02 5:26 ` Resolution of LaTeX fragments Carsten Dominik
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=44F8AB2E.60606@gmail.com \
--to=djsinder@gmail.com \
--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).