From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Scott Otterson <scotto@sharpleaf.org>
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Latex preview overlay scaling not consistent across PPI
Date: Wed, 30 Nov 2016 22:05:16 +0100 [thread overview]
Message-ID: <87eg1sel0z.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAPY3P0SkKahH_KTnjoG-UNn6kbG-k6Wb3YKS_Gh-FXCnO057pw@mail.gmail.com> (Scott Otterson's message of "Wed, 30 Nov 2016 17:35:33 +0100")
Hello,
Scott Otterson <scotto@sharpleaf.org> writes:
> The size of the latex preview overlay scaling is inconsistent across
> screens with different pixel densities.
>
> I've set my customization to use dvipng for the latex previews I see when I
> type C-c C-x C-l. Dvipng is customized as follows:
>
> [image: Inline image 1]
>
> The "Value" is set to (1.0 . 1.0), which I would think means that the font
> size in the preview overlay is scaled the same as the font size org
> buffer's normal text.
>
> This is more or less true for a Windows 7 machine connected to a 24",
> 1920x1080 pixel monitor:
>
> [image: Inline image 2]
>
> However, on a Windows 10 machine with a 12.3", 2736x1824 pixel monitor, the
> same customization looks like this:
>
> [image: Inline image 3]
>
> On the second computer (a Surface Pro 4) the previews are tiny because the
> screen has a much higher pixel density; the normal text is scaled
> appropriately but the overlays aren't scaled to match.
I made a change to how dpi is computed in `org-create-formula-image'.
Could you test it and report if it fixes your issue ?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-11-30 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 16:35 Bug: Latex preview overlay scaling not consistent across PPI Scott Otterson
2016-11-30 21:05 ` Nicolas Goaziou [this message]
2016-12-01 6:31 ` Scott Otterson
2016-12-01 19:45 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg1sel0z.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@sharpleaf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.