ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pavneet Arora <pavneet_arora@waroc.com>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Template for handling editorial content in a large book project
Date: Sat, 8 Aug 2015 11:03:42 -0400	[thread overview]
Message-ID: <20150808150342.GG23211@darjiling> (raw)
In-Reply-To: <alpine.OSX.2.02.1508080937380.68804@nqv-znpobbx>

Perfect.  I think that modes will work nicely.

To further explain my use case:  I have a manuscript, which I would like 
to continue to evolve with editorial comments, suggestions, ideas for 
further development (some generated by the author, others by reviewers).  

At any given time the "text" of the document is lagging the editorial 
input.  Revisions of the project are under "mercurial" source code 
control.  The primary view of the document is to be a publication ready 
version, but in its draft form, the author's version should include the 
work-in-progress.  Eventually, the editorial comments may diminish or be 
left for another day, and the work-in-progress will get incorporated 
into the main text.  The "publication" view is useful if you have 
multiple people reviewing the book, and you don't want to proliferate 
the union of all editorial comments into the review copy.

I wanted to capture this author-editor workflow under ConTeXt.  I think 
modes will be just what I need.

Thanks.

On 08Aug15, Aditya Mahajan wrote:
> On Sat, 8 Aug 2015, Pavneet Arora wrote:
> 
> >I am working on a large book project.  What I need done in ConTeXt
> >is something similar to what Boris presented at TUG 2015:
> >
> >http://tug.org/tug2015/abstracts/veytsman-access.txt
> >
> >In other words, the output should address different audiences.  In
> >my case, I want the full project to continue to contain editorial
> >comments, or notes by the author.  I am thinking of using both
> >margin notes, and specially styled paragraphs (narrower, font
> >change, etc.).  Then depending on the target audience, reader or
> >editor, the editorial comment could be included or not.
> >
> >Is there a recommended design pattern that I could use for this
> >type of work?
> 
> I am not sure I completely understand your question, but have a look
> at modes: http://wiki.contextgarden.net/Modes
> 
> Aditya

-- 
----
Pavneet Arora           m: 647.406.6843
Waroc Informatik        t: 416.937.9276
___________________________________________________________________________________
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-08-08 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08 12:23 Pavneet Arora
2015-08-08 13:38 ` Aditya Mahajan
2015-08-08 15:03   ` Pavneet Arora [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=20150808150342.GG23211@darjiling \
    --to=pavneet_arora@waroc.com \
    --cc=adityam@umich.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).