From: Wei-Wei Guo <wwguocn@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texts in \component files are not present
Date: Mon, 11 May 2009 08:32:23 +0800 [thread overview]
Message-ID: <4A077217.8070800@gmail.com> (raw)
In-Reply-To: <ECDA434E-052D-4189-958E-87B4CC7D5495@gmail.com>
Wolfgang Schuster 写道:
>> Text in component files are not included in the attached example. I
>> also put the log
>> file in it. The log shows that the component files were found and
>> complied but their
>> texts were not present in the generated pdf file.
>>
>> I'm not sure whether I did anything wrong in the example or not. I
>> checked many time
>> and didn't find anything.
>
> Works OK for me but I found a few you could/should change.
>
> 1. Don't use project files as top level file for your document, use
> product and
> components (which can be nested) files only, projects are meta file
> when you
> have many document with the same topic (e.g. a magazine etc.)
>
A magazine is really one of my purposes. :)
> 2. You can write \usepath[kaka,leasure] in your environment files and write
> in test.tex
>
> \component leasure
> \component kaka
>
> ConTeXt looks now in both directories for the files leasure.tex and
> kaka.tex
> but take care to use unique filenames.
>
After adding \usepath[kaka,leasure], the texts in \component present, but, as the
caution you mentioned, since I have two files with the same name, i.e. mytime.tex,
only the file in kaka/ is added and is added twice. Although \usepath can partly
solve my problem, it limits flexibility.
Best wishes,
Wei-Wei
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-11 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 15:29 Wei-Wei Guo
2009-05-10 15:42 ` Hans Hagen
2009-05-11 0:25 ` Wei-Wei Guo
2009-05-10 17:15 ` Wolfgang Schuster
2009-05-11 0:32 ` Wei-Wei Guo [this message]
2009-05-11 6:34 ` Henning Hraban Ramm
2009-05-11 14:53 ` Wei-Wei Guo
2009-05-11 14:53 ` Henning Hraban Ramm
2009-05-12 8:12 ` Wei-Wei Guo
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=4A077217.8070800@gmail.com \
--to=wwguocn@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).