Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ichimusai <ichi@ichimusai.org>
Subject: Re: HTML render like crap in Emacs/Gnus :(
Date: Sun, 05 Jan 2003 14:42:47 +0100	[thread overview]
Message-ID: <ulm1zww4o.fsf@ichimusai.org> (raw)
In-Reply-To: <adieitjz.fsf@optushome.com.au>

urfaust <urfaust@optushome.com.au> writes:

> Ichimusai <ichi@ichimusai.org> writes:
>
>> People frequently send mail to lists I am on in text/html and it
>> looks like crap in Emacs/Gnus.
>
> HTML is evil. I always delet html email. 

You have that option, I don't.

> It is usually from spammers, nigerian conmen or technically
> challenged people. None of these are people I wish to recieve email
> from

You obviously are not in the situation where I am where you have
several hundred people you need to communicate with email wise and
they either have no clue what HTML is or they send my mail on to the
sysadmin who ignores it saying I am the only complaint out of everyone
they communicates with.

>> Should I install W3? Last time I tried it stopped rendering
>> completely only showing a status line with an error and then it
>> showed the raw
>
> W3 handles most html. If there is large amounts of machine generated
> ( ie : FrontPurge) Javascript, then it may barf. If that happens, it
> is simple to edit the html in Emacs until it is readable.

Which is about every mail send out from Outlook / Outlook Express
which literally everyone in a corporated environment uses. Sigh.

It's not even proper HTML. It is MSHTML.

I could just edit it myself if I saw the HTML code, but I never see
the HTML. When I press enter on it in the summary it is rendered and I
can't seem to be able to display it raw somewhere. All I see is a
mail, it is rendered, the font is changed into some ariel shite, the
quoted material and the new material are all reflowed into a soup that
is impossible to discern.

It does not make new paragraphs on a <p> it does not end lines on a
<br>. It is completely oblivious to > as a quote marker or
<blockquot>. If it just left it alone it would be fine, but I do not
know how to turn it off. I makes a bloody mess of everything not plain
text, there is something cheesy going on as well when people use MIME
in news but I have no idea what is happening.

-- 
AA #769 ICQ: 1645566 Yahoo: Ichimusai AOL: Ichimusai1972 MSN: Ichimusai 
IRC: Ichimusai#AmigaSWE@IRCnet URL: http://www.ichimusai.org/  
Virgo: (Aug. 23-Sept. 22): Certain shortcomings in your education and
upbringing cause you to read meaning into the relationships among various
celestial bodies.


       reply	other threads:[~2003-01-05 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uof6v23v9.fsf@ichimusai.org>
     [not found] ` <adieitjz.fsf@optushome.com.au>
2003-01-05 13:42   ` Ichimusai [this message]
     [not found]     ` <87wul03jrn.fsf@mail.paradoxical.net>
2003-01-19 21:46       ` Lucas
     [not found]       ` <m33cnov8kv.fsf@defun.localdomain>
2003-01-20  5:10         ` Josh Huber
     [not found] ` <87vg13smd0.fsf@kuntu.zangpo.org>
2003-01-05 14:45   ` Adam P.
     [not found] ` <m31y3reove.fsf@neo.loria>
     [not found]   ` <uptrbwwgn.fsf@ichimusai.org>
2003-01-05 15:16     ` Kai Großjohann
2003-01-05 15:35       ` Ichimusai

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=ulm1zww4o.fsf@ichimusai.org \
    --to=ichi@ichimusai.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).