all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>,
	24831@debbugs.gnu.org, yamaoka@jpl.org
Subject: bug#24831: shr mangling messages
Date: Fri, 04 Nov 2016 14:18:03 -0400	[thread overview]
Message-ID: <87twbn3y90.fsf@lifelogs.com> (raw)
In-Reply-To: <E1c1cg8-0003gg-PY@fencepost.gnu.org> (Richard Stallman's message of "Tue, 01 Nov 2016 13:16:52 -0400")

On Tue, 01 Nov 2016 13:16:52 -0400 Richard Stallman <rms@gnu.org> wrote: 

>> Another idea would be first run it through a validator.
>> If valid, proceed as before.
>> If invalid, just spew out all the text nodes of the whole document,
>> separated by spaces.

RS> Do we have a validator in Emacs Lisp?  Or would we run one as a child?
RS> What program is available?

IMHO validation is not a workable solution, both because of complexity
and because real-world HTML authors are incredibly skilled at writing
broken HTML that somehow renders in the browsers they support.

Ted





  reply	other threads:[~2016-11-04 18:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87shrgvt8y.fsf@jidanni.org>
2016-10-31  2:45 ` bug#24831: shr mangling messages 積丹尼 Dan Jacobson
2016-11-01  1:39   ` Katsumi Yamaoka
2016-11-01  9:59     ` Katsumi Yamaoka
2016-11-01 10:06       ` Lars Ingebrigtsen
2016-11-01 10:12         ` Lars Ingebrigtsen
2016-11-01 18:43         ` Lars Ingebrigtsen
2016-11-02  9:49           ` Katsumi Yamaoka
2016-11-04  7:19             ` Katsumi Yamaoka
2016-11-04  8:51               ` Lars Ingebrigtsen
2016-11-04 10:28                 ` Katsumi Yamaoka
2016-11-04 11:17                   ` Lars Ingebrigtsen
2016-11-06 23:32                     ` Katsumi Yamaoka
2016-11-01 11:22   ` 積丹尼 Dan Jacobson
2016-11-01 17:16     ` Richard Stallman
2016-11-04 18:18       ` Ted Zlatanov [this message]
2016-11-01 11:24   ` 積丹尼 Dan Jacobson

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=87twbn3y90.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=24831@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.org \
    --cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.