emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Frankel <rick@rickster.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] export to various flavors of (X)HTML
Date: Tue, 30 Apr 2013 10:38:44 -0400	[thread overview]
Message-ID: <ed376f0a56f6f5b8f522a187f00f0e0b@mail.rickster.com> (raw)
In-Reply-To: <87bo8xeuxd.fsf@ericabrahamsen.net>

On 29.04.2013 02:02, Eric Abrahamsen wrote:
> Rick Frankel <rick@rickster.com> writes:
>
>> On Fri, Apr 26, 2013 at 10:14:17AM -0700, Eric Abrahamsen wrote:
>>> Rick Frankel <rick@rickster.com> writes:

>>> > See the discussions of polyglot markup @
>>> > http://en.wikipedia.org/wiki/Polyglot_markup
>>> > and
>>> > 
>>> http://www.w3.org/TR/2011/WD-html-polyglot-20110405/#dfn-polyglot-markup
>>> > for the rationale.
>>>
>>> Ah, those were interesting links, I hadn't considered those issues.
>>> Luckily, your second option was a three-line change to the existing
>>> patch: using "xhtml5" now produces the same output as "html5", 
>>> except
>>> that self-closing tags are self-closed, and there's a xmlns 
>>> declaration
>>> in the <html> element. Best of all worlds, I hope.
>>

Overall, works well. A couple of things related to
`org-html-xml-declaration':

    - It should not be added by default for xhtml5
      (from 
http://www.w3.org/TR/2011/WD-html-polyglot-20110405/#PI-and-xml):

	 #+BEGIN_QUOTE
       2. Processing Instructions and the XML Declaration

        Processing Instructions and the XML Declaration are both
        forbidden in polyglot markup.
	 #+END_QUOTE

    - If `org-html-xml-declaration' is set to nil or the empty string,
      a blank first line is placed in the document prior to the DOCTYPE
      declaration. If the above fix is added (so it is not generated
      for xhtml5) that should solve the immediate problem, but i think
      that the formatting code in org-html-html-template should check
      that the inner format (line #1697). A patch is attached to fix
      both issues.

> 1. There's a new export option, 
> org-html-html5-fancy/HTML_HTML5_FANCY,
> which defaults to 'nil, making most of the following opt-in only.

Very nice.

> 5. It's generally accepted that one should use some variety of the
> html5shiv[1] to make IE <9 render new HTML5 elements correctly. I've
> dropped a note to this effect in the docstring of
> `org-html-html5-fancy', but I suppose it's possible we could take a 
> more
> interventionist stance, perhaps including hosting a version of the 
> shiv
> on orgmode.org, and linking to it automatically. I guess I'm in favor 
> of
> leaving it to the user, though.

I agree that we should comment and leave it to the user. I believe
the owner of html5shiv is against CDN hosting the javascript and feels
that it should always be downloaded and included locally.

> Tangential coding question: I've noticed that setting 
> HTML_HTML5_FANCY
> to nil at the top of the export file results in `(plist-get info
> :html-html5-fancy)' returning the string "nil", ie true. Not right,
> obviously, and it makes it impossible to set it to 'nil per-file if 
> the
> global value is 't. Am I handling this wrong?

I believe Nicolas answered the is a previous email, but the solution
is use "'()" and not nil.

rick

  parent reply	other threads:[~2013-04-30 14:38 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 [this message]
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
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=ed376f0a56f6f5b8f522a187f00f0e0b@mail.rickster.com \
    --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).