From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Attributes on HTML tables? Date: Fri, 12 Apr 2013 10:06:21 +0800 Message-ID: <87ehegtsde.fsf@ericabrahamsen.net> References: <86bo9rnj6q.fsf@iro.umontreal.ca> <87ppy66eke.fsf@bzg.ath.cx> <878v4uxjp6.fsf@gmail.com> <87mwtavzgv.fsf@gmail.com> <86fvyy1dsp.fsf@iro.umontreal.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQTHu-0002K4-Fq for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 22:00:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQTHt-0000d0-BZ for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 22:00:26 -0400 Received: from plane.gmane.org ([80.91.229.3]:40326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQTHt-0000cu-5E for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 22:00:25 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UQTHs-0000Ho-09 for emacs-orgmode@gnu.org; Fri, 12 Apr 2013 04:00:24 +0200 Received: from 114.250.106.12 ([114.250.106.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Apr 2013 04:00:23 +0200 Received: from eric by 114.250.106.12 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Apr 2013 04:00:23 +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: emacs-orgmode@gnu.org François Pinard writes: > Christian Moe writes: > >> XHTML is also fussy about quoting attribute values, and about escaping >> special characters as HTML entities, including the ampersand (&), and >> including inside attribute values. I'm guessing the exporter already >> does the right thing here. > > Org can of course take care of XTHML fussiness, there is likely no > problem there. > > 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? E