ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Rogers <davidandrewrogers@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Can this layout be done in Context
Date: Tue, 23 Jul 2013 12:47:06 -0700	[thread overview]
Message-ID: <87d2q9xdmt.fsf@gmail.com> (raw)
In-Reply-To: <20130723011131.GE40886@verizon.net> (Russell Urquhart's message of "Mon, 22 Jul 2013 20:11:32 -0500")

Russell Urquhart <russurquhart1@verizon.net> writes:

> On Sun, Jul 21, 2013 at 11:19:27PM -0700, David Rogers wrote:
>> To summarize: A page header with page number and guide word (the guide
>> word showing which chapter of which book of the Bible begins on this
>> page), two columns of regular text, "margin notes" *for both columns*
>> set in their own special single (very narrow) centre column, and
>> footnotes in one single large column, which is permitted to take a lot
>> of vertical space on the page when necessary, with all those areas of
>> the page separated from each other by thin ruled lines. Correct?
>
> I know that this example is probably a little extreme, but i love the
> layout of thise books, and while i may not want to be able to do
> something that has ALL of those layout attributes, i'd be curious as
> to what it would take on the Context side.


I don't think it's extreme - I just wanted to make sure we didn't miss
any of what it contains.

I think there would need to be a lot of typing inside of the Bible text
itself (for example, needing to manually tag each and every chapter of
each book of the Bible), to get the guide-words to display correctly -
you definitely wouldn't be able to just book-end the Bible with some
code at the beginning and end. I don't know how easy it is to get margin
notes from two different text columns to combine into one margin
column. The rest of it seems not very challenging from a ConTeXt point
of view - footnotes are quite well-supported (though again for both the
footnotes and the margin notes there would be considerable hand-work
adding the commands for every single note, to make them appear in the
right places); and the physical layout of the page is not difficult in
itself.

The benefit of all that typing, if done with the right kind of planning
in mind, would be that later you'd easily be able to change the page
size, amount of white space, fonts and font sizes, etc.

The disadvantage would be that you would no longer have the "clean,
plain" text of the Bible in your ConTeXt file; it would be permanently
littered with commands and switches, so it would be much harder to check
your textual accuracy. Therefore you would want to be quite sure you
have exactly the Bible version you want, with all the spelling corrected
and verses and paragraphs the way they ought to be and so on, before you
begin your ConTeXt adventure.

-- 
David R
___________________________________________________________________________________
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:[~2013-07-23 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 15:45 INstalling the context version of TeX distro john Culleton
2013-07-17 15:54 ` Wolfgang Schuster
2013-07-17 15:56 ` Marco Patzer
2013-07-17 16:00 ` Sietse Brouwer
2013-07-19 18:51   ` john Culleton
2013-07-19 19:16     ` Pablo Rodríguez
2013-07-21  4:22       ` Can this layout be done in Context Russell Urquhart
2013-07-22  6:19         ` David Rogers
2013-07-23  1:11           ` Russell Urquhart
2013-07-23 19:47             ` David Rogers [this message]
2013-07-23 20:07               ` Hans Hagen
2013-07-22  8:01         ` Wolfgang Schuster
2013-07-23  1:17           ` Russell Urquhart

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=87d2q9xdmt.fsf@gmail.com \
    --to=davidandrewrogers@gmail.com \
    --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).