From: Po Lu <luangruo@yahoo.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: default charset for text/html selection in X11
Date: Thu, 22 Jun 2023 19:48:46 +0800 [thread overview]
Message-ID: <87v8ffzpi9.fsf@yahoo.com> (raw)
In-Reply-To: <87edm3g90e.fsf@gmail.com> (Robert Pluim's message of "Thu, 22 Jun 2023 11:07:45 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> It does.
Thanks. The bug lies in Chromium, not Emacs.
> Po Lu> The ICCCM clearly states that:
>
> Po Lu> STRING as a type or a target specifies the ISO Latin-1 character set
> Po Lu> plus the control characters TAB (octal 11) and NEWLINE (octal 12.)
> Po Lu> The spacing interpretation of TAB is context dependent. Other ASCII
> Po Lu> control characters are explicitly not included in STRING at the
> Po Lu> present time.
>
> Iʼm not about to contradict the ICCCM, but `gui-get-selection' does
> the following
>
> ;; Guess at the charset for types like text/html
> ;; -- it can be anything, and different
> ;; applications use different encodings.
> ((string-match-p "\\`text/" (symbol-name data-type))
> (decode-coding-string
> data (car (detect-coding-string data))))
> ;; Do nothing.
>
> I took a closer look, and `yank-media' does the wrong thing, but
> `(yank-media-types t)' and selecting "text/html" does the right
> thing. The difference is that the former uses
> `gui-backend-get-selection', and the latter uses `gui-get-selection',
> and thus does the auto-detection.
If this does solve the problem, please modify yank-media in such a
manner. It will make Emacs more robust against non-compliant selection
owners, which is always welcome.
next prev parent reply other threads:[~2023-06-22 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 15:51 default charset for text/html selection in X11 Robert Pluim
2023-06-21 17:13 ` Eli Zaretskii
2023-06-22 0:56 ` Po Lu
2023-06-22 3:37 ` Po Lu
2023-06-22 7:23 ` Robert Pluim
2023-06-22 7:57 ` Po Lu
2023-06-22 9:07 ` Robert Pluim
2023-06-22 11:48 ` Po Lu [this message]
2023-06-22 12:27 ` Robert Pluim
2023-06-22 10:08 ` Eli Zaretskii
2023-06-22 12:14 ` Robert Pluim
2023-06-22 12:26 ` Yuri Khan
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=87v8ffzpi9.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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).