From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Attributes on HTML tables?
Date: Sun, 07 Apr 2013 22:48:48 +0200
Message-ID: <87mwtavzgv.fsf@gmail.com>
References: <86bo9rnj6q.fsf@iro.umontreal.ca> <87ppy66eke.fsf@bzg.ath.cx>
	<m2ppy6xv0j.fsf@christianmoe.com> <878v4uxjp6.fsf@gmail.com>
	<m2obdqxegv.fsf@christianmoe.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:54429)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1UOwWE-0005CG-4M
	for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 16:48:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1UOwWD-0008KZ-Ay
	for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 16:48:54 -0400
In-Reply-To: <m2obdqxegv.fsf@christianmoe.com> (Christian Moe's message of
	"Sun, 07 Apr 2013 22:39:28 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Christian Moe <mail@christianmoe.com>
Cc: Bastien <bzg@gnu.org>, =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>, emacs-orgmode@gnu.org

Christian Moe <mail@christianmoe.com> writes:

> But what is it that nees to be supported, and why couldn't you just pass
> through *whatever* :attribute value pair the user puts in attr_html?

Does every possible attribute follow attribute="value" pattern? Aren't
there single keywords? If they are that regular, we can indeed walk the
plist like a list and change

  (:key1 val1 :key2 val2 ...)

into

  key1="val1" key2="val2"

If there are irregular keywords, the export back-end needs to know about
them.

Also, if attributes are provided, I assume defaults should be ignored
altogether. Or do we need to create the union between default values and
provided attributes?


Regards,

-- 
Nicolas Goaziou