Re: Gnus and international attachment names

Re: Gnus and international attachment names

[Pavel Janík]

[How should we attach files with international names and how to display
them in Gnus.]

   From: Dave Love <d.love@dl.ac.uk>
   Date: 17 Apr 2001 23:50:29 +0100

   >  PJ>  Content-Type: application/octet-stream;
   >  PJ>  	name="=?iso-8859-2?Q?Korekura_Vesel=EDk=2Ezip?="
   > 
   > Does the MIME RFC allow that?  I thought encoded words weren't allowed
   > there.

But how do you store international names in it?

This is how Oort Gnus attach file which name is ěščřžýáíé.txt:

 Content-Disposition: attachment;
   filename*=iso-8859-2''%ec%b9%e8%f8%be%fd%e1%ed%e9.txt

This is displayed as text/plain;
iso-8859-2''%ec%b9%e8%f8%be%fd%e1%ed%e9.txt in the Gnus from CVS and
correctly displayed in Oort.

This is bad (for 21).

Gnus 5.9.0 do attach it as:

 Content-Disposition: attachment; filename=ěščřžýáíé.txt

When I try to save the mail with this in it, it is saved (from Oort and
also from 5.9.0) with magic \202 before each iso-8859-2 letter in it. This
is bad too :-(

I do not know though, which one is the correct behavior. What is the clean
way of attaching the file, whose name is ěščřžýáíé.txt and how to do that
with either Oort Gnus or Gnus from Emacs 21?

I'd be happy to test everything you suggest.
-- 
Pavel Janík

Sounds like a "bug waiting to be implemented" ;)
                  -- Rik van Riel in linux-kernel

Re: Gnus and international attachment names

[Dave Love]

>>>>> "PJ" == Pavel Janík <Pavel@Janik.cz> writes:

 >> Does the MIME RFC allow that?  I thought encoded words weren't allowed
 >> there.

 PJ> But how do you store international names in it?

Perhaps you're not supposed to.  My filing system may not grok
Latin-2.

 PJ> When I try to save the mail with this in it, it is saved (from
 PJ> Oort and also from 5.9.0) with magic \202 before each iso-8859-2
 PJ> letter in it. This is bad too :-(

What do you mean by `save'?  emacs-mule is appropriate for encoding
complete messages or folders on disc, if that's what you mean.

Re: Gnus and international attachment names

[Pavel Janík]

   From: Dave Love <d.love@dl.ac.uk>
   Date: 22 Apr 2001 19:00:00 +0100

Hi,

   > Perhaps you're not supposed to.  My filing system may not grok
   > Latin-2.

:-( What if I receive such file?

   >  PJ> When I try to save the mail with this in it, it is saved (from
   >  PJ> Oort and also from 5.9.0) with magic \202 before each iso-8859-2
   >  PJ> letter in it. This is bad too :-(
   > 
   > What do you mean by `save'?  emacs-mule is appropriate for encoding
   > complete messages or folders on disc, if that's what you mean.

By save I meant C-o in the summary buffer. This is buggy in both Oort and
5.9.0.
-- 
Pavel Janík

If you just recently "discovered" VIM, you aren't observant
enough to learn Emacs.
                  -- Galen Boyer in alt.religion.emacs

Re: Gnus and international attachment names

[Bjørn Mork]

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Pavel@Janik.cz (Pavel Janík) writes:
>    From: Dave Love <d.love@dl.ac.uk>
> 
>    > Perhaps you're not supposed to.  My filing system may not grok
>    > Latin-2.
> 
> :-( What if I receive such file?

Then you complain to the sender, asking him to use a MIME compliant
mail client. From RFC2047:

   + An 'encoded-word' MUST NOT be used in parameter of a MIME
     Content-Type or Content-Disposition field, or in any structured
     field body except within a 'comment' or 'phrase'.



[-- Attachment #2: Type: text/plain, Size: 7 bytes --]


Bjørn

Re: Gnus and international attachment names

[Pavel Janík]

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

   From: "Bjørn Mork" <bmork@dod.no>
   Date: 22 Apr 2001 22:01:56 +0200

Hi,

   > Then you complain to the sender, asking him to use a MIME compliant
   > mail client. From RFC2047:
   > 
   >    + An 'encoded-word' MUST NOT be used in parameter of a MIME
   >      Content-Type or Content-Disposition field, or in any structured
   >      field body except within a 'comment' or 'phrase'.

thank you for this reference. This is what we were looking for :-)

So the bug report is now:

Gnus 5.9.0 and Oort too allow to attach a file which has ISO 8859-2
characters in its name. Oort will attach it as:

Content-Disposition: attachment;
  filename*=iso-8859-2''%ec%b9%e8%f8%be%fd%e1%ed%e9.txt

[-- Attachment #2: Type: text/plain, Size: 409 bytes --]


So, does this really mean that I'm not able to send the file with this name
via attachment if I do want to be compliant with all MIME RFCs? BTW - where
is the description of this style of coding of filename* parameter? What
does filename* really mean?
-- 
Pavel Janík

UNIX is basically a simple operating system, but you have to be a genius to
understand the simplicity.
                  -- Dennis Ritchie

Re: Gnus and international attachment names

[Eli Zaretskii]

On 22 Apr 2001, Pavel =?iso-8859-2?q?Jan=EDk?= wrote:

>    > Perhaps you're not supposed to.  My filing system may not grok
>    > Latin-2.
> 
> :-( What if I receive such file?

I don't know; I don't think we have ever discussed this.  Perhaps Emacs 
should prompt for a different name?

Re: Gnus and international attachment names

[Lars Magne Ingebrigtsen]

Pavel@Janik.cz (Pavel Janík) writes:

> Gnus 5.9.0 and Oort too allow to attach a file which has ISO 8859-2
> characters in its name. Oort will attach it as:
>
> Content-Disposition: attachment;
>   filename*=iso-8859-2''%ec%b9%e8%f8%be%fd%e1%ed%e9.txt
> So, does this really mean that I'm not able to send the file with this name
> via attachment if I do want to be compliant with all MIME RFCs?

No, this is actually compliant.  Only with RFC2231, and not RFC2047. 

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