emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Robert Klein <roklein@roklein.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: another blog exporter
Date: Mon, 10 Feb 2014 09:48:48 +0100	[thread overview]
Message-ID: <874n47bbf3.fsf@bzg.ath.cx> (raw)
In-Reply-To: <52F78FDC.8090402@roklein.de> (Robert Klein's message of "Sun, 09	Feb 2014 15:25:32 +0100")

Hi Robert,

Robert Klein <roklein@roklein.de> writes:

> I posted the latest three posts on http://www.xyzzy.de using
> ox-blog.

Neat, thanks!

> I can use #+ATTR_HTML, but I wasn't sure about using new attributes,
> e.g. :highlight and :lineno for source blocks.  I didn't want to pollute
> ATTR_HTML with things that are of no use for the HTML exporter.

You're right.

Somehow this calls for a way to let a backend use several affiliated
keywords.  For example you would have:

#+ATTR_HTML: :width 400px
#+ATTR_BLOG: :lineno t

and the exporter would take both into account, letting you to simply
export to HTML without the need to add redundant information.

Nicolas, did this cross your mind?  Or maybe this is already feasible?

> If you don't see a problem in #+ATTR_HTML, I'll happily change this.

No, that will pollute the HTML export (I don't expect anything weird
in the HTML output with unknown attributes, but the document will not
validate correctly, and this is confusing anyway.)

Thanks!

-- 
 Bastien

  reply	other threads:[~2014-02-10  8:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 17:10 another blog exporter Robert Klein
2014-02-07 17:35 ` Rasmus
2014-02-07 19:17   ` Robert Klein
2014-02-08  0:27 ` Ken Mankoff
2014-02-08  8:40   ` Robert Klein
2014-02-08 20:41 ` Robert Klein
2014-02-09  7:55   ` Bastien
2014-02-09 14:25     ` Robert Klein
2014-02-10  8:48       ` Bastien [this message]
2014-02-10 11:30         ` Nicolas Goaziou
2014-03-04  9:51           ` Robert Klein

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=874n47bbf3.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=roklein@roklein.de \
    /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).