From: Cecilio Pardo <cpardo@imayhem.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71909@debbugs.gnu.org
Subject: bug#71909: 30.0.60; yank-media on MS-Windows
Date: Thu, 24 Oct 2024 01:13:49 +0200 [thread overview]
Message-ID: <51b40c99-1104-4fbd-bf58-dde7d4c0791a@imayhem.com> (raw)
In-Reply-To: <8634l54cp4.fsf@gnu.org>
Getting back to this, I have been checking what some programs (a couple
of nonfree ones) provide on the clipboard for different media types.
GIMP | Copy pixels | PNG
LibreOffice | Copy vectorial object | PNG, GDIMetafile
LibreOffice | Copy embedded image | PNG
LibreOffice | Copy text | RTF, HTML, ODT
LibreOffice | Copy equation | RTF
LibreOffice | Copy Calc cells | PNG, RTF, HTML, GDIMetafile
Firefox | Copy Image | DIBV5
Firefox | Copy Text | HTML, RTF
Krita | Copy pixels | PNG
Inkscape | Copy vector | SVG, PNG, PDF, Postscript
Windows Paint | Copy pixels | PNG
Acrobat Reader | Copy text | RTF
They offer more formats, but in many cases they are not really there
(the yank-media code knows about this, and in fact checks every type to
purge the empty ones from list), or are propietary.
So I think we should stick to these:
- 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.
- 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.
- 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.
next prev parent reply other threads:[~2024-10-23 23:13 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 ` Cecilio Pardo [this message]
2024-10-24 7:18 ` bug#71909: 30.0.60; yank-media on MS-Windows 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
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=51b40c99-1104-4fbd-bf58-dde7d4c0791a@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).