From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Message gets multipart/related support...
Date: Fri, 07 Mar 2014 14:27:26 +0100 [thread overview]
Message-ID: <87y50m16m9.fsf@building.gnus.org> (raw)
In-Reply-To: <upzcd2hy40om.fsf@dod.no> (Steinar Bang's message of "Fri, 07 Mar 2014 14:07:21 +0100")
Steinar Bang <sb@dod.no> writes:
> AFAIK the org export uses the ordinary HTML export and then either
> pushes it as-is and let WordPress strip it down to the supported tag
> set, or strips the HTML down to what WordPress expects.
Right. The interface Org uses to push stuff to WordPress must be more
permissive (allows more tags and stuff) than the email interface.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-03-07 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 19:22 Lars Ingebrigtsen
2014-03-07 6:59 ` Steinar Bang
2014-03-07 12:28 ` Lars Ingebrigtsen
2014-03-07 12:33 ` Lars Ingebrigtsen
2014-03-07 12:56 ` Lars Ingebrigtsen
2014-03-07 13:07 ` Steinar Bang
2014-03-07 13:27 ` Lars Ingebrigtsen [this message]
2014-03-07 12:59 ` Steinar Bang
2014-04-19 22:00 ` Alexander Baier
2014-03-07 12:51 ` 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=87y50m16m9.fsf@building.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).