unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Dmitri Minaev" <minaev@gmail.com>
To: "Girish Kulkarni" <geeree@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why is MIME hard?
Date: Fri, 28 Sep 2007 12:17:37 +0500	[thread overview]
Message-ID: <b6c377310709280017x4d91c0d1yde1a9ed00f0f38cf@mail.gmail.com> (raw)
In-Reply-To: <1190902460.055800.73670@y42g2000hsy.googlegroups.com>

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

On 9/27/07, Girish Kulkarni <geeree@gmail.com> wrote:
> I know this has been asked here many times before, but I'd be glad if
> someone explains in a less esoteric manner.

I'll take the opportunity to add a couple of questions :).

In the last couple of weeks, I've been playing with Wanderlust. It
supports MIME using FLIM and SEMI libraries. My impressions are
positive as of yet, in spite of the discouraging complexity of the
whole set of packages, but I had some problems with MIME messages.

Say, I receive a message with the following MIME structure (as seen in mutt):

1 <no description>                 [multipa/alternativ, 7bit, 9.0K]
2 ├─><no description>        [text/plain, quoted, koi8-r, 0.8K]
3 └─><no description>        [text/html, quoted, koi8-r, 7.9K]
4 image001.jpg                        [image/jpeg, base64, 104K]

First, the message was retrieved partially, but later I re-fetched it
completely and the cached copy is complete. However, Wanderlust shows
only parts 1, 1.1 and 1.2. Part 2 is not seen. Is this a bug in FLIM
or am I missing something?

Another message, which I wrote in WL, looks like this (irrelevant
headers omitted):

=====================
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka)
FLIM/1.14.6 (Marutamachi) APEL/10.7 Emacs/23.0.0 (i686-pc-linux-gnu)
MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: dmitri.minaev@sgs.com
X-OriginalArrivalTime: 24 Sep 2007 13:03:05.0159 (UTC)
FILETIME=[3EE7CD70:01C7FEAB]

Спасибо.
=====================

When I open this message in WL, the actual text is simply missing.
Could it be because of the wrong Content-Transfer-Encoding? How do I
fix it?

Emacs: "GNU Emacs 23.0.0.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll
bars) of 2007-08-13 on cera"
Wanderlust: "Wanderlust/2.14.0 (Africa)"
FLIM: Version 1.14.6 (Marutamachi)
SEMI: Version 1.14.6 (Maruoka)
APEL: Version 10.7


Thank you.


-- 
With best regards,
Dmitri Minaev

Russian history blog: http://minaev.blogspot.com

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

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

  parent reply	other threads:[~2007-09-28  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 14:14 Why is MIME hard? Girish Kulkarni
2007-09-27 19:15 ` Reiner Steib
2007-09-27 20:52   ` Eli Zaretskii
2007-09-28  7:17 ` Dmitri Minaev [this message]
2007-09-28 15:42 ` Stefan Monnier
2007-09-30 13:28 ` Tim X
2007-09-30 14:38   ` Reiner Steib
2007-10-02  7:03     ` Tim X

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6c377310709280017x4d91c0d1yde1a9ed00f0f38cf@mail.gmail.com \
    --to=minaev@gmail.com \
    --cc=geeree@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).