rfc2047 changes

rfc2047 changes

[Lars Magne Ingebrigtsen]

On gnus-bug, a user pointed out the following:
 
7. Conformance

   A mail composing program claiming compliance with this specification
   MUST ensure that any string of non-white-space printable ASCII
   characters within a '*text' or '*ctext' that begins with "=?" and
   ends with "?=" be a valid 'encoded-word'.  ("begins" means: at the
   start of the field-body, immediately following 'linear-white-space',
   or immediately following a "(" for an 'encoded-word' within '*ctext';
   "ends" means: at the end of the field-body, immediately preceding
   'linear-white-space', or immediately preceding a ")" for an
   'encoded-word' within '*ctext'.)  In addition, any 'word' within a
   'phrase' that begins with "=?" and ends with "?=" must be a valid
   'encoded-word'.

That is, if I type "=?hello?=, sailor" in a Subject header, then the
first word should be encoded.  It's rather unlikely, but the change
made it necessary to delve into the bowels of rfc2047.el and hack
away a bit.  If I broke something, give a holler...    
 
-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: rfc2047 changes

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> That is, if I type "=?hello?=, sailor" in a Subject header, then the
> first word should be encoded.  It's rather unlikely, but the change
> made it necessary to delve into the bowels of rfc2047.el and hack
> away a bit.  If I broke something, give a holler...    

Found one bug.  Sending via the Agent encoded things twice.

Hm.  Fixed that, but I'm starting to thing that this might not have
been a good idea.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: rfc2047 changes

[Katsumi Yamaoka]

>>>>> In <m3hductj1n.fsf@quimbies.gnus.org>
>>>>>	Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:

>> That is, if I type "=?hello?=, sailor" in a Subject header, then the
>> first word should be encoded.  It's rather unlikely, but the change
>> made it necessary to delve into the bowels of rfc2047.el and hack
>> away a bit.  If I broke something, give a holler...

> Found one bug.  Sending via the Agent encoded things twice.

> Hm.  Fixed that, but I'm starting to thing that this might not have
> been a good idea.  :-)

Phew, I've merged that change into my version of rfc2047.el. :)

ftp://ftp.jpl.org/pub/tmp/rfc2047.el.gz

I will install it in Gnus CVS by the end of today (in Japan).
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: rfc2047 changes

[Lars Magne Ingebrigtsen]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Phew, I've merged that change into my version of rfc2047.el. :)
>
> ftp://ftp.jpl.org/pub/tmp/rfc2047.el.gz
>
> I will install it in Gnus CVS by the end of today (in Japan).

Cool.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen