unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 72442@debbugs.gnu.org
Subject: bug#72442: 31.0.50; Gnus or message.el doesn't handle international message reply subject prefixes and insults users
Date: Sat, 03 Aug 2024 18:43:11 +0300	[thread overview]
Message-ID: <868qxdvchc.fsf@gnu.org> (raw)
In-Reply-To: <87o769n3y8.fsf@> (bug-gnu-emacs@gnu.org)

> Date: Sat, 03 Aug 2024 16:14:39 +0300
> From:  Björn Bidar via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> Gnus doesn't handle international message reply prefixes as opposed
> to Re: or it's variants.
> 
> An example would be `gnus-simpliy-subject-re' which threats English
> subject prefixes.
> 
> Message.el doesn't do so either (by default) I don't think it makes
> sense to open a separate bug about this but please reply that should be
> done.
> 
> The message manual also judges users for using localized variants of
> "Re: " by calling them "nincompoops" for using these "abominations"
> which it says are "meaningless and evil".
> 
> The offending text can be found in the documentation for
> `message-subject-re-regexp' in the chapter "3.1 Message Headers".

FWIW, Rmail does support the various ways of saying "Re:", so the code
could be lifted from there.





       reply	other threads:[~2024-08-03 15:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o769n3y8.fsf@>
2024-08-03 15:43 ` Eli Zaretskii [this message]
2024-08-03 16:58   ` bug#72442: 31.0.50; Gnus or message.el doesn't handle international message reply subject prefixes and insults users Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87ed75lf09.fsf@>
2024-08-03 17:19     ` Eli Zaretskii
2024-08-20  9:46       ` Robert Pluim
2024-08-20 12:20         ` Eli Zaretskii
2024-08-20 13:56           ` Robert Pluim
2024-08-21 10:21             ` Francesco Potortì
2024-08-22 11:37             ` Robert Pluim
2024-08-22 12:04               ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 12:15               ` Eli Zaretskii
2024-08-27 15:50                 ` Robert Pluim
2024-08-27 16:39                   ` Eli Zaretskii
     [not found]               ` <66c7296a.a70a0220.2590d7.c939SMTPIN_ADDED_BROKEN@mx.google.com>
2024-08-22 13:14                 ` Robert Pluim
2024-08-23  5:39                   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                   ` <66c8208e.050a0220.16a63b.3a8cSMTPIN_ADDED_BROKEN@mx.google.com>
2024-08-23  8:00                     ` bug#72442: : " Robert Pluim
2024-08-03 13:14 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=868qxdvchc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72442@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    /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).