From: Nick Dokos <nicholas.dokos@hp.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: multilingual presentation with org
Date: Wed, 15 Feb 2012 17:01:39 -0500 [thread overview]
Message-ID: <9192.1329343299@alphaville> (raw)
In-Reply-To: Message from Jambunathan K <kjambunathan@gmail.com> of "Thu, 16 Feb 2012 03:18:43 +0530." <81pqdfepj8.fsf@gmail.com>
Jambunathan K <kjambunathan@gmail.com> wrote:
>
> Nick
>
> What Brian is saying is this and I am interpreting.
>
> There is a line by line correspondence between the two files. So,
>
> 1. Put the English file under version control and check it in.
>
> 2. Overwrite the English file with the Sanskrit file (remember to
> preserve line by line correspondence) and check the sanskrit file in.
>
> 3. Now do a C-x v u to launch ediff on the two versions of the file. Two
> windows will pop up and IIRC, you can arrange for the windows to be
> either arranged side by side or one on top of another.
>
> 4. Press q on Ediff control panel so that diff overlays are removed
> while leaving the windows intact.
>
I don't understand what the first four steps do for you.
> 5. Now do M-x scroll-all-mode so that the two windows scroll
> together. Cursor position in the two windows can be used to guiding
> the eyeballs of the audience.
>
All you need for this is two side-by-side windows with the two files and
scroll-all-mode[fn:1]. Ediff (and source control) is irrelevant -
correct?
If only hl-line-highlight played well with scroll-all-mode...
> An advanced option will be to siphon off each stanza in the recital in
> to separate files of their own and put the sanskrit and english files in
> separate directories (but with the same name) as below.
>
> english/stanza1
> english/stanza2
>
> sanskrit/stanza1
> sanskrit/stanza2
>
> Then one can do M-x ediff-directories to have all the stanzas show up
> and then launch ediff on each of the stanzas.
>
I might try this to see how it works but it'd take more time than I can
afford right now.
Thanks,
Nick
Footnotes:
[fn:1] I was looking for that and didn't find it - thanks for pointing
it out. I thought at first that follow-mode was what was needed,
but that wasn't it.
next prev parent reply other threads:[~2012-02-15 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rustompmody@gmail.com>
2012-02-15 8:03 ` multilingual presentation with org Rustom Mody
2012-02-15 13:08 ` Nick Dokos
2012-02-15 14:24 ` suvayu ali
2012-02-15 18:32 ` Rustom Mody
2012-02-15 18:43 ` Rustom Mody
2012-02-15 19:02 ` brian powell
2012-02-15 19:49 ` Nick Dokos
2012-02-15 20:01 ` brian powell
2012-02-15 20:26 ` brian powell
2012-02-15 21:04 ` Nick Dokos
2012-02-15 21:48 ` Jambunathan K
2012-02-15 22:01 ` Nick Dokos [this message]
2012-02-15 22:31 ` Jambunathan K
2012-02-15 17:23 ` brian powell
2012-02-15 17:51 ` Nick Dokos
2012-02-16 22:59 ` Daniel Clemente
2012-02-17 3:44 ` Rustom Mody
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=9192.1329343299@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).