From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#71909: 30.0.60; yank-media on MS-Windows Date: Thu, 24 Oct 2024 10:18:08 +0300 Message-ID: <8634kmdl5b.fsf@gnu.org> References: <865xtnhyn6.fsf@foxmail.com> <868qv2wwyk.fsf@gnu.org> <865xq6wwkc.fsf@gnu.org> <86wmimuz18.fsf@gnu.org> <0056b65b-5cdc-4271-b717-0acc75661c17@imayhem.com> <86o73xvkj8.fsf@gnu.org> <86o73wt997.fsf@gnu.org> <1b239275-068f-40b4-814e-dbaf9229e99f@imayhem.com> <8634l54cp4.fsf@gnu.org> <51b40c99-1104-4fbd-bf58-dde7d4c0791a@imayhem.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19735"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71909@debbugs.gnu.org To: Cecilio Pardo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 24 09:19:14 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1t3s7l-0004xj-3z for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Oct 2024 09:19:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t3s7F-00029J-34; Thu, 24 Oct 2024 03:18:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t3s79-00028Y-9b for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2024 03:18:35 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1t3s76-0008Ts-QR for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2024 03:18:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=E+M2ZztesukKYyoArNeU8Nlc9dDBHg4U//fQB8T5mmk=; b=m7xOADeRTs+gARhwGhyps0esxnCvyNVO0639VWfVvRzNZRsizJI1EtnNJ2J07E41bMZriKtsxRLM70h7Jcbhv9fckUs1PaVUkpmxMdkWyNG6dNOd6RHo4z+1mT//eMIDAaQeguTkVk+bGbiYr6zUl3UDaCud+3tBO99ocC91f3vqQlpI+MbwR/pIeZYYNsXA3E+P3SiZ3lEv4DoWJYSpUUsce9eyOMyMKsCKD8hlHRVWHwpWL8Xgf75aCQDdW3pJR2XRYU4eZUtq01ANnAUljh1WZu3hhqRIzyUt0BafyOahRGzCUsCKrZ/sWOKqhFsSdJ904RwSt9YxVV8rO2+lCQ==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1t3s7a-0002zA-Kv for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2024 03:19:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Oct 2024 07:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71909 X-GNU-PR-Package: emacs Original-Received: via spool by 71909-submit@debbugs.gnu.org id=B71909.172975433211454 (code B ref 71909); Thu, 24 Oct 2024 07:19:02 +0000 Original-Received: (at 71909) by debbugs.gnu.org; 24 Oct 2024 07:18:52 +0000 Original-Received: from localhost ([127.0.0.1]:33411 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t3s7Q-0002yg-33 for submit@debbugs.gnu.org; Thu, 24 Oct 2024 03:18:52 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34900) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t3s7N-0002yR-F8 for 71909@debbugs.gnu.org; Thu, 24 Oct 2024 03:18:51 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t3s6m-0008Sd-Vc; Thu, 24 Oct 2024 03:18:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=E+M2ZztesukKYyoArNeU8Nlc9dDBHg4U//fQB8T5mmk=; b=YSDuQKqEigUy eDNQV1GWDgBbAMF06Jx83FYFX9gNBWa67gU7CUtSklQS/06iTYqiSzSJdQDGUZNkg9JHwTc5hkMsI xkS5XVWl9GFfNh1dcTuAn1+oMvnOaU+Jxh59G+W/LEKk8pBKRdPnOowsdSKbpeD68Z1685uzVLJJr m37ZkM91GTbDB1ecXsuSbOnerckS7LmrX9yZVtmSgDKWJoFlPyyBQYAT5gls9YNtXk5U1LuUtYgka uPvKsoK/63s6Myk164Vpf0dh6JFU0BK5llAstaIGQb3pJi8npXWGef3gPiARQ6XcBdy4tdkWkPU0f dXX6rTRw4Tqxj0sf4clwxg==; In-Reply-To: <51b40c99-1104-4fbd-bf58-dde7d4c0791a@imayhem.com> (message from Cecilio Pardo on Thu, 24 Oct 2024 01:13:49 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:294167 Archived-At: > Date: Thu, 24 Oct 2024 01:13:49 +0200 > Cc: 71909@debbugs.gnu.org > From: Cecilio Pardo > > - Rename PNG to image/png, so the emacs programs find it. If there are > other image formats with mime spec, yank-media will let the user choose. > For example, krita offers a huge amount of formats, as mime. > > - If no PNG is offered, but DIBV5 is, like Firefox, convert the pixel > data to a PNG file, and offer it as image/png. We don't loose anything > converting the BMP to PNG, and the programs that use yank-media for > images (message-mode, org-mode) need a file, not an in-memory image > object. And PNG is a much better format. I'm not sure I follow: isn't yank-media about yanking the image into the current buffer? If so, why is having a file important, let alone necessary? > - GDIMetafile would be ideally converted to SVG. Offering the metafile > as it is makes little sense in my opinion. It is not a very used format. Will we support yanking from a spreadsheet? If so, with what format? > - Text as HTML should be offered as text/html, for the use of html > editing modes. > > - Rtf text should be offered also to org-mode, adding a new yank handler > to convert rtf format to org format. I am working on that. We could also > provide it to enriched-mode, but it could use very few properties of the > text. Anyway, this is not a Windows issue, and it still a little far away. Where we have both RTF and HTML, should we perhaps use HTML and pass it through shr, to produce text with faces, rather than raw HTML? Once RTF handler exists, we could use that instead, but having it rendered via HTML might be a useful option anyway. Anyway, all in all, this sounds like a good plan, thanks.