From: Rick Frankel <rick@rickster.com>
To: emacs-orgmode@gnu.org
Subject: Re: Attributes on HTML tables?
Date: Sat, 13 Apr 2013 13:10:13 -0400 [thread overview]
Message-ID: <20130413171013.GA66674@BigDog.local> (raw)
In-Reply-To: <87ehegtsde.fsf@ericabrahamsen.net>
On Fri, Apr 12, 2013 at 10:06:21AM +0800, Eric Abrahamsen wrote:
> François Pinard <pinard@iro.umontreal.ca> writes:
>
> > Christian Moe <mail@christianmoe.com> writes:
> >
> > While on this subject! :-)
> >
> > Could Org allow the output of HTML5 rather than XHTML, under the control
> > of some option? I've read that some frameworks really expect HTML5 to
> > work properly, such an option might ease inter-operation between
> > exported Org and such frameworks.
>
> I'm curious about this possibility as well -- how much work would it be?
Sorry, late to the thread, i've been laid up. Anyway, the xhtml output
from ox-html _should_ be
mostly valid html5 (valid xhtml 1.0 in general should be valid html5).
However, you will need to change the html-table-tag to not use
attributes, and remove the xml declaration
(which is a warning and not an error in html5)
Here's a sample org file (which changes the divs to be more "html5ish"
as well, not necessary)
which validates as HTML5: (btw, i've remove the scripts and
default-styles just to make the
html output smaller, the file will validate even with them in the
output).
rick
----- %< ---------
#+TITLE: HTML 5 Test
#+DATE: {{{modification-time(%Y-%m-%d)}}}
#+HTML_DOCTYPE: <!DOCTYPE html>
#+BIND: org-html-xml-declaration ""
#+BIND: org-html-head-include-default-style nil
#+BIND: org-html-table-tag "<table>"
#+BIND: org-html-scripts ""
#+BIND: org-html-divs ((preamble "header" "preamble") (content
"section" "content") (postamble "footer" "postamble"))
* Org HTML5 Test
ok?
* How about a table
| col1 | col2 |
|------+------|
| a | 1 |
| b | 2 |
* And a list
- a
- b
- c
* A definiton list
- a :: foo
- b :: bar
next prev parent reply other threads:[~2013-04-13 17:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 2:55 Attributes on HTML tables? François Pinard
2013-04-07 6:27 ` Bastien
2013-04-07 14:42 ` Christian Moe
2013-04-07 18:46 ` Nicolas Goaziou
2013-04-07 20:39 ` Christian Moe
2013-04-07 20:48 ` Nicolas Goaziou
2013-04-08 21:09 ` Christian Moe
2013-04-10 17:44 ` François Pinard
2013-04-12 2:06 ` Eric Abrahamsen
2013-04-12 5:42 ` Bastien
2013-04-12 6:01 ` Eric Abrahamsen
2013-04-12 8:46 ` Bastien
2013-04-12 14:36 ` François Pinard
2013-04-13 3:38 ` Eric Abrahamsen
2013-04-13 5:31 ` Eric Abrahamsen
2013-04-13 20:42 ` Rick Frankel
2013-04-14 10:13 ` Eric Abrahamsen
2013-04-14 18:01 ` Rick Frankel
2013-04-15 18:03 ` Rick Frankel
2013-04-13 17:10 ` Rick Frankel [this message]
2013-04-14 8:41 ` Bastien
2013-04-10 19:37 ` Nicolas Goaziou
2013-04-11 8:28 ` Christian Moe
2013-04-11 10:55 ` Nicolas Goaziou
2013-04-11 12:14 ` Christian Moe
2013-04-11 15:34 ` Bastien
2013-04-11 17:29 ` Nicolas Goaziou
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=20130413171013.GA66674@BigDog.local \
--to=rick@rickster.com \
--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).