From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: New HTML rendering: shr-insert-document
Date: Mon, 04 Oct 2010 18:19:25 +0200 [thread overview]
Message-ID: <m362xidj76.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3aamudjhd.fsf_-_@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> And it works with my only test case, so I guess it's perfect now.
I had a peek at a few Gwene groups, and it seems to mostly do the right
thing.
It doesn't implement rowspan and colspan yet, which I guess it should.
And images in tables don't work at all, which should definitely work.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-04 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 15:40 New HTML rendering: srh-insert-document Lars Magne Ingebrigtsen
2010-10-02 16:56 ` Lars Magne Ingebrigtsen
2010-10-02 18:06 ` Tassilo Horn
2010-10-02 22:06 ` Lars Magne Ingebrigtsen
2010-10-04 16:13 ` New HTML rendering: shr-insert-document Lars Magne Ingebrigtsen
2010-10-04 16:19 ` Lars Magne Ingebrigtsen [this message]
2010-10-03 7:01 ` New HTML rendering: srh-insert-document Steinar Bang
2010-10-03 12:47 ` Lars Magne Ingebrigtsen
2010-10-03 20:21 ` Steinar Bang
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=m362xidj76.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).