From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: 67533@debbugs.gnu.org
Subject: bug#67533: SVG images confound position pixel measurements
Date: Sat, 02 Dec 2023 16:18:28 +0200 [thread overview]
Message-ID: <835y1g8z7v.fsf@gnu.org> (raw)
In-Reply-To: <906A480A-85B4-4AB0-B2E3-1533A48C228D@gmail.com> (message from JD Smith on Sat, 2 Dec 2023 08:36:07 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sat, 2 Dec 2023 08:36:07 -0500
> Cc: 67533@debbugs.gnu.org
>
> Strange. Both of my ports here (NS and Mac) show the same issue. Did you check the
> svg-pixel-demo-report buffer the header mentions, where the mismatch measurement information
> gets reported? The specific problems encountered are listed in the report buffer, updated with
> my/check-buffer-pixel-values. For example, at a standard width of 80 characters, I get this report:
>
> SVG Position analysis for svg-pixel-demo (width 80, text-properties)
>
> Incorrect at point= 34: line 2 at (224 . 14) (image): expected 14 got 28
> Incorrect at point= 99: line 3 at (244 . 43) (image): expected 29 got 46
> Incorrect at point=126: line 4 at (42 . 75) (image): expected 32 got 46
> Incorrect at point=162: line 4 at (345 . 75) (image): expected 32 got 52
> Incorrect at point=210: line 5 at (133 . 110) (image): expected 35 got 49
I never understood I need to look in another buffer. I will look into
these.
> So in this case, 5 of the image locations (of 7) are showing sizes of entities one pixel above them as
> too large (with sizes sometimes not matching any line height). At small window widths (like 25-30
> characters) many zero heights start showing up. Running the check in a normal text window
> produces an empty report (no errors).
So any messages in that buffer are problems in your opinion? Or just
those which state zero height?
next prev parent reply other threads:[~2023-12-02 14:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 19:02 SVG images confound position pixel measurements JD Smith
2023-11-29 20:31 ` bug#67533: " JD Smith
2023-11-30 17:32 ` Eli Zaretskii
2023-11-30 21:00 ` JD Smith
2023-12-01 7:08 ` Eli Zaretskii
2023-12-01 22:04 ` JD Smith
2023-12-02 7:30 ` Eli Zaretskii
2023-12-02 13:36 ` JD Smith
2023-12-02 14:18 ` Eli Zaretskii [this message]
2023-12-02 19:39 ` Eli Zaretskii
2023-12-02 21:44 ` JD Smith
2023-12-03 3:04 ` JD Smith
2023-12-03 13:02 ` Eli Zaretskii
2023-12-03 15:48 ` JD Smith
2023-12-03 15:52 ` Eli Zaretskii
2023-12-03 16:31 ` Eli Zaretskii
2023-12-03 21:25 ` JD Smith
2023-12-03 23:14 ` JD Smith
2023-12-04 3:27 ` Eli Zaretskii
2023-12-04 4:32 ` JD Smith
2023-12-04 13:11 ` Eli Zaretskii
2023-12-04 14:14 ` JD Smith
2023-12-16 9:32 ` Eli Zaretskii
2023-12-16 15:07 ` JD Smith
2023-12-16 15:23 ` Eli Zaretskii
2023-12-03 15:49 ` JD Smith
2023-12-03 16:33 ` Eli Zaretskii
2023-12-03 18:58 ` JD Smith
2023-12-01 14:40 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-01 14:55 ` Eli Zaretskii
2023-12-01 15:21 ` JD Smith
2023-12-01 15:36 ` Eli Zaretskii
2023-12-01 15:45 ` JD Smith
2023-12-01 15:59 ` Eli Zaretskii
2023-12-01 16:17 ` JD Smith
2023-12-01 16:30 ` Eli Zaretskii
2023-12-01 16:27 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-01 16:31 ` Eli Zaretskii
2023-12-01 8:36 ` Manuel Giraud via Emacs development discussions.
2023-12-01 14:11 ` JD Smith
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=835y1g8z7v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67533@debbugs.gnu.org \
--cc=jdtsmith@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 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.