From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Built-in HTML parsing and rendering library
Date: Mon, 06 Sep 2010 14:28:10 +0200 [thread overview]
Message-ID: <m3r5h7ys2t.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87pqwrjc7b.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> It's what Gnome uses so it's pretty good. Because of the Gnome link it
> would probably be the easiest one to bring into the Emacs core.
Yes. I had a quick peek at the interface, and it seemed to return a
nice DOM that could probably be exported to Emacs pretty easily as an
elisp list tree like (:html (:head ...) (:body ...)) etc.
And since libxml2 is already installed on 99% of Linux machines, linking
Emacs to it should be no big deal.
So the question is: If we have the parse tree in Emacs Lisp, would we be
able to render it quickly enough for it to make sense to use? I haven't
really thought about it much, but it strikes me that rendering heavily
nested tables and the like might be a time-consuming task in a language
that's as slow as Emacs Lisp. But it might be fine; I'm not sure at all.
Is there a component of libxml2 (or some other handy library) that does
HTML rendering, too? :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-06 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 22:58 Lars Magne Ingebrigtsen
2010-09-06 4:27 ` Daniel Pittman
2010-09-06 7:53 ` Steinar Bang
2010-09-06 11:33 ` Lars Magne Ingebrigtsen
2010-09-06 12:20 ` Ted Zlatanov
2010-09-06 12:28 ` Lars Magne Ingebrigtsen [this message]
2010-09-06 12:40 ` Julien Danjou
2010-09-06 13:09 ` Ted Zlatanov
2010-09-06 18:26 ` Sivaram Neelakantan
2010-09-06 19:58 ` Lars Magne Ingebrigtsen
2010-09-06 7:32 ` Steinar Bang
2010-09-06 8:29 ` David Engster
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=m3r5h7ys2t.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).