From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: how to produce text with facing translation?
Date: Fri, 3 Mar 2006 21:25:27 +0100 [thread overview]
Message-ID: <47F5FC64-A9B9-4965-901E-AA5AFCFB41FA@fiee.net> (raw)
In-Reply-To: <300C1ECC-F9C0-4CC8-843A-2D10FF571E49@uni-bonn.de>
Am 2006-03-03 um 12:45 schrieb Thomas A. Schmitz:
>> i played with dual streams a bit yesterday but have no time to
>> explore it now;
>> it's a tricky business and much depends on what the input / output
>> is to be
>>
>> it is doable to develop a framework for this, but only when you and
>> others first
>> come up with some decent spec (what kind of input, what kind of
>> sync, what kind
>> of content, how to handle floats, etc)
>>
>> Hans
>
> Several other members said they were interested too. So could you
> give us a hint how this can be achieved? Could we start from
> something very simple and then move on to more advanced features? For
> the time being, I don't need any floats etc., just basic texts on
> both sides with footnotes and the possibility to give breakpoints on
> the recto side.
Friendly as ever, Hans suggests that you write a sample/spec how
you'd like to use this feature, so that he can think about some
implementation himself.
E.g., would such help?:
\setupsynced[setup name][mode=pages, after=pagebreak, n=2]
% n = (number of synced columns, think of more language versions to
compare...; default=2)
% mode = pages, columns (default=columns; pages only with n=2)
% after = pagebreak, space, continue...? (what should we do with
remaining space in column?)
% footnotes = local, ...? (synced text needs its own set of footnote
counters...)
% frame, background etc.?
\startsynced[mysetup]%
{ greek text }%
{ german text }
\stopsynced
This would be analogous to combinations, but could handle only single
paragraphs, I guess.
I don't think I need this feature, so it's your turn to propose a
syntax!
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)
next prev parent reply other threads:[~2006-03-03 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 10:37 Thomas A. Schmitz
2006-03-02 16:41 ` David Rogers
2006-03-03 11:45 ` Thomas A. Schmitz
2006-03-03 19:03 ` David Rogers
2006-03-03 20:25 ` Henning Hraban Ramm [this message]
2006-03-05 10:10 ` Thomas A. Schmitz
2006-03-05 12:11 ` Hans Hagen
2006-03-05 14:21 ` Thomas A. Schmitz
2006-03-06 9:13 ` Hans Hagen
2006-03-16 16:55 ` Thomas A. Schmitz
2006-03-16 20:48 ` Hans Hagen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F5FC64-A9B9-4965-901E-AA5AFCFB41FA@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).