From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] export to various flavors of (X)HTML
Date: Mon, 6 May 2013 07:49:16 +0200 [thread overview]
Message-ID: <F979FC4C-8900-4E0C-90D6-34071E47406A@gmail.com> (raw)
In-Reply-To: <87k3nhqeed.fsf@ericabrahamsen.net>
Hi Eric, Rick, Francois and others,
Nicolas commented to me about this patch that he was wondering if it
would not be better to have a separate backend for html5, i.e.
ox-html5.el that could be derived from ox-html.el and make it easier
in the future to build it out to take full advantage of html5 features.
I think he has a point, and I would like to hear your comments.
Thanks
- Carsten
On 2.5.2013, at 23:07, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Rick Frankel <rick@rickster.com> writes:
>
>> On Tue, Apr 30, 2013 at 08:26:52PM -0700, Eric Abrahamsen wrote:
>>> Rick Frankel <rick@rickster.com> writes:
>>>
>>>> Whoops. Wrong key. Patch actually attached to this email...
>>>> rick
>>>
>>> Great, I'll consolidate all these -- would it be better to mush them
>>> into one big patch, or to keep them separate (I suppose for ease of
>>> rollback, if something goes wrong)?
>>
>> Probably squashing them into one patch would be the best. But Carsten
>> or Bastien might disagree :).
>>
>> rick
>
> Okay, there it is: one big patch (including your xml declaration fix).
>
> I didn't add any more refined handling of the html5-fancy option. As a
> second-order option it didn't seem worthy of an #+OPTIONS entry, and I
> didn't bother checking for an empty string, either. It can always be
> #+BINDed if necessary, and if it ever annoys anyone I can fix it
> further.
>
> E
>
> <0001-ox-html.el-Export-to-different-X-HTML-flavors-includ.patch>
next prev parent reply other threads:[~2013-05-06 5:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 9:57 [PATCH] export to various flavors of (X)HTML Eric Abrahamsen
2013-04-19 15:37 ` Rick Frankel
2013-04-20 2:59 ` Eric Abrahamsen
2013-04-23 1:00 ` Rick Frankel
2013-04-23 4:30 ` Eric Abrahamsen
2013-04-23 4:57 ` Samuel Wales
2013-04-23 6:55 ` Carsten Dominik
2013-04-23 7:54 ` Eric Abrahamsen
2013-04-23 12:09 ` François Pinard
2013-04-24 1:17 ` Christian Wittern
2013-04-24 13:10 ` François Pinard
2013-04-25 21:20 ` Eric Abrahamsen
2013-04-26 13:49 ` Rick Frankel
2013-04-26 17:14 ` Eric Abrahamsen
2013-04-26 18:49 ` Rick Frankel
2013-04-29 6:02 ` Eric Abrahamsen
2013-04-29 7:45 ` Nicolas Goaziou
2013-04-30 14:38 ` Rick Frankel
2013-04-30 14:40 ` Rick Frankel
2013-05-01 3:26 ` Eric Abrahamsen
2013-05-01 11:55 ` Rick Frankel
2013-05-02 21:07 ` Eric Abrahamsen
2013-05-03 7:17 ` Carsten Dominik
2013-05-06 5:49 ` Carsten Dominik [this message]
2013-05-06 7:36 ` Eric Abrahamsen
2013-05-06 7:48 ` Carsten Dominik
2013-05-06 9:05 ` Eric Abrahamsen
2013-05-06 12:56 ` Rick Frankel
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F979FC4C-8900-4E0C-90D6-34071E47406A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).