all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuchen Pei <id@ypei.org>
To: emacs-devel@gnu.org
Subject: Coding warning attributes to wrong char
Date: Sat, 17 Jun 2023 14:22:18 +1000	[thread overview]
Message-ID: <87bkhebtvp.fsf@ypei.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

Could reprod in 28.2 and 29.0.91:

1. Open the attached text file, or save the following in a file and open
   it (hopefully displayed correctly here in your email client...)
--8<---------------cut here---------------start------------->8---
   The issue is not with ’, but the  (nul, insert with C-q C-@).
--8<---------------cut here---------------end--------------->8---

2. M-x set-buffer-file-coding-system utf-8 <RET>

3. A warning appears, attributing the issue to the ’, the quote (in the
   following I have replaced the chars with literal strings

--8<---------------cut here---------------start------------->8---
These default coding systems were tried to encode the following
problematic characters in the buffer ‘encoding.txt’:
  Coding System           Pos  Codepoint  Char
  utf-8-unix               23  #x3FFFE2   \342
                           24  #x3FFF80   \200
                           25  #x3FFF99   \231

However, each of them encountered characters it couldn’t encode:
  utf-8-unix cannot encode these: \342 \200 \231

Click on a character (or switch to this window by ‘C-x o’
and select the characters by RET) to jump to the place it appears,
where ‘C-u C-x =’ will give information about it.

Select one of the safe coding systems listed below,
or cancel the writing with C-g and edit the buffer
   to remove or modify the problematic characters,
or specify any other coding system (and risk losing
   the problematic characters).

  raw-text no-conversion
--8<---------------cut here---------------end--------------->8---

Despite the warning, the correct fix is to remove the nul character.

This can be quite misleading, especially when one wants to fix encoding
issues in big text files.


[-- Attachment #2: encoding.txt --]
[-- Type: text/plain, Size: 43 bytes --]

The issue is not with ’, but the \0 (nul).

[-- Attachment #3: Type: text/plain, Size: 131 bytes --]


Best,
Yuchen

-- 
PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
          <https://ypei.org/assets/ypei-pubkey.txt>

             reply	other threads:[~2023-06-17  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  4:22 Yuchen Pei [this message]
2023-06-17  6:30 ` Coding warning attributes to wrong char Eli Zaretskii
2023-06-17  9:20   ` Yuchen Pei

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=87bkhebtvp.fsf@ypei.org \
    --to=id@ypei.org \
    --cc=emacs-devel@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 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.