From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Attributes on HTML tables? Date: Thu, 11 Apr 2013 19:29:37 +0200 Message-ID: <87vc7tq8la.fsf@gmail.com> References: <86bo9rnj6q.fsf@iro.umontreal.ca> <87ppy66eke.fsf@bzg.ath.cx> <878v4uxjp6.fsf@gmail.com> <87mwtavzgv.fsf@gmail.com> <87haje41ns.fsf@gmail.com> <87hajds5f5.fsf@gmail.com> <87bo9lrsi3.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQLJh-00071i-F0 for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 13:29:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQLJg-0006EX-1q for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 13:29:45 -0400 In-Reply-To: <87bo9lrsi3.fsf@bzg.ath.cx> (Bastien's message of "Thu, 11 Apr 2013 17:34:12 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Bastien Cc: emacs-orgmode@gnu.org, Christian Moe Hello, Bastien writes: > Nicolas Goaziou writes: > >>> than it is to automatically replace verbatim attribute code with plists, >>> especially if there are all sorts of html irregularities in there. >> >> I prefer not to mix the two methods as it would be fragile (e.g. what >> happens if an attribute is defined both outside and inside the :options >> keyword?). > > Sorry, catching up in this thread -- my understanding was that > :options was *always* available as a fallback, even with other > attributes set before it. Am I wrong? :options is more or less required in LaTeX export. Other keywords may go in different locations (optional arguments, mandatory arguments) so the back-end has to understand the keywords provided. It also means there will always be keywords it won't understand (i.e. which are not hardcoded). The :options bucket is a good place for them. On the other hand, I think we don't need it in HTML export. All attributes go in the same place, so the backend just transforms the plist into a string. Since it doesn't need to know about what it transforms, the bucket becomes useless, maybe confusing. Regards, -- Nicolas Goaziou