Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: Shouldn't Gnus (er, W3) inline related images in <img src=cid:...>?
Date: Sun, 5 Mar 2000 09:24:52 -0500	[thread overview]
Message-ID: <200003051424.JAA03761@localhost.localdomain> (raw)
In-Reply-To: Karl Kleinpaste's message of "29 Feb 2000 16:40:20 -0500"

Karl Kleinpaste <karl@justresearch.com> writes:

> Quite a long time back, I recall there being some hackery done in Gnus,
> or perhaps W3, regarding proper inlining of images within a text/html
> message. As I see things today, in CVS-current 5.8.4, the inlining
> doesn't happen at all, and instead the cid:foo identifier is displayed in
> [square brackets] as the "content" of the text/html message. Oddly, even
> the content ID string dispalyed is mangled, being cut off at the first
> `.' -- is that perhaps the bug? Or is there some knob I'm supposed to
> have twisted in order to get the image to inline with the text/html
> directly? If you `C-d', you can see all the component parts, of course,
> but I wouldn't think I'd have to work that hard -- it's already supposed
> to show the image in question. Test message follows, using a smallish
> .gif image. "M-x w3-version RET" reveals "4.0pre.46", which is current in
> xemacs-packages.

Hrmm... Is the content-id supposed to have <...> around it?  Emacs/W3 just
looks for it raw.  Look at your messages buffer - do you see something like
"Unknown CID encountered: ..."?

-Bill P.



  reply	other threads:[~2000-03-05 14:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-29 21:40 Karl Kleinpaste
2000-03-05 14:24 ` William M. Perry [this message]
2000-03-05 14:35   ` Karl Kleinpaste
2000-04-20 20:26 ` Lars Magne Ingebrigtsen
2000-04-20 22:02   ` Michael Harnois
2000-04-20 22:53     ` Lars Magne Ingebrigtsen
2000-04-21 22:37       ` Michael Harnois
2000-04-22 12:14         ` Lars Magne Ingebrigtsen
2000-04-23 16:46           ` Michael Harnois
2000-08-10 18:48             ` Lars Magne Ingebrigtsen
2000-08-10 18:53               ` Roland Mas
2000-08-10 19:00                 ` Lars Magne Ingebrigtsen
2000-08-10 19:02                   ` Lars Magne Ingebrigtsen
2000-08-11  2:04                   ` Rene H. Larsen
2000-08-11  4:33                     ` ShengHuo ZHU
2000-08-11 13:17                       ` Kai Großjohann
2000-08-11 13:48                         ` ShengHuo ZHU
2000-08-11 21:03                           ` Kai Großjohann
2000-08-11 21:41                             ` ShengHuo ZHU
2000-08-13 16:07                               ` Kai Großjohann
2000-08-14  3:31                                 ` Daniel Pittman
2000-08-14 14:00                                   ` William M. Perry
2000-08-11 23:51                       ` Rene H. Larsen
2000-08-12  1:04                         ` Rene H. Larsen
2000-08-14 12:04                           ` `mm-quote-arg' and shell quoting in mailcap (was: Shouldn't...) Toby Speight
2000-08-15  0:35                             ` Rene H. Larsen
2000-08-15 12:51                               ` `mm-quote-arg' and shell quoting in mailcap Toby Speight
2000-12-04  1:46                               ` `mm-quote-arg' and shell quoting in mailcap (was: Shouldn't...) Greg Stark
2000-08-15 13:09                           ` Shouldn't Gnus (er, W3) inline related images in <img src=cid:...>? François Pinard

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

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

  git send-email \
    --in-reply-to=200003051424.JAA03761@localhost.localdomain \
    --to=wmperry@aventail.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).