ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \product tag
Date: Wed, 8 Aug 2012 16:28:24 +0200	[thread overview]
Message-ID: <CAF=dkzzj_ZPuLs=_bDMEE+mc3n8OuxC4qrHy29K46B5v-85NYQ@mail.gmail.com> (raw)
In-Reply-To: <20120807202917.28dad9cb@sda3.wexfordpress.net>

Hi John,

What Wolfgang said: `\product X` should be processed once inside
`\startproject` environments, and never otherwise. And you should
probably have products as your build targets, not projects.

@Hans: when I looked at the `processors` table in file-job.lua, I
found some discrepancies between the processing commands and the
reporting strings. Here is the table edited to show just the
discrepancies:

local processors = utilities.storage.allocate {
    -- [we_are_inside_startthis] = {
    --     [we_encounter_this] = { "string_for_message",
processing_command }, -- comment
    -- }
    [v_text] = {
        [v_project]     = { "none", context.processfileonce }, -- none
        [v_product]     = { "none", context.processfileonce }, -- none
    },
    [v_project] = {
        [v_product]     = { "once", context.processfilenone }, -- once
        -- consistent, but strange comment
        [v_component]   = { "none", context.processfilenone }, -- many *
    },
    [v_product] = {
        [v_product]     = { "none", context.processfilemany }, -- none
    },
}

Is this all right? In general, the reporing strings are the ones
consistent with the table at the bottom of
http://wiki.contextgarden.net/Project_structure
which is taken from page 3 of
http://pragma-ade.com/general/magazines/mag-1101.pdf

Cheers,

Sietse


On Wed, Aug 8, 2012 at 2:29 AM, john Culleton <John@wexfordpress.com> wrote:
> 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.
>
> --
> John Culleton
> Free list of books for self-publishers:
> http://wexfordpress.net/shortlist.html
> Police Procedural and Expose: "Death Wore Black"
> "Create Book Covers with Scribus"
> http://www.booklocker.com/books/4055.html
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2012-08-08 14:28 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
2012-08-08 14:28 ` Sietse Brouwer [this message]
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='CAF=dkzzj_ZPuLs=_bDMEE+mc3n8OuxC4qrHy29K46B5v-85NYQ@mail.gmail.com' \
    --to=sbbrouwer@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).