From: Jambunathan K <kjambunathan@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: multilingual presentation with org
Date: Thu, 16 Feb 2012 03:18:43 +0530 [thread overview]
Message-ID: <81pqdfepj8.fsf@gmail.com> (raw)
In-Reply-To: <8912.1329339888@alphaville> (Nick Dokos's message of "Wed, 15 Feb 2012 16:04:48 -0500")
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.
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.
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.
> brian powell <briangpowellms@gmail.com> wrote:
>
>
>> --It works if you put line numbers at the beginning of each
>> line--then it highlights the diff per line in both buffers/in both
>> files--you do "Mx ediff-buffers" on--I know it works if you do--I
>> tested it before I posted.
>
> I did and it did not. I did it with cat -n at first and then tried nl
> just to see if it had some magic (as one might have guessed, no magic):
> there is one diff region for the whole buffer, not one per line.
>
> Nick
>
> PS. I attach the two files in case you, or somebody else, want to try it
> although I'm not sure the attachments are going to make it through the
> list unscathed. I'm making them octet-streams to try to preserve the contents
> unscathed. Here are SHA1s for them if you want to check (foo.txt.n is
> the transliterated file, foo-hi.txt.n is the devanagari)
>
> 85fd89d20ba4d1443089726fdb7a8bee7c7698ec foo-hi.txt.n
> e35932a206d2c129b8da1f855694d23838ea1013 foo.txt.n
>
>
> 1 OM bhUrbhuvaH suvaH
> 2 tatsaviturvarenyam
> 3 bhargo devasya dhImahi
> 4 dhiyo yonaH prachodayAt
>
>
--
next prev parent reply other threads:[~2012-02-15 21:49 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 [this message]
2012-02-15 22:01 ` Nick Dokos
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=81pqdfepj8.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).