From: Karl EICHWALDER <ke@gnu.franken.de>
Cc: ding@gnus.org
Subject: Re: de .* and gnus-group-posting-charset-alist
Date: 12 Dec 1999 07:39:35 +0100 [thread overview]
Message-ID: <shzovg7jdk.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "11 Dec 1999 21:20:24 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
| I discussed with the guys in de.comm.software.newsreader, and they
| explained to me that Latin 1 chars in headers must be escaped
Yes, of course. gnus-msg.el and/or message.el has to take care about
it. AFAIK, encoding header lines is independend from the encoding of
the body.
| * Tell Gnus to always encoding Latin 1 chars in de.ALL. This gives us
| correct postings with possibly superfluous encoding.
|
| * Tell Gnus to never encode Latin 1 chars in de.ALL. This gives
| problems for people with Latin 1 characters in their name.
|
| * Like previous, but forbid use of non-ASCII characters in headers.
Please, implement the 4th option:
* Message bodies: Tell Gnus to never encode Latin 1 chars in de.ALL.
Header lines: Encode non-ASCII characters.
--
work : ke@suse.de |
: http://www.suse.de/~ke/ | ------ ,__o
personal: ke@gnu.franken.de | ------ _-\_<,
: http://www.franken.de/users/gnu/ke/ | ------ (*)/'(*)
next prev parent reply other threads:[~1999-12-12 6:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 20:45 Karl EICHWALDER
1999-12-08 6:50 ` Florian Weimer
1999-12-11 20:20 ` Kai Großjohann
1999-12-12 6:39 ` Karl EICHWALDER [this message]
1999-12-12 9:22 ` Florian Weimer
1999-12-12 11:46 ` Bjørn Mork
1999-12-13 12:04 ` Christophe Cuq
1999-12-12 10:47 ` Kai Großjohann
1999-12-12 15:54 ` Karl EICHWALDER
1999-12-12 11:07 ` Per Abrahamsen
1999-12-12 11:15 ` Florian Weimer
1999-12-13 9:08 ` Per Abrahamsen
1999-12-13 23:51 ` Karl EICHWALDER
1999-12-14 8:48 ` Per Abrahamsen
1999-12-21 20:06 ` Kai Großjohann
1999-12-21 20:30 ` Florian Weimer
1999-12-21 21:32 ` Kai Großjohann
1999-12-23 20:30 ` Florian Weimer
1999-12-21 20:47 ` Per Abrahamsen
1999-12-22 0:07 ` Russ Allbery
1999-12-22 0:52 ` Stainless Steel Rat
1999-12-14 20:18 ` smarkacz
1999-12-14 20:56 ` Florian Weimer
1999-12-17 11:49 ` Toby Speight
1999-12-18 19:33 ` Florian Weimer
1999-12-19 10:47 ` Per Abrahamsen
1999-12-19 18:23 ` Karl EICHWALDER
[not found] ` <ug0x1bxde.fsf@lanber.ca <shvh5uhjsf.fsf@tux.gnu.franken.de>
1999-12-20 11:24 ` Per Abrahamsen
1999-12-20 23:22 ` Florian Weimer
1999-12-21 20:23 ` Florian Weimer
1999-12-20 18:20 ` Karl EICHWALDER
1999-12-15 7:20 ` Per Abrahamsen
1999-12-17 8:53 ` Hrvoje Niksic
1999-12-21 20:08 ` Kai Großjohann
1999-12-21 20:29 ` Florian Weimer
1999-12-21 21:31 ` Kai Großjohann
1999-12-22 10:10 ` Hrvoje Niksic
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=shzovg7jdk.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).