unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: yamaoka@jpl.org, 35383@debbugs.gnu.org
Subject: bug#35383: 27.0.50; Complete process of decoding Gnus group names
Date: Tue, 30 Apr 2019 06:55:00 +0300	[thread overview]
Message-ID: <83wojcrvu3.fsf@gnu.org> (raw)
In-Reply-To: <87sgu0h92o.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Mon, 29 Apr 2019 13:04:31 -0700)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: yamaoka@jpl.org,  35383@debbugs.gnu.org
> Date: Mon, 29 Apr 2019 13:04:31 -0700
> 
> >> Actually, maybe that's wrong. We don't care how the files are written,
> >> only that, after parsing, the group names are successfully _decoded_ to
> >> 'utf-8-emacs. Maybe I'm trying too hard?
> >
> > When you decode _any_ text by _any_ coding-system, the result is
> > _always_ utf-8-emacs, because utf-8-emacs is the internal
> > representation of characters and raw bytes in Emacs buffers and
> > strings.
> 
> I did know that much! I'm pretty bad at encoding, but not quite that
> bad.

Sorry, it was not clear to me, since you talked about "decoding to
utf-8-emacs", which is a kind of tautology.

> So you think Gnus' various *-file-coding-system options should
> default to 'utf-8-emacs rather than 'raw-text?

Not sure about all of them, I don't think I have a clear idea of what
they are used for.  The principle is that we use utf-8-emacs for files
where Emacs records its internal data, and whose primary role is to
allow Emacs to restore its internal data with maximum reliability.
One good example of this is auto-save files, where we use utf-8-emacs
regardless of the actual encoding of the file whose buffer is
auto-saved.

If this principle is not enough to make a decision, please point out
the specific variables you are unsure about, and I will take a look at
their actual usage.

> As per your other message, it sounds like active files written as
> 'raw-text will probably survive being read as 'utf-8-emacs. And if the
> user has previously customized those options to something else, the
> change in default value won't matter anyway.

That is true, but good defaults do matter to new users and new files.

And raw-text is almost never appropriate as the default for
human-readable text.

> What I meant by "trying too hard" is, maybe it's enough to just change
> the defaults, and not add any other error checking and guarantees?

What other checks and guarantees did you consider?  (Sorry, I didn't
read the entire thread, so maybe just point me to the message where
you described this.)





  reply	other threads:[~2019-04-30  3:55 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 18:39 bug#35383: 27.0.50; Complete process of decoding Gnus group names Eric Abrahamsen
2019-04-23  8:12 ` Katsumi Yamaoka
2019-04-23 19:55   ` Eric Abrahamsen
2019-04-24  8:06     ` Katsumi Yamaoka
2019-04-24 17:04       ` Eric Abrahamsen
2019-04-24 23:48         ` Katsumi Yamaoka
2019-04-25 16:10           ` Eric Abrahamsen
2019-04-26  5:21             ` Katsumi Yamaoka
2019-04-26  6:53               ` Eli Zaretskii
2019-04-26  8:08                 ` Katsumi Yamaoka
2019-04-26 10:55                   ` Eli Zaretskii
2019-04-29  4:05               ` Eric Abrahamsen
2019-04-29  4:07                 ` Eric Abrahamsen
2019-04-29 15:41                   ` Eli Zaretskii
2019-04-29 20:04                     ` Eric Abrahamsen
2019-04-30  3:55                       ` Eli Zaretskii [this message]
2019-04-30 17:03                         ` Eric Abrahamsen
2019-04-30 17:11                           ` Eli Zaretskii
2019-04-30 17:19                             ` Eric Abrahamsen
2019-04-30 17:44                               ` Eli Zaretskii
2019-04-30 18:17                                 ` Eric Abrahamsen
2019-04-29 15:38                 ` Eli Zaretskii
2019-05-13  0:32     ` Katsumi Yamaoka
2019-05-13 20:14       ` Eric Abrahamsen
2019-05-18 20:25         ` Eric Abrahamsen
2019-05-18 22:12           ` Basil L. Contovounesios
2019-05-18 23:23             ` Eric Abrahamsen
2019-05-19  1:03               ` Basil L. Contovounesios
2019-05-19  2:56                 ` Eric Abrahamsen
2019-05-19 17:02                   ` Eric Abrahamsen
2019-06-10 23:19                     ` Katsumi Yamaoka
2019-06-11  0:03                       ` Eric Abrahamsen
2019-06-11  4:33                       ` Eric Abrahamsen
2019-06-11  8:09                         ` Katsumi Yamaoka
2019-04-23 15:42 ` Andy Moreton
2019-04-23 21:42   ` Eric Abrahamsen
2019-04-23 22:58     ` Andy Moreton
2019-06-17  6:06 ` Eric Abrahamsen
2019-06-17 12:12   ` Deus Max
2019-06-17 16:22     ` Eric Abrahamsen
2019-06-19 20:57       ` Deus Max
2019-06-19 21:02       ` Deus Max
2019-06-19 21:40         ` Eric Abrahamsen
2019-06-20 13:00           ` Deus Max
2019-06-20 16:29             ` Eric Abrahamsen
2019-06-20 19:01               ` Deus Max
2019-06-20 19:16                 ` Eric Abrahamsen
2019-06-21 20:59                   ` Eric Abrahamsen
2019-06-22 14:44                     ` Deus Max
2019-06-22 16:09                       ` Eric Abrahamsen
2019-06-23 10:27                         ` Deus Max
2019-07-08  3:09                           ` Eric Abrahamsen
2019-07-08 19:46                             ` Deus Max
2019-07-23 23:52                               ` Eric Abrahamsen
2019-07-30 23:00                               ` Eric Abrahamsen
2019-08-01 12:07                                 ` Lars Ingebrigtsen
2019-08-01 16:22                                   ` Eric Abrahamsen
2019-08-03 21:53                                   ` Eric Abrahamsen
2019-09-27 14:58                                     ` Lars Ingebrigtsen
2019-06-19 21:28       ` Deus Max

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=83wojcrvu3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35383@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=yamaoka@jpl.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 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).