all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: charles@aurox.ch (Charles A. Roelli)
Cc: 31062@debbugs.gnu.org
Subject: bug#31062: 26.0.91; warning on UTF-8 encoding of unibyte text
Date: Thu, 02 Sep 2021 10:52:35 +0200	[thread overview]
Message-ID: <87sfyn7418.fsf@gnus.org> (raw)
In-Reply-To: <m2po3e25g3.fsf@aurox.ch> (Charles A. Roelli's message of "Wed, 04 Apr 2018 20:26:52 +0200")

charles@aurox.ch (Charles A. Roelli) writes:

> (This test case assumes a locale-coding-system of utf-8-unix, and
> LANG: en_GB.UTF-8 or anything similar.)
>
> emacs -q
> C-x b test RET
> M-: (insert-byte 195 1) RET
> M-: (insert-byte 188 1) RET	> buffer text should look like \303\274
> C-x C-s /tmp/foo RET		> the path is irrelevant
>
> There's this warning:
>
> These default coding systems were tried to encode text
> in the buffer ‘test’:
>   (utf-8-unix (1 . 4194243) (2 . 4194236))
> However, each of them encountered characters it couldn’t encode:
>   utf-8-unix cannot encode these: \303 \274
>
> Is the text "(1 . 4194243) (2 . 4194236)" useful here?  It looks like
> it's there by accident.  If it is helpful, could someone please
> explain what it means?

I've now made this warning more readable (and informative) by formatting
it as a table, and saying what the data means in Emacs 28.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-09-02  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 18:26 bug#31062: 26.0.91; warning on UTF-8 encoding of unibyte text Charles A. Roelli
2018-04-04 19:20 ` Eli Zaretskii
2018-04-05 18:27   ` Charles A. Roelli
2018-04-05 18:47     ` Eli Zaretskii
2018-04-08  9:49       ` Charles A. Roelli
2021-09-02  8:52 ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfyn7418.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=31062@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.