unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: 35383@debbugs.gnu.org
Subject: bug#35383: 27.0.50; Complete process of decoding Gnus group names
Date: Tue, 23 Apr 2019 16:42:05 +0100	[thread overview]
Message-ID: <vz11s1spw36.fsf@gmail.com> (raw)
In-Reply-To: <878sw1995f.fsf@ericabrahamsen.net>

On Mon 22 Apr 2019, Eric Abrahamsen wrote:

> This is part two and the completion of bug#33653, which changed Gnus's
> obarrays into hash tables, and group names from symbols to (encoded)
> strings. The commits in the recently-pushed "scratch/gnus-decoded"
> branch change group names to decoded strings.
>
> Bug 33653 was a mess for a few reasons: I partitioned the changes
> poorly, didn't call for testers, and it turned out that I was locally
> testing a mismash of that change plus a couple changes included in this
> branch, which hid some bugs.
>
> This time around I'll keep it cleaner: I'll locally test only this
> change in isolation, I'm writing a semi-interactive test suite for Gnus,
> and in a few weeks I'll rope in three or four users to road-test the
> changes. The upside is that, once these changes are stabilized and put
> in, it will eliminate a whole class of potential bugs.
>
> In the meantime I'm hanging this here as a placeholder. If any brave
> soul does decide to give it a test-run in the meantime, back up your
> .newsrc.eld file first!

There don;t seem to bnbe any problems with the .nersrc.eld, as I have
used the same file in emacs-26, master and scratch/gnus-decoded branches
without obvious problems.

There is a problem in the server buffer in the scratch/gnus-decoded buffer
with group names. In my setup:
1) Start gnus, and open the server buffer
2) Select the feedbase server. This is configured as:

  (gnus-secondary-select-methods
   '((nntp "feedbase"
           (nntp-open-connection-function nntp-open-tls-stream)
           (nntp-port-number 563)
           (nntp-address "feedbase.org"))
     ...

3) Note that some group names are not decoded correctly in the server
buffer. The group names are decoded properly in the article buffer.

For example, (showing only names with problems):

server buffer (master branch):

K    140: feedbase.blog.københavnsskiklub
K    208: feedbase.news.brk.høringer
K   2017: feedbase.news.dr.hovedstadsområdet


server buffer (scratch/gnus-decoded branch):

K    140: feedbase.blog.k\303\270benhavnsskiklub
K    208: feedbase.news.brk.h\303\270ringer
K   2017: feedbase.news.dr.hovedstadsomr\303\245det

The raw bytes (shown as escapes above) match the UTF-8 for the expected
characters, so the decoding is not quite right.

    AndyM






  parent reply	other threads:[~2019-04-23 15:42 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
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 [this message]
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=vz11s1spw36.fsf@gmail.com \
    --to=andrewjmoreton@gmail.com \
    --cc=35383@debbugs.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 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).