unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com,  emacs-devel@gnu.org,
	Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: default charset for text/html selection in X11
Date: Thu, 22 Jun 2023 14:14:13 +0200	[thread overview]
Message-ID: <87a5wrg0dm.fsf@gmail.com> (raw)
In-Reply-To: <831qi34xmv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Jun 2023 13:08:56 +0300")

>>>>> On Thu, 22 Jun 2023 13:08:56 +0300, Eli Zaretskii <eliz@gnu.org> said:
    >> (get-text-property 0 'foreign-selection html) => STRING
    >> 
    >> but itʼs definitely a utf-8 string, not iso-latin-1.

    Eli> Does that depend on the locale, per chance?  Could you try changing
    Eli> the locale's codeset and looking at what Chromium produces then?

LC_ALL=C chromium

makes no difference, although

LC_ALL=C firefox

results in U+00A0 being transferred as U+0020, but something like

U+2764 U+FE0F still gives me utf-8 constituent bytes:

\xe2\x9d\xa4\xef\xb8\8f

so Iʼm thinking that using `gui-get-selection' is the right thing. Lars,
can you shed any light on why yank-media uses
`gui-backend-get-selection' rather than `gui-get-selection'?

Robert
-- 



  reply	other threads:[~2023-06-22 12:14 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
2023-06-22 12:27             ` Robert Pluim
2023-06-22 10:08       ` Eli Zaretskii
2023-06-22 12:14         ` Robert Pluim [this message]
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=87a5wrg0dm.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).