Attachments getting wrong encoding when saved to disk
kehoea at parhasard.net
Sat Jan 13 06:54:15 EST 2007
Ar an naoiú lá de mí Eanair, scríobh Mats Lidell:
> >>>>> Aidan wrote:
> Aidan> Is this in the attachment names, or in the attachment contents?
> The names. The content is OK. When I save an attachments I have to
> remove all locale chars and then I'm safe.
> Or I can rename the file after saving but that takes longer to do and
> the result is the same. I can't just use the file in the
> attachment. And I can't invoke an external program on the attachment
> from within gnus because the external program is looking for the wrong
> file. (Or so it seems anyway.)
Can you point me to an example? An mbox file would be ideal. When I have an
mbox file containing the below (where \303 and \241 stand for the octets
with those octal code on disk):
I can save it to disk, and the prompted file name is
aidan-contrÃ¡ct-work-2006-12-10.pdf , and that’s the file name that appears
on disk (my file-name-coding-system is utf-8). That means the filename part
of the content-disposition header is treated as having 'binary encoding,
which is well and good, since the character set hasn’t been specified using
When I was in the scouts, the leader told me to pitch a tent. I couldn't
find any pitch, so I used creosote.
More information about the XEmacs-Beta