From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Matt Huszagh <huszaghmatt@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Patch to align baseline of latex fragments and surrounding text
Date: Thu, 9 Dec 2021 20:59:30 +0000 [thread overview]
Message-ID: <c5cf414c-5a55-de0f-7ddb-4a2a60aedc53@posteo.eu> (raw)
In-Reply-To: <87v906bepp.fsf@gmail.com>
Hi,
Matt Huszagh writes:
> I feel that maybe it would be useful to attach screenshots to show the
> improvement from this patch? Anyway, I've attached two images: one with
> the correct baseline alignment to surrounding text and the other with
> the current, incorrect, baseline alignment.
>
> I think a lot of people would like this functionality. It looks much
> better than the current behavior.
This looks great indeed but I've failed to reproduce in my
environment.
I couldn't get ~org--match-text-baseline-ascent~ to compute the
ascent : the ~xml-get-attribute~ call returns
: ("-16.945024" "12.153473" "16.148855" "8.064997")
which gives an ascent < -100, and the code then defaults to 'center.
The options described in your =my-dvisvgm= seem outdated, you can
check the latest default value of =dvisvgm= : =use-xcolor= is
deprecated and a =:image-size-adjust= property is provided for the
images to be sized properly. Are the arguments =--no-fonts= and
=--exact-bbox= necessary ?
If there are no drawbacks, perhaps this behaviour should be the
default. Otherwise, it should at least be easier to toggle.
Can something similar be done with =dvipng= ?
Regards,
--
Sébastien Miquel
next prev parent reply other threads:[~2021-12-09 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 23:23 Patch to align baseline of latex fragments and surrounding text Matt Huszagh
2021-10-10 23:29 ` Matt Huszagh
2021-12-03 2:32 ` Matt Huszagh
2021-12-09 20:59 ` Sébastien Miquel [this message]
2021-12-09 22:18 ` Matt Huszagh
2021-12-10 15:49 ` Sébastien Miquel
2021-12-11 4:53 ` [Patch] Align " Matt Huszagh
2022-07-30 9:55 ` Ihor Radchenko
2024-01-19 6:41 ` Matt Huszagh
2024-01-19 9:33 ` Timothy
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=c5cf414c-5a55-de0f-7ddb-4a2a60aedc53@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@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
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).