Re: bug in encoded-word encoding

[ShengHuo ZHU <zsh@cs.rochester.edu>]

vvv@vsu.ru writes:

> 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'.

You use a wrong quote. It should be the following one.

,----[ RFC2047 ]
| (3) As a replacement for a 'word' entity within a 'phrase', for example,
|     one that precedes an address in a From, To, or Cc header.  The ABNF
|     definition for 'phrase' from RFC 822 thus becomes:
| 
|     phrase = 1*( encoded-word / word )
| 
|     In this case the set of characters that may be used in a "Q"-encoded
|     'encoded-word' is restricted to: <upper and lower case ASCII
|     letters, decimal digits, "!", "*", "+", "-", "/", "=", and "_"
|     (underscore, ASCII 95.)>.  An 'encoded-word' that appears within a
|     'phrase' MUST be separated from any adjacent 'word', 'text' or
|     'special' by 'linear-white-space'.
`----

Since it is a phrase, special characters ("." and others) must be in
quoted string to use within a word (see RFC 822).

But there may be another bug, encoded words in a quoted string. I am
not sure how to encode a quoted string with non-ASCII characters.
Anyone knows?

ShengHuo

-- 
(setq gnus-posting-styles 
      '((".*" (signature (format "(setq gnus-posting-styles 
      '%S)" gnus-posting-styles)))))