From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: Changing way hlines in tables are exported? Date: Thu, 02 Jul 2009 12:52:01 +0200 Message-ID: <87ab3n9x2m.fsf@kassiopeya.MSHEIMNETZ> References: <200906301615.52930.rainer.hansen@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MMJpo-0008JQ-0a for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 06:48:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MMJpi-0008FQ-Ug for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 06:48:07 -0400 Received: from [199.232.76.173] (port=34318 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMJpi-0008F9-Gf for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 06:48:02 -0400 Received: from mail.gmx.net ([213.165.64.20]:36045) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MMJph-0003eE-NI for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 06:48:02 -0400 In-Reply-To: (Carsten Dominik's message of "Tue, 30 Jun 2009 19:46:09 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > On Jun 30, 2009, at 4:15 PM, Rainer Hansen wrote: > >> Hi, >> >> I wonder if there is an easy way to change the style of the "exported" hlines >> in tables. This should not only be possible per table but per single hline, >> e.g. the first hline should be thick and in blue, the next two one are >> ordinary ones and the third should be thick and red. This should be possible >> for HTML, LaTeX and other export formats. > > Not currently, I guess this would need a look by CSS exports. Org > uses the hlines to define different groups. > We could probably assign classes to them, but I don't have a recipe > on how to do this differently on a per-table base. Would get complex, > it would require new #+ inbuffer settings. Well, this is possible already: #+ATTR_HTML: class="tableTypeA" | Table Header | |--------------| | Simple rows | | ... | |--------------| | Table Foot | CSS: table.tableTypeA thead { /* styles for the thead ... */ } table.tableTypeA thead tr { /* styles for in thead ... */ } table.tableTypeA thead td { /* styles for in thead ... */ } table.tableTypeA tbody { /* styles for the thead ... */ } table.tableTypeA tfoot { /* styles for the thead ... */ }