From: Cecilio Pardo <cpardo@imayhem.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71909@debbugs.gnu.org
Subject: bug#71909: 30.0.60;
Date: Wed, 9 Oct 2024 14:52:57 +0200 [thread overview]
Message-ID: <1b239275-068f-40b4-814e-dbaf9229e99f@imayhem.com> (raw)
In-Reply-To: <86o73wt997.fsf@gnu.org>
On 07/10/2024 13:58, Eli Zaretskii wrote:
> Isn't CF_BITMAP format indicate the data to which we convert images on
> Windows in the w32-specific portions of image.c? Or maybe it's a BMP
> data (which we can already display, see w32image.c)? If so, then
> yanking images into an Emacs buffer could simply use the data instead
> of converting to PNG, then back to bitmap.
But how would lisp programs register for receiving that?
yank-media-handler asks for mime types.
>> I didn't expect the PNG, image/png formats. I suppose they are the same
>> image as the DIB/BITMAP.
>
> I'd rather expect them to be in PNG format.
Yes, the same pixels, but in PNG format.
>>> What about other kinds of media, like audio and video data? Is that
>>> supported, and if so, can we include that in some way?
>>
>> In standard formats there is CF_RIFF and CF_WAVE. Also programas may
>> insert a file format (as they do with PNGS), but I haven't found any
>> example yet. In any case, we can do the same as with images.
>
> If CF_WAVE are the same data as in *.wav files, then we should be able
> to invoke play-sound in some way.
But again, lisp programas need to register for a mime type, and then act
on the data as they require.
next prev parent reply other threads:[~2024-10-09 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <865xtnhyn6.fsf@foxmail.com>
2024-10-05 12:28 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-05 12:33 ` Eli Zaretskii
2024-10-05 12:42 ` Eli Zaretskii
2024-10-05 17:14 ` Cecilio Pardo
2024-10-05 19:31 ` Eli Zaretskii
2024-10-05 21:24 ` Cecilio Pardo
2024-10-06 5:59 ` Eli Zaretskii
[not found] ` <87ldz1h5s4.fsf@gmail.com>
2024-10-06 11:50 ` Eli Zaretskii
2024-10-06 12:15 ` Visuwesh
2024-10-07 10:24 ` Cecilio Pardo
2024-10-07 11:58 ` Eli Zaretskii
2024-10-09 12:52 ` Cecilio Pardo [this message]
2024-10-09 13:40 ` Eli Zaretskii
2024-10-10 10:04 ` Cecilio Pardo
2024-10-10 10:49 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b239275-068f-40b4-814e-dbaf9229e99f@imayhem.com \
--to=cpardo@imayhem.com \
--cc=71909@debbugs.gnu.org \
--cc=eliz@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.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).