emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Enhancing table cell alignments and commenting columns (was Re: Orthogonality of blocks)
Date: Thu, 29 Dec 2011 11:36:27 +0530	[thread overview]
Message-ID: <81boqrud24.fsf@gmail.com> (raw)
In-Reply-To: <81fwg4sz9z.fsf_-_@gmail.com> (Jambunathan K.'s message of "Thu, 29 Dec 2011 11:19:28 +0530")


> I think the colcookie lines could be enhnaced to also support "t" and
> "/" characters. IMNSHO, using #+ATTR_ODT: lines for commenting out
> columns will not only be cumbersome but also error-prone.

A random thought:

I think there will be more flexibility if the colcookies characters -
"l" and "r" - were actually style strings (of length > 1). The backend
can use their own discretion on how they "apply" these styles.

There was some interest to mark certain columns specially - for example,
mark automatically computed derived columns specially (both in Org and
may be in the different backends). The colcookie could line could be put
to some use here. (Question: Is there a way to fontify a rectangle in
Emacs?)

On a related note:

From ODT perspective and taking a cue from the way LibreOffice does
autoformatting of tables, I was thinking of introducing "template
tables" whose only job is to specify the styles to be associated with
each of the different categories of table cells.

OpenDocument talks of following types of columns and LibreOffice's
autoformatting is much richer and recognizes, I believe, as much as 16
categories of table cells.

,---- C-h v org-export-odt-table-styles
| TABLE-CELL-TYPE       := "FirstRow"   | "LastColumn" |
|                          "FirstRow"   | "LastRow"    |
|                          "EvenRow"    | "OddRow"     |
|                          "EvenColumn" | "OddColumn"  | ""
| 
`----

#+ATTR_ODT: template-table
| red | green | yellow |
|-----+-------+--------|
|     |       |        |

ps: I don't have time to implement the above features. I am just
capturing my thoughts so that it is archived.

-- 

  reply	other threads:[~2011-12-29  6:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 19:46 Orthogonality of blocks Charles Turner
2011-12-27 20:37 ` Eric Schulte
2011-12-27 21:12   ` Christian Moe
2011-12-27 21:10     ` Eric Schulte
2011-12-27 23:19       ` Christian Moe
2011-12-27 23:30     ` Nick Dokos
2011-12-28  0:14       ` Torsten Wagner
2011-12-28  4:48       ` Jambunathan K
2011-12-28  5:30         ` Jambunathan K
2011-12-28  7:10       ` Sebastien Vauban
2011-12-28 14:51     ` Charles Turner
2011-12-29  5:18       ` Jambunathan K
2011-12-29  5:49         ` Enhancing table cell alignments and commenting columns (was Re: Orthogonality of blocks) Jambunathan K
2011-12-29  6:06           ` Jambunathan K [this message]
2011-12-29 16:22           ` Jambunathan K
2011-12-29  6:14       ` Orthogonality of blocks Jambunathan K
2011-12-30 14:17 ` Eric S Fraga

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=81boqrud24.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).