bug#71909: 30.0.60;

[Cecilio Pardo <cpardo@imayhem.com>]

On 30/10/2024 16:35, Eli Zaretskii wrote:
>> The ability to yank DIBV5 will be lost. If there is no alternative such
>> as PNG or image/*, then yank can't be done.
> 
> Is this because w32-use-native-image-API set to nil disables loading
> of GDI+?  If so, we could load it even if w32-use-native-image-API is
> nil, but just return false from w32_can_use_native_image_api.  This
> would allow us to use the GDI+ functions needed for yanking, but not
> those needed for image display.  Does this make sense?

Yes, I'll do that.

>>> 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?
> 
> Yes.  But we need to document that in the doc string.
> 
>> I can
>> treat text/* differently, and make exceptions for types like image/svg+xml.
> 
> That'd be much better.

Ok.

I'm on it.