From: Karl Kleinpaste <karl@justresearch.com>
Subject: text/html parse failure
Date: 21 Jan 2000 14:52:01 -0500 [thread overview]
Message-ID: <vxkbt6fqk2m.fsf@beaver.jprc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Below are two messages, which I stole out of a mailing list and then
hacked on manually in a different personal group until I got to a
point where one difference between them determines whether they parse
correctly as HTML or not.
The first one displays as a bunch of raw (but oddly quote-colorized :-)
HTML directives. The second one displays as properly parsed and
formatted text. The difference between them is the presence or
absence of two lines, which looks to me like rather uneventful text.
In fact, one can add or delete nearly any single <div></div> segment
to or from these messages, to toggle success of HTML parsing and
display. I do not understand this at all.
I am almost surely looking at a W3 error, but since I found it within
Gnus, I figured I'd ask here first.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: difference between successful & unsuccessful HTML parse & display. --]
[-- Type: text/x-patch, Size: 960 bytes --]
--- 4101 Fri Jan 21 14:42:45 2000
+++ 4103 Fri Jan 21 14:43:27 2000
@@ -1,11 +1,11 @@
X-Gnus-Mail-Source: file:/var/spool/mail/karl
-Message-ID: <000c01bf6440$12ac0090$ed06830a@pheugh.baughre>
+Message-ID: <000c01bf6440$12ac0090$ed06830a@bletch.pheugh.baughre>
To: karl
MIME-Version: 1.0
Date: Fri, 21 Jan 2000 11:48:13 -0700
From: karl@justresearch.com
Reply-to: teaparty@onelist.com
-Subject: test 1
+Subject: test 2
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0009_01BF6405.65F48140"
Content-Transfer-Encoding: 8bit
@@ -30,8 +30,6 @@
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Just Looking Things Over.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
-<DIV><FONT size=2><A
-href="mailto:steve_tassio@csgsystems.com">steve_tassio@csgsystems.com</A></FONT></DIV>
<DIV><FONT size=2>I am America - Don't Tread On Me!</FONT></DIV>
<DIV><FONT size=2><BR>Brothers in Christ and Sons of Liberty<BR>Steve
Tassio</FONT></DIV>
[-- Attachment #3: Type: message/rfc822, Size: 1373 bytes --]
[-- Attachment #3.1.1: Type: text/plain, Size: 26 bytes --]
just looking things over.
[-- Attachment #3.1.2: Type: text/html, Size: 666 bytes --]
[-- Attachment #4: Type: message/rfc822, Size: 1271 bytes --]
[-- Attachment #4.1.1: Type: text/plain, Size: 26 bytes --]
just looking things over.
[-- Attachment #4.1.2: Type: text/html, Size: 557 bytes --]
next reply other threads:[~2000-01-21 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 19:52 Karl Kleinpaste [this message]
2000-01-22 2:58 ` David Maslen
2000-01-22 13:04 ` Steinar Bang
2000-01-22 15:43 ` Karl Kleinpaste
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=vxkbt6fqk2m.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/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).