ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reverse page order and reverse page numbering in one part of a book
Date: Wed, 22 Jul 2015 14:45:51 +0200	[thread overview]
Message-ID: <20150722144551.523f1d5d@iram-ha-003105.extra.cea.fr> (raw)
In-Reply-To: <op.x16bi2aiejo439@ishamid-pc>

On Wed, 22 Jul 2015 05:58:04 -0600
Idris Samawi Hamid ادريس سماوي حامد <Idris.Hamid@colostate.edu> wrote:

> That said: You could typeset both books as distinct products or
> components within a single project file - see page 20 of cont-eni.pdf
> (I once did two books this way). Then you can do cross-references
> between both books. IIRC you can then take the TOC in one product or
> component and place it in the other. So in the English book you can
> place the Arabic TOC and vice versa. 

This raises a related, more general question on how to handle
multilingual documents. The English first half, Arabic second half is
just one example. There are also bilingual texts with left and right
columns or facing even and odd pages. We also all know of manuals
containing a succession of different languages, sometimes sharing a
unique set of figures, sometimes repeating the figures (with differing
captions and labels).

It is not obvious how to maintain parallel texts containing identical
structure in multiple languages (in multiple files?). 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. Presently, I maintain
multiple files that I compare and edit side-by-side using a "diff" tool
such as meld (gtk) or kdiff3 (kde). I am sure that other users have
good or better solutions that they might want to indicate.

The question is how to create a structure that is both readable and
manageable?

Alan
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2015-07-22 12:45 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 [this message]
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

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=20150722144551.523f1d5d@iram-ha-003105.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=Idris.Hamid@colostate.edu \
    --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).