ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid ادريس سماوي حامد via ntg-context" <ntg-context@ntg.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
Subject: Can modes be used for content control?
Date: Tue, 16 Nov 2021 16:25:05 -0700	[thread overview]
Message-ID: <op.1cy4ocleejo439@desktop-mt1m160> (raw)

Dear gang,

For creating/authoring content in ConTeXt: Can modes or the like be used  
for content control? For example, someone wants to write at least two  
versions of a book managed from a single file. So, e.g., we may have

a) abridged content
b) unabridged content - includes a)
c) abridged content + translation
d) unabridged content + translation
[:]

One can author and organize this in XML - pre-ConteXt - but perhaps one  
prefers to write in ConTeXt (take advantage of shortcuts etc.). So maybe

\defineparagraphs[unabridged]
\defineparagraphs[abridged]
\defineparagraphs[translation]

Then one authors the complete work in a single project, but you can  
produce a variety of versions, depending on the mode chosen:

\definemode[unabridged]
etc.

Can one do this in context? If so, does anyone have some working example  
of how to do it? Might even be worth a MyWay if not too unwieldy.. Thank  
you in advance!

Best wishes
Idris
-- 
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2021-11-16 23:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 23:25 Idris Samawi Hamid ادريس سماوي حامد via ntg-context [this message]
2021-11-17  0:23 ` Aditya Mahajan via ntg-context
2021-11-17  3:06   ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 11:32     ` Henning Hraban Ramm via ntg-context
2021-11-17 15:08       ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 15:51         ` Henning Hraban Ramm via ntg-context
2021-11-17 19:52           ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 15:57         ` Taco Hoekwater via ntg-context
2021-11-17 17:56     ` Aditya Mahajan via ntg-context
2021-11-17 18:54       ` Hans Hagen via ntg-context
2021-11-17 19:45         ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 19:36       ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17  7:59 ` Hans Hagen via ntg-context

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=op.1cy4ocleejo439@desktop-mt1m160 \
    --to=ntg-context@ntg.nl \
    --cc=Idris.Hamid@colostate.edu \
    /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).