From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trouble with ConTeXt's project structure
Date: Mon, 18 Oct 2010 12:00:46 +0200 [thread overview]
Message-ID: <4CBC1ACE.10304@gmx.de> (raw)
In-Reply-To: <69DADB50-F26C-4EB3-B5E0-8F67E29F37DF@fiee.net>
On 18.10.2010 01:29, Henning Hraban Ramm wrote:
> Am 2010-10-17 um 21:43 schrieb Stefan Müller:
>
>> 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).
> ...
>> 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?
>
> Consider it a feature that actual code in your project file is always
> executed.
> Consider the table of content call in the wiki a bad example. Mea culpa.
> Change it.
>
> Greetlings from Lake Constance!
> Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
Okay, so the \completecontent should be put inside another component, right?
>> 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...
For me the trouble lies more in my second example "Another case, same
problem" because the "\component c_something" calls are also considered
as "actual code", not only the \completecontent. Using a (fake) product
in this case seems to me like a workaround.
Thank you very much so far,
Stefan.
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-18 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 19:43 Stefan Müller
2010-10-17 23:29 ` Henning Hraban Ramm
2010-10-18 10:00 ` Stefan Müller [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=4CBC1ACE.10304@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).