From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: reverse page order and reverse page numbering in one part of a book
Date: Fri, 24 Jul 2015 12:18:25 +0200 [thread overview]
Message-ID: <55B210F1.9050704@wxs.nl> (raw)
In-Reply-To: <20150722154716.354d1ab2@iram-ha-003105.extra.cea.fr>
On 7/22/2015 3:47 PM, Alan BRASLAU wrote:
> On Wed, 22 Jul 2015 14:54:17 +0200
> "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:
>
>> On 07/22/2015 02:45 PM, Alan BRASLAU wrote:
>>> The
>>> project/product/component mechanism can help somewhat. I also know
>>> that Thomas had written a streams module to handle the
>>> synchronization of texts. However, I am not so sure how to go about
>>> this in a real, full-fledged case with a complicated text.
>>
>> Correction: "Thomas had a streams module written (by Hans)." I used
>> it for a bilingual document for my course material, but in the end,
>> it turned out that using it for a "real" book would have been
>> extremely complex. In my field, there are numerous books with a
>> bilingual layout, but I guess they are all still handcrafted, i.e.
>> manual page breaks etc. I just shudder to think what would happen if
>> someone has to add three words on page 3 of such a book - they would
>> have to redo every single darn pagebreak?
>
> There are several different issues. Synchronization can be
> line-by-line, paragraph-by-paragraph, sectionblock-by-sectionblock...
> or, as is the case with the posting of this thread, part-by-part (i.e.
> halves). The different "products" in multiple languages might only be
> "synchronized" by structure, not by rendering at all.
>
> Maybe Mari (and others) have regular experience in managing
> multilingual documents and maintaining them under modification. And I
> bring up this issue under the present thread as managing left-to-right
> mixed with right-to-left text is a further complication that Idris (and
> others) address regularly.
To some extend we can typeset in parallel but only with properly
structured input (and xml is then probably the best candidate). Anyway I
think that the editing is the bottleneck: how does one most conveniently
edit in parallel? We might need to think about that first: the
typeseting component should adapt, convenient editing is core issue.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-07-24 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 9:49 talazem
2015-07-22 11:58 ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-22 12:45 ` Alan BRASLAU
2015-07-22 12:54 ` Thomas A. Schmitz
2015-07-22 13:47 ` Alan BRASLAU
2015-07-22 14:28 ` Thomas A. Schmitz
2015-07-24 10:15 ` Hans Hagen
2015-07-24 10:18 ` Hans Hagen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B210F1.9050704@wxs.nl \
--to=pragma@wxs.nl \
--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).