From: "Stefan Müller" <warrence.stm@gmx.de>
To: ntg-context@ntg.nl
Subject: Trouble with ConTeXt's project structure
Date: Sun, 17 Oct 2010 21:43:11 +0200 [thread overview]
Message-ID: <201010172143.11583.warrence.stm@gmx.de> (raw)
Dear list,
I tried to set up a project of mine using the project structure propagated in
the wiki [1]. Because I ran into some trouble I made the following small
example (using MkIV, minimals 2010.10.14 13:14).
%% project_mymag.tex
\startproject project_mymag
\environment env_mymag
\product prd_year2004-01
\completecontent[criterium=all]
\stopproject
%% EOF
%% env_mymag.tex
\startenvironment env_mymag
\setupindenting[medium, yes] %some random setup
\stopenvironment
%% EOF
%% prd_year2004-01
\startproduct prd_year2004-01
\project project_mymag
\component c_editorial
\component c_article01
\stopproduct
%% EOF
%% c_editorial.tex
\startcomponent c_editorial
\product prd_year2004-01
\project project_mymag
\chapter{Editorial}
Dear reader...
\stopcomponent
%% EOF
%% c_article01.tex
\startcomponent c_article01
\product prd_year2004-01
\project project_mymag
\chapter{First Article}
This will be awesome...
\stopcomponent
%% EOF
When I translate the project file I get what I want, e.g. 3 pages: first page
"Editorial", second page "First Article", third page "Content".
When I translate the product file I don't get "Editorial", "First Article" as
expected, but "Content", "Editorial", "First Article". It seems as if context
first typesets the project file without going down inside the products again,
before typesetting the originally called project.
When I translate one of the component files, lets say c_editorial.tex, I get
"Contents", "Editorial" instead of just one page "Editorial". Again, it seems
as if context first looks inside the project file (without going down) and only
then typesets the component.
Another case, same problem. If I drop the "product", i.e. I only have a
project file including several components, the individual component files and an
environment file, kind of the same problems appear. Translating the project file
works well. Translating the component file c_editorial.tex results in a PDF
with 4 pages (instead of one with "Editorial"): "Editorial", "First Article",
"Contents", "Editorial". Context puts the whole project in the PDF and appends
the component c_editorial...
All this seems very strange to me, especially since a friend told me project
structure works pretty well in his projects. I tested on two different machines
(Windows Vista and Linux). Am I doing something wrong? Is this a bug or a
feature?
Thanks for your help in advance.
Best wishes,
Stefan.
[1] http://wiki.contextgarden.net/Project_structure
___________________________________________________________________________________
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 reply other threads:[~2010-10-17 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 19:43 Stefan Müller [this message]
2010-10-17 23:29 ` Henning Hraban Ramm
2010-10-18 10:00 ` Stefan Müller
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=201010172143.11583.warrence.stm@gmx.de \
--to=warrence.stm@gmx.de \
--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).