[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: default charset for text/html selection in X11
From: |
Po Lu |
Subject: |
Re: default charset for text/html selection in X11 |
Date: |
Thu, 22 Jun 2023 19:48:46 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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.