From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/34840
Path: main.gmane.org!not-for-mail
From: vvv@vsu.ru
Newsgroups: gmane.emacs.gnus.general
Subject: bug in encoded-word encoding
Date: 18 Feb 2001 14:46:46 +0300
Sender: owner-ding@hpc.uh.edu
Message-ID: <eyae7kkyc9.fsf@video.uic.vsu.ru>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1035170688 32351 80.91.224.250 (21 Oct 2002 03:24:48 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 03:24:48 +0000 (UTC)
Return-Path: <owner-ding@hpc.uh.edu>
Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1])
	by mailhost.sclp.com (Postfix) with ESMTP id 38EE7D049E
	for <jason@mastaler.com>; Sun, 18 Feb 2001 06:46:52 -0500 (EST)
Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5])
	by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id FAC23328;
	Sun, 18 Feb 2001 05:46:48 -0600 (CST)
Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 18 Feb 2001 05:46:09 -0600 (CST)
Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged))
	by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id FAA03024
	for <ding@hpc.uh.edu>; Sun, 18 Feb 2001 05:46:00 -0600 (CST)
Original-Received: from vsu.ru (relay1.vsu.ru [62.76.169.14])
	by mailhost.sclp.com (Postfix) with ESMTP id 35289D049E
	for <ding@gnus.org>; Sun, 18 Feb 2001 06:46:30 -0500 (EST)
Original-Received: from video.uic.vsu.ru ([62.76.169.38] verified)
  by vsu.ru (CommuniGate Pro SMTP 3.4b9)
  with ESMTP id 2404927 for ding@gnus.org; Sun, 18 Feb 2001 14:46:48 +0300
Original-To: ding@gnus.org
User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.6
Precedence: list
X-Majordomo: 1.94.jlt7
Original-Lines: 16
Xref: main.gmane.org gmane.emacs.gnus.general:34840
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:34840

Hi,

i wrote:

> sorry for wrong quote from RFC. i wonder, is this still a buggy
> behavior?

looks like yes:

 RFC2047> Ordinary ASCII text and 'encoded-word's may appear together in the
 RFC2047> same header field.  However, an 'encoded-word' that appears in a
 RFC2047> header field defined as '*text' MUST be separated from any adjacent
 RFC2047> 'encoded-word' or 'text' by 'linear-white-space'.

Best,
v.