From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-html: Under html5-fancy, use <nav> for the ToC
Date: Wed, 10 Jul 2013 11:26:41 +0800 [thread overview]
Message-ID: <87hag3nlhq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87ip0jzc9w.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Kodi Arfer <kodi@arfer.net> writes:
>
>> While I admit I'm not totally sure, in general, when a given fancy
>> HTML5 element is appropriate, this case (an intra-page table of
>> contents) seems right in line with the second code example here:
>>
>> http://www.w3.org/html/wg/drafts/html/master/sections.html#the-nav-element
>>
>> From a1aa357f75cd37ef676f5ac4dbbe66ad66d76aa8 Mon Sep 17 00:00:00 2001
>> From: Kodi Arfer <git@arfer.net>
>> Date: Sat, 1 Jun 2013 17:41:38 -0400
>> Subject: [PATCH] ox-html: Under html5-fancy, use <nav> for the ToC
>>
>> * lisp/ox-html.el (org-html-toc): Use <nav> instead of <div>
>> for the root element when appropriate.
>
> Applied. Thank you.
Back when we were putting together the html5 stuff, I think we agreed to
table the issue of deeper html5 tag use until we'd had a bit of think
about the current default behavior of org's html output. Not that I
don't think this patch should be accepted -- it's definitely the least
controversial of the html5 tags.
At the time I think I was thinking that the html org produces by default
seemed very much predicated on the creation of unix-y style
documentation pages: the prev/next/up links, the preamble and postamble,
etc. That seemed strange to me, as my assumption was that most people
are not going to be producing that kind of html page. In retrospect that
doesn't seem like such a big deal -- it's so easy to turn off, and
there's always the body-only switch.
So maybe it would just be enough to patch html5 further so that the
preamble and postamble use <header> and <footer> tags? The behavior of
`org-html-divs' would have to be reconsidered, but it shouldn't have to
be anything too momentous...
Eric
prev parent reply other threads:[~2013-07-10 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 21:50 [PATCH] ox-html: Under html5-fancy, use <nav> for the ToC Kodi Arfer
2013-07-09 20:52 ` Nicolas Goaziou
2013-07-10 3:26 ` Eric Abrahamsen [this message]
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=87hag3nlhq.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.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 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).