From: Cecilio Pardo <cpardo@imayhem.com>
To: 71909@debbugs.gnu.org
Subject: bug#71909: 30.0.60;
Date: Wed, 30 Oct 2024 10:05:08 +0100 [thread overview]
Message-ID: <3b0ad17c-aa6e-421c-a17a-453bf0483023@imayhem.com> (raw)
In-Reply-To: <86plnj56li.fsf@gnu.org>
>> The image conversion is done using GdiPlus functions, which are
>> already used on w32image.c, but are static. I have splitted this file
>> into .c and .h, to be able to reuse those definitions. The image
>> conversion requires that native image functions are activated.
>
> What happens with yank-media if the user disables native image APIs?
> Do we signal an error or is there some graceful degradation (like
> using another MIME type)?
The ability to yank DIBV5 will be lost. If there is no alternative such
as PNG or image/*, then yank can't be done.
> Why a unibyte string? Is this always binary data or something? If
> this could be text (e.g., text/html), then a unibyte string is not the
> best choice.
It can be binary, but not always. Is unibyte ok for binary cases? I can
treat text/* differently, and make exceptions for types like image/svg+xml.
> In any case, if the function must return a unibyte string in some
> cases, that should be mentioned in the doc string, because callers
> will otherwise not expect to get a unibyte string. Also, where will
> this unibyte string be decoded?
In the binary case, is there any decoding to do?
next prev parent reply other threads:[~2024-10-30 9:05 UTC|newest]
Thread overview: 37+ 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-20 13:09 ` Ihor Radchenko
2024-10-20 13:51 ` Eli Zaretskii
2024-10-20 13:59 ` Ihor Radchenko
2024-10-20 14:22 ` Eli Zaretskii
2024-10-20 15:02 ` Ihor Radchenko
2024-10-20 15:34 ` Eli Zaretskii
2024-10-20 15:57 ` Ihor Radchenko
2024-10-20 17:50 ` Visuwesh
2024-10-20 17:59 ` Eli Zaretskii
2024-10-20 17:16 ` Cecilio Pardo
2024-10-20 17:58 ` Eli Zaretskii
2024-10-07 10:24 ` Cecilio Pardo
2024-10-07 11:58 ` Eli Zaretskii
2024-10-09 12:52 ` Cecilio Pardo
2024-10-09 13:40 ` Eli Zaretskii
2024-10-23 23:13 ` bug#71909: 30.0.60; yank-media on MS-Windows Cecilio Pardo
2024-10-24 7:18 ` Eli Zaretskii
2024-10-24 8:39 ` Cecilio Pardo
2024-10-24 9:38 ` Eli Zaretskii
2024-10-24 10:43 ` Cecilio Pardo
2024-10-10 10:04 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-10 10:49 ` Eli Zaretskii
2024-10-28 21:46 ` Cecilio Pardo
2024-10-29 14:25 ` Eli Zaretskii
2024-10-29 14:55 ` Eli Zaretskii
2024-10-30 9:05 ` Cecilio Pardo [this message]
2024-10-30 15:35 ` Eli Zaretskii
2024-10-30 15:49 ` Cecilio Pardo
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=3b0ad17c-aa6e-421c-a17a-453bf0483023@imayhem.com \
--to=cpardo@imayhem.com \
--cc=71909@debbugs.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).