From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \product tag
Date: Wed, 8 Aug 2012 05:32:12 +0200 [thread overview]
Message-ID: <4CC9C92D-50AC-4F50-B751-FA9D1F290D98@gmail.com> (raw)
In-Reply-To: <20120807202917.28dad9cb@sda3.wexfordpress.net>
Am 08.08.2012 um 02:29 schrieb john Culleton <John@wexfordpress.com>:
> In a MKIV file using the approved method of structuring projects,
> does the \product tag do anything or is it just internal
> documentation for the source file? When I process a file called
> book.tex and containing the tag:
> \product foobar
> the result is a file called book.pdf, just as if the tag did not
> exist.
The name of the output file is always the name of the main input file
and you can only change this with the result option for context/texexec scripts.
The \product command is a special version of \input and the given file
is only read when the command appears in a project file and since it is
no longer recommended to use a project as main file the command has
no real purpose except a internal reference (in a component) to the parent file.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-08-08 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 0:29 john Culleton
2012-08-08 3:32 ` Wolfgang Schuster [this message]
2012-08-08 14:28 ` Sietse Brouwer
2012-08-08 21:45 ` 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=4CC9C92D-50AC-4F50-B751-FA9D1F290D98@gmail.com \
--to=wolfgang.schuster@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).