emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Wittern <cwittern@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Side-by-side support
Date: Tue, 24 Jan 2012 08:51:59 +0900	[thread overview]
Message-ID: <4F1DF29F.6000403@gmail.com> (raw)
In-Reply-To: <81bopucr81.fsf@gmail.com>

Hi Jambunathan,

On 2012-01-24 01:34, Jambunathan K wrote:
>
>> In my case, I have simply separated the columns by a<tab>  character
>> and set the tab-width to a sensible value for nice on-screen display.
>> These are 'text' and 'translation of that text' side-by-side,
> When you are saying on-screen display, I presume you are referring to
> the Emacs screen? I have a strong feeling that you are using two column
> editing. Otherwise, it would be extremely difficult to keep one's
> sanity.
Actually I started out using 2C editing for this, but it came constantly in 
my way, so currently what I am doing is:
(1) use a tab character to separate the two columns and
(2) set the tab-width to 30 (in most cases), so that most of the columns are 
nicely separated.

This works very well for editing in Emacs.  However, at the moment I do not 
have an easy way to export this to ODT as it s.  Now I have given further 
thought to this, maybe the following will work:
(1) consecutive lines with 1 or more <tab> characters and the *same* number 
of such <tab>s will be considered as a table and the exporter will work with 
this as if it were a org-table. (Note that I usually only have two columns 
and as you said, with more columns one is probably better off using proper 
tables)
(2) This option is switched on or off through a variable or a OPTION line in 
the header of the file.
(3) as I mentioned earlier, it would be good to be also able to globally set 
the proportions (maybe this can already be done with column properties?)

All the best,

Christian

-- 
Christian Wittern, Kyoto

      reply	other threads:[~2012-01-23 23:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  8:52 [ODT] image scaling overridden by long caption Andreas Leha
2012-01-19 20:03 ` Jambunathan K
2012-01-21 10:18   ` Andreas Leha
2012-01-23 19:53     ` Jambunathan K
2012-01-23 21:20       ` Nicolas Goaziou
2012-02-01  9:16         ` comments and attributes Jambunathan K
2012-02-01 13:04           ` Nicolas Goaziou
2012-02-15  0:03       ` [ODT] image scaling overridden by long caption Andreas Leha
2012-01-27 14:40     ` Jambunathan K
2012-01-27 22:41       ` Andreas Leha
2012-01-31  4:59         ` Jambunathan K
2012-02-07 10:04           ` Andreas Leha
2012-01-23  1:53   ` Side-by-side support (was:Re: [ODT] image scaling overridden by long caption) Christian Wittern
2012-01-23 16:34     ` Side-by-side support Jambunathan K
2012-01-23 23:51       ` Christian Wittern [this message]

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=4F1DF29F.6000403@gmail.com \
    --to=cwittern@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=n.goaziou@gmail.com \
    /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).