all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 59341@debbugs.gnu.org
Subject: bug#59341: 29.0.50; Lisp files with other encoding than UTF-8?
Date: Fri, 18 Nov 2022 13:59:18 +0200	[thread overview]
Message-ID: <83mt8obhih.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm9CLLZ4OayeHqsuUN7F725fqTvObobsPxhgT0VjcPKMw@mail.gmail.com> (message from Stefan Kangas on Fri, 18 Nov 2022 03:11:15 -0800)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Fri, 18 Nov 2022 03:11:15 -0800
> Cc: 59341@debbugs.gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > However, I think we should add a note in the Commentary section about
> > these subtleties, so that whoever next is bothered about this will be
> > able to have their questions answered.
> 
> How about adding something like this to the Commentary section of the
> relevant files (i.e. the list I posted originally):
> 
> ;; Note that this file contains non-Unicode characters, which are
> ;; needed for certain conversions.  See the discussion in Bug#59341.

I'd rather describe the reason in more detail there.

I can do this myself if you prefer.





  reply	other threads:[~2022-11-18 11:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 19:38 bug#59341: 29.0.50; Lisp files with other encoding than UTF-8? Stefan Kangas
2022-11-17 19:54 ` Eli Zaretskii
2022-11-18  4:14   ` Stefan Kangas
2022-11-18  7:57     ` Eli Zaretskii
2022-11-18 11:11       ` Stefan Kangas
2022-11-18 11:59         ` Eli Zaretskii [this message]
2022-11-18 17:14           ` Stefan Kangas
2022-11-19  9:26             ` Eli Zaretskii
2022-11-18 16:53         ` Drew Adams
2022-11-18 17:16           ` Stefan Kangas
2022-11-18 16:49       ` Drew Adams

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=83mt8obhih.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59341@debbugs.gnu.org \
    --cc=stefankangas@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 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.