e fix it. Not elegant, but if it works it works!
>>
>> Good luck,
>> Taco
>>
>>
>> >
>> > \startcomponent[chapter-14]
>> > \startMPpage
>> > ...
>> > \stopMPpage
>> > \stopcomponent
>> >
>> &g
> >
> > \startcomponent[chapter-14]
> > \startMPpage
> > ...
> > \stopMPpage
> > \stopcomponent
> >
> > But if I compile my project, it disappears !!
> >
> > \startproduct[terminale-manual]
> > \startbodymatter
> >
gt; ...
> \stopMPpage
> \stopcomponent
>
> But if I compile my project, it disappears !!
>
> \startproduct[terminale-manual]
> \startbodymatter
> \component[chapter-1]
> \component[chapter-2]
> \component[chapter-3]
> \componen
le my project, it disappears !!
\startproduct[terminale-manual]
\startbodymatter
\component[chapter-1]
\component[chapter-2]
\component[chapter-3]
\component[chapter-4]
\component[chapter-5]
\component[chapter-6]
\component[chapter-7]
\comp
Hi Taco,
I knew I wouldn't be able to explain what was happening.
The code works perfectly and the figure is clearly visible in the component
chapter-14 :
\startcomponent[chapter-14]
\startMPpage
...
\stopMPpage
\stopcomponent
But if I compile my project, it disappears !!
\startpr
I produce a small magazine where the source files are organised into a product
and component structure.
For each issue, I have a main file with \startproduct and then,
inside that, several \component[filename] statements, one per article. Each
article starts in a standard way, including
> > > So I suggest you to save those keystrokes for other tasks. Not those,
> > > > petty petty betty. I know it's hard to teach an ol' dog new tricks,
> > > > but… it's worth to try! right?
> > >
> > > Please explain why this example (which is a val
ity to nest \starttext is necessary when you \startproduct etc.
where components can be be documents on its own and this means \startcomponent
includes \starttext in its
definition.
begin example
\starttext
\starttext
\stoptext
\stoptext
end example
but this doesn't.
begin
ity to nest \starttext is necessary when you \startproduct etc.
where components can be be documents on its own and this means \startcomponent
includes \starttext in its
definition.
begin example
\starttext
\starttext
\stoptext
\stoptext
end example
but this doesn't.
begin
eXt document) works
>
Opening a group with \starttext makes no sense because there is nothing after
\stoptext.
The possibility to nest \starttext is necessary when you \startproduct etc.
where components can be be documents on its own and this means \startcomponent
includes \starttext in its
e of contents does not appear. On the other
>> > hand, the 12 chapters are present.
>>
>> \startproduct[terminale-manual]
>>
>> \startfrontmatter
>> \starttitle[title=Table des matières]
>> \placelist
>
> I don't see why the table of contents does not appear. On the other
> > hand, the 12 chapters are present.
>
> \startproduct[terminale-manual]
>
> \startfrontmatter
> \starttitle[title=Table des matières]
> \placelist
>
On 4/20/2023 6:59 PM, Fabrice Couvreur via ntg-context wrote:
Hi,
I don't see why the table of contents does not appear. On the other
hand, the 12 chapters are present.
\startproduct[terminale-manual]
\startfrontmatter
\starttitle[title=Table des matières]
\plac
Hi,
I don't see why the table of contents does not appear. On the other hand,
the 12 chapters are present.
Thanks
Fabrice
\startproduct[terminale-manual]
\project[terminale-environment]
\startfrontmatter
\setuppagenumbering
[location=]
\definefont
[ChapterText
arden.net
__
_
% master000.tex – ConTeXt MkIV Module
\startproduct master000
\project iebpmonographs
\environment ieb-c-layout-000
\environment monograph-local-layout
\usemodule[statistical-charts]
% \enabletrackers[typesetters.suspects]
% \sho
documents.
Here are the files:
% /MainFolder/Meta.tex
\startproject *
\usepath [{ Metadata }]
\environment Environment.tex
\stopproject
% /MainFolder/Metadata/Environment.tex
\startenvironment *
% Test if setup is applied.
\setupbodyfont[ebgaramond]
\stopenvironment
% /MainFolder/SubFolder/SubSubFolde
On 10/16/2021 7:34 PM, Fabrice Couvreur via ntg-context wrote:
Hi,
The latest version of lmtx does not allow me to compile the following
file although there was no problem before.
Thank you
Fabrice
\startproduct[expertes-manual]
\startfrontmatter
\setuppagenumbering
Hi,
The latest version of lmtx does not allow me to compile the following file
although there was no problem before.
Thank you
Fabrice
\startproduct[expertes-manual]
\startfrontmatter
\setuppagenumbering
[location=]
\definefont
[ChapterTextStyle]
[SansBold*default
Hi Wolfgang,
Pablo's solution works, but I tried yours without success. Here are the
main lines of my project
begin product
\startproduct[terminale-manual]
\project[terminale-environment]
\startdocument
\startfrontmatter
...
\stopfrontmatter
\startbodymatter
\comp
because you
can use the *component mode to check whether the parent file is a
product or a component.
begin product
\startproduct [*]
\environment [...]
\startfrontmatter
...
\stopfrontmatter
\startbodymatter
\component [...]
\stopbodymatter
\stopproduct
end product
begin
use only ASCII characters
for the file names and avoid anything which is special in TeX,
using spaces or extra periods should be avoided as well.
2. Arguments for \component etc.
In my example I passed the argument to \component, \startproduct
etc. in square brackets but this is only a alternative
On 3/10/2021 5:56 PM, Wolfgang Schuster wrote:
Hi,
when the wildcard symbol is used as argument to \startcomponent (or
\startproduct) the name of the folder is now used and not the file name.
\startcomponent *
\quotation{\currentcomponent}
\stopcomponent
it's programmed that way (must
Hi,
when the wildcard symbol is used as argument to \startcomponent (or
\startproduct) the name of the folder is now used and not the file name.
\startcomponent *
\quotation{\currentcomponent}
\stopcomponent
Wolfgang
that I am having
with
my two volume proceedings.)
I'd be grateful for suggestions.
Best, Richard
% testproject.tex -- LMTX 2021.03.02
\startproject testproject
\product testproduct000
\product testproduct001
\stopproject
% master000.tex -- LMTX 2021.03.02
\startproduct testproduc
use \project to load only
one file but this is seldom needed.
begin product.tex
\startproduct *
\environment environment
\component component_1
\component component_2
\stopproduct
end product.tex
begin component_1.tex
\startcomponent *
\environment environment
...
\st
> Am 24.11.2020 um 22:38 schrieb Wolfgang Schuster
> :
>
> Jannik Voges schrieb am 24.11.2020 um 22:24:
>> Hello,
>> as the title suggested, I get an error when using spaces in the argument of
>> \startproduct. For example typesetting
>> \startproduct{foo ba
Hello,
as the title suggested, I get an error when using spaces in the argument
of \startproduct. For example typesetting
\startproduct{foo bar}
\starttext
foo
\stoptext
\stopproduct
results in an error:
tex error > tex error on line 2 in file ./foo bar.tex: Too many
Jannik Voges schrieb am 24.11.2020 um 22:24:
Hello,
as the title suggested, I get an error when using spaces in the argument
of \startproduct. For example typesetting
\startproduct{foo bar}
You can have a filename with a space use
\startproduct [foo bar]
but you don't even nee
opypages use the figure mechanism) with \setupexternalfigure[location=...]. Below is a modified (but untested) version of your sample document. Wolfgang begin product\startproduct product \environment env-WA % \setvariables% [document]% [ manual={Course Manual},% tit
of your sample document.
Wolfgang
begin product
\startproduct product
\environment env-WA
% \setvariables
% [document]
% [ manual={Course Manual},
% title={Title},
%subtitleone={Subtitle 1},
%subtitletwo={Subtitle 2},
% revnumber={Revision number
lamma The main product file==\environment env-WA \startproduct currentproduct % Document definitions\define\MyManual{Course Manual}\define\MyTitle{Title}\define\MySubtitleOne{Subtitle 1}\define\MySubtitleTwo{Subtitle 2}\define\MyRevnumber{Revision number} % Load frontmatter files\start
ld be able to copy and adapt to your needs.
Kind regards,
Jan Willem Flamma
*The main product file*
==
\environment env-WA
\startproduct currentproduct
% Document definitions
\define\MyManual{Course Manual}
\define\MyTitle{Title}
\define\MySubtitleOne{Subtitle 1}
\d
) Once the bodymatter starts the pagenumber is set to the arabic 1 (see below in the main product file) You should be able to copy and adapt to your needs. Kind regards,Jan Willem Flamma The main product file==\environment env-WA \startproduct currentproduct % Document definitions\define
Mahajan a écrit :
> On Thu, 7 May 2020, Fabrice Couvreur wrote:
>
> > Hi,
> > Here is part of a project that is starting to be heavy ; when i add a
> > chapter i do context seconde.tex
> > How do I compile only the chapter I just added ?
> > Thank you.
>
On Thu, 7 May 2020, Fabrice Couvreur wrote:
Hi,
Here is part of a project that is starting to be heavy ; when i add a
chapter i do context seconde.tex
How do I compile only the chapter I just added ?
Thank you.
Fabrice
\startproduct Seconde
\environment modules
\environment specialite-style
Hi,
Here is part of a project that is starting to be heavy ; when i add a
chapter i do context seconde.tex
How do I compile only the chapter I just added ?
Thank you.
Fabrice
\startproduct Seconde
\environment modules
\environment specialite-style
\environment specialite-macros
entering
> of the tabulation.
>
> Cheers,
> Tim
>
>
> \startproduct test-tabulate
>
> \setuppapersize[B5]
> \setuplayout
> [backspace=13pc,
> leftmargin=8pc,
> leftmargindistance=1pc,
> width=24.5pc,
> rightmargin=0pc,
> %%
> topspace=4pc,
> heade
the centering of the
tabulation.
Cheers,
Tim
\startproduct test-tabulate
\setuppapersize[B5]
\setuplayout
[backspace=13pc,
leftmargin=8pc,
leftmargindistance=1pc,
width=24.5pc,
rightmargin=0pc,
%%
topspace=4pc,
header=0pc,
height=49pc,
footer=0pc,
bottomdistance=2.5pc,
bottom=1pc,
location
variant,
they are way too big! (See attachment.) Pagella and Latin Modern do this right.
Is this a font issue or a ConTeXt issue? Anything I can do about this without
redefining every symbol I need by hand?
Cheers,
Tim
\startproduct test
\setupbodyfont[lucidaot,10pt]
$\square\boxtimes
. Can somebody give me a hint?
Cheers,
Tim
\startproduct test
\definefontfallback[pagellaarrows][texgyrepagella-math][arrows][check=yes,force=yes]
\definefontfallback[pagellaarrows][texgyrepagella-math][0x021AF][check=yes,force=yes]
\starttypescript[math][main]
\loadfontgoodies[lucida-typeone
uff before that,
> > including a table of contents. This has worked fine:
> >
> > \startproduct prd-pr23
> >
> > \startfrontmatter
> > \setuppagenumber[stop]
> > \component pr23-cover_front_web
> > \component blank.tex
> > \component c-cont
Mari Voipio schrieb am 02.09.2019 um 13:07:
Hello!
I have a document where I want the page numbers to start from the
first page of chapter one. There's bunch of stuff before that,
including a table of contents. This has worked fine:
\startproduct prd-pr23
\startfrontmatter
\setuppagen
oject
```
- test_prod.tex
```
\startproduct *
\project test
\startalignment[middle]
HEY
\stopalignment
\component test_comp
\stopproduct
```
- test_comp.tex
```
\startcomponent *
\product test_prod
% \project test_project % uncomment this to use the
\section{Test}
\input ward
\stopcomponent
```
>
,
incrementnumber=list]
\startproduct Danggok
\definestructureconversionset[frontpart:pagenumber][][romannumerals]
\definestructureconversionset[bodypart:pagenumber][][numbers]
\definestructureconversionset[backpart:pagenumber][][numbers]
\startsectionblockenvironment[frontpart]
\setupuserpagenumber
\startproduct [*]
\project [project_skel]
\startdocument
\component [c_01]
\component [c_02]
\stopdocument
\stopproduct
or
[..]
Environment file:
1. Don’t load the project from your environment file
2. Don’t use \usepath to set the folders for the
can be
> used to insert a titlepage or endpage). You can even use \startdocument (or
> \setupdocument) to set the document name in the pdf viewer (yes it can also
> be done with \setupinteraction but \startdocument is nicer).
>
> A minimal file would be
>
> \star
confirmation of the above assumption.
The \product command is more or less useless because it provides only
the information
of the main file of the document.
The real question is where you should put the \project or \environment
commands.
When you put them before \startproduct you’re loading your
\setupinteraction but
\startdocument is nicer).
A minimal file would be
\startproduct [*]
\project [project_skel]
\startdocument
\component [c_01]
\component [c_02]
\stopdocument
\stopproduct
or
\startproduct [*]
\project [project_skel]
\startdocument
pected behaviour, or not?
Opening a group with \starttext makes no sense because there is nothing after
\stoptext.
The possibility to nest \starttext is necessary when you \startproduct etc.
where components
can be be documents on its own and this means \startcomponent includes
\starttext in its
ext
Is this the expected behaviour, or not?
Opening a group with \starttext makes no sense because there is nothing after
\stoptext.
The possibility to nest \starttext is necessary when you \startproduct etc.
where components
can be be documents on its own and this means \startcomponent in
Garden):
\starttext
text
\starttext
\bf text
\stoptext
text % this text is in bold, too.
\stoptext
Is this the expected behaviour, or not?
Opening a group with \starttext makes no sense because there is nothing
after \stoptext.
The possibility to nest \starttext is necessary when you \startproduc
My ConTeXt ver: 2017.05.15 21:48 MKIV beta fmt: 2017.6.10
>
> Grateful for any hints about where I'm going wrong.
>
> Mike
>
> - project_guide.tex -
> \startproject project_guide
> \environment env_guide
>
> \product prd_guide
>
> \stopproject
>
> -
are
from the latest beta:
My ConTeXt ver: 2017.05.15 21:48 MKIV beta fmt: 2017.6.10
Grateful for any hints about where I'm going wrong.
Mike
- project_guide.tex -
\startproject project_guide
\environment env_guide
\product prd_guide
\stopproject
- prd_guide.tex ---
Hello,
How to compile the final chapter added (sequences/probabilites) without
recompiling all the other chapters ?
The command line is currently used context --purgeall cours.tex
Thank you
Fabrice
\startproduct cours
\project documents
\startfrontmatter
\component contents
tex error > tex error on line 2 in file reference-manual-1.tex: ! TeX
capacity exceeded, sorry [text input levels=600]
\m_syst_action_nop #1 ->\clf_startproduct {#1}
l.11 \startproduct reference-manual-1
whether such commands exist; anyway, I didn't need them)
\mainlanguage[cz]
...
book.tex
% Main file to build the whole book
\environment styles.sty
\startproduct *
\startfrontmatter
...
\stopfrontmatter
\startbodymatter
\component comp01
...
\stopbodymatter
\s
rmation regardless I compile
a component or a product.
My solution:
envi_thesis.tex -
\startenvironment envi_thesis
%% PATHS
\usepath[{comp_chapter1,comp_chapter2}]
blah blah blah
\stopenvironment
prod_thesis.tex --
\star
blah blah
\stopcomponent
prod_thesis.tex has:
\startproduct prod_thesis
\environment envi_thesis
blah blah blah
\component comp_chap1
\component comp_chap2
(...)
\stopproduct
and finally, envi_thesis.te
rence=chaptwo, title={Plain chapter two}]
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
\startsection[reference=sectwowithpic, title={Section chap2 with image}]
\startplacefigure[reference=figtwo, title={Figure 2}]
\externalfigure[cow.pdf]
\stopplacefigure
\stopsection
\stopchapt
.
2.
Part 3 Title
1.
2.
##
lesson.tex
\project manual
\startproduct lesson
\startfrontmatter
\component titlepage
\component contents
\stopfrontmatter
\startbodymatter
\component chapter-1
\component chapter-2
\stopbodymatter
\stoppr
Hi,
My product lesson contains the component chapter-1 which itself contains
the components activities and synthesis.
Is it possible to compile lesson.tex and have the output that
activities.pdf file
?
Thanks,
Fabrice
\project manual
\startproduct lesson
\startfrontmatter
\component
rong, or is this a known bug (such that I
> should cease my attempts)? Is \useexternaldocument the wrong command for this
> purpose? Minimum example files below:
>
> % project
> \project project_xref
> \startproduct prd_xref
> \component xref1
> \component xref2
> \stop
(such that I should
cease my attempts)? Is \useexternaldocument the wrong command for this purpose?
Minimum example files below:
% project
\project project_xref
\startproduct prd_xref
\component xref1
\component xref2
\stopproduct
% product
\startproject project_xref
\environment env_xref
produced, where the first part—ComponentA—uses
EnvironmentA’s layout, while the second part—ComponentB—uses EnvironmentB's. If
any startsetups need to be defined, I’d be grateful for any example, showing
also where to place them.
# Product
\startproduct MyProduct
\component ComponentA
\comp
EnvironmentA’s layout, while the second part—ComponentB—uses EnvironmentB's. If
any startsetups need to be defined, I’d be grateful for any example, showing
also where to place them.
# Product
\startproduct MyProduct
\component ComponentA
\component ComponentB
\stopproduct
# Environ
Dear everyone,
I am currently implementing the old French Bible of David Martin in ConTeXt
MkIV.
The source code looks like this:
\startproduct martin1707
\project bibles % Font settings, page layout, etc.
\startbiblebook[number={1}, name={Genéſe}, abbreviation={Gen.}, title={Le
On 7/19/2015 1:24 PM, Joas Yannick wrote:
Dear everyone,
I am currently typesetting the old (published in 1707) French Bible of
David Martin using
ConTeXt MkIV. The source code looks like this:
\startproduct martin1707
\startproject bibles % Page layout, fonts, language, etc
Dear everyone,
I am currently typesetting the old (published in 1707) French Bible of
David Martin using
ConTeXt MkIV. The source code looks like this:
\startproduct martin1707
\startproject bibles % Page layout, fonts, language, etc.
\startbiblebook[number={1}, name={Genéſe
document you are reading now}
\pages{14}
\stoppublication
\startproduct components-001
\startfrontmatter
% \component components-002
two: \cite[me]
\stopfrontmatter
\placepublications
[criterium=text]
\stopproduct
But, I'm not able to compile even this file.
I'
Hello,
suppose the following case:
Book.mkiv
\startproduct *
\component A.mkiv
\component B.mkiv
\stopproduct
A.mkiv
\startcomponent *
\section{A}
\stopcomponent
B.mkiv
\startcomponent *
\section{B}
\stopcomponent
When compiling "Book.mkiv&
Hello,
suppose the following case:
Book.mkiv
\startproduct *
\component A.mkiv
\component B.mkiv
\stopproduct
A.mkiv
\startcomponent *
\section{A}
\stopcomponent
B.mkiv
\startcomponent *
\section{B}
\stopcomponent
When compiling "Book.mkiv", I
t;
>
> Yes, this is strange. `\enabledirectives [system.synctex]` works for me *if*
> it’s in the product file (no `--synctex` switch needed). It even works if it
> is not in the first line, for example:
>
> Product file:
>
> \startproduct pd-test
> \enabledirectives
tch needed). It even
works if it is not in the first line, for example:
Product file:
\startproduct pd-test
\enabledirectives [system.synctex]
\component 01-intro
\stopproduct
Component:
\startcomponent 01-intro
Hi there, can you show me this sentence in the source file?
\stopcomponent
But, ind
> Am 13.03.2015 um 09:01 schrieb Wolfgang Werners-Lucchini :
>
>> According toll my observations, you need to reference the needed parts
>> inside of the \start... and \stop..., so your product would become:
>>
>>
>> ```
>> \startproduct pd-medizin
\stopproject
% prd.tex
\startproduct prd
\project prj
\starttext
Bla bla
\stoptext
\stopproduct
Note that when using \everystoptext rather than \everystarttext, it does work
(it adds the text to the last page)
So what am I doing wrong ?
\startsetups [document:title
a minimal (not) working example:
% env.tex
\startenvironment env
\setuppapersize[A5]
\appendtoks
Title page
\to \everystarttext
\stopenvironment
% prj.tex
\startproject prj
\environment env
\stopproject
% prd.tex
\startproduct prd
\project prj
initial
prd_book.tex ===
\startproduct prd_book
\project project_cataoia
\starttext
\start
\startstandardmakeup[doublesided=no]
\ss
\hairline \start
\blank[line]
\switchtobodyfont[16pt]\bf
\leftaligned{Chess}%
\blank[line]
\leftaligned{and the Art of}%
\blank[line
> According toll my observations, you need to reference the needed parts
> inside of the \start... and \stop..., so your product would become:
>
>
> ```
> \startproduct pd-medizin
> \project pj-medizin
> \component test
> \stopproduct
> ```
>
> You also hav
According toll my observations, you need to reference the needed parts
inside of the \start... and \stop..., so your product would become:
```
\startproduct pd-medizin
\project pj-medizin
\component test
\stopproduct
```
You also have to restructure the other files, so that \start... is the
space[medium]
> \stopenvironment
> --pj-medizin.tex---
> \environment env-medizin
> \startproject pj-medizin
> \product pd-medizin
> \stopproject
> --pd-medizin.tex---
> \project pj-mediz
\product pd-medizin
\stopproject
--pd-medizin.tex---
\project pj-medizin
\startproduct pd-medizin
\component test
\stopproduct
--test.tex---
\project pj-medizin
\product pd-medizin
\startcomponent test
> Am 14.01.2015 um 19:28 schrieb 19cat :
>
> Hello, again.
>
> I have another issue.
>
> When I put \definefontfeature command into environment file, doesn't work. I
> must put in product file, before \startproduct command.
>
> You know why?
Load the
Hello, again.
I have another issue.
When I put \definefontfeature command into environment file, doesn't work. I
must put in product file, before \startproduct command.
You know why?
This is my tree structure:
prd_productname
env_productname
c_title
c_cha
tags are hooked into starttext and at startproduct time export
is not yet enabled,
Nice that you immediately found the error! I suppose it is fixed in next beta?
Indeed. Uploading now. You were lucky that I was looking at the export
already ... now
\setupbackend
[export=yes
Here you are.
>
> Ah, the document tags are hooked into starttext and at startproduct time
> export is not yet enabled,
Nice that you immediately found the error! I suppose it is fixed in next beta?
Greetlings, Hraban
---
http://www.fiee.net/texnique/
ht
On 8/27/2014 11:25 AM, Henning Hraban Ramm wrote:
Am 2014-08-27 um 15:05 schrieb Hans Hagen :
I.e. the root node is missing.
hm, can you make a small example?
Here you are.
Ah, the document tags are hooked into starttext and at startproduct time
export is not yet enabled,
Hans
t least in the following product file with two components, some links
>> work (\reference), some only sometimes (\at) and others never (\in). The
>> problem seems to be with labels.
>>
>> \startproduct LinkTest
>> \setupinteraction[state=start]
>> \component Test0
.
\startproduct LinkTest
\setupinteraction[state=start]
\component Test01
\component Test02
\stopproduct
\startcomponent Test01
\product LinkTest
\reference[startknuth]{}\input knuth
\page
\input knuth\reference[endknuth]{}\footnote[knuth]{A note.}
\section[new]{a title}
\input ward
\page[makeup
Hans--there are still some odd failures in hyperlinking between components.
At least in the following product file with two components, some links work
(\reference), some only sometimes (\at) and others never (\in). The problem
seems to be with labels.
\startproduct LinkTest
\setupinteraction
ironment env" before the \startproduct).
The first problem is that it seems some of the functionality of
products, projects, and components is lost. But maybe that's a matter
of taste.
Another problem is that env.tex doesn't know that one is compiling a
product or component---
Sanjoy Mahajan writes:
> The wiki page for "Project Structure" has always shown setups (via
> \project ... ) going after the \startcomponent or \startproduct. I've
> edited the examples to have setups before the
> \start(product|component). If I did it wrong, let
gt; context sets and resets some values with \starttext etc. and to avoid some
> problems it’s better to put all setup commands before it.
Agreed. The wiki page for "Project Structure" has always shown setups
(via \project ... ) going after the \startcomponent or \startproduct.
I
something wrong?
Thanks!
Steffen
Am 04.07.2013 um 12:07 schrieb Wolfgang Schuster :
>
> Am 02.07.2013 um 17:30 schrieb Steffen Kram :
>
>> Hello,
>>
>> is it possible to reference parts of a document in a "relative" style?
>>
>> My struct
Am 02.07.2013 um 17:30 schrieb Steffen Kram :
> Hello,
>
> is it possible to reference parts of a document in a "relative" style?
>
> My structure is as follows:
>
> \startproduct
> …
> \startbodymatter
> \component chapterFoo/main
> \
Hello,
is it possible to reference parts of a document in a "relative" style?
My structure is as follows:
\startproduct
…
\startbodymatter
\component chapterFoo/main
\component chapterBar/main
\stopbodymatter
…
\stopproduct
Each of my chapters uses \chapter, \section … \subsub
"project.tex".
project.tex:
\startproject proj
\product product1/product.tex
\product product2/product.tex
\stopproject
product1/product.tex:
\startproduct prod1
\component product1/components/component1.tex
% I would like to use "components/component1.tex"
% that is a
\startproduct prd
\component cmp
\stopproduct
2. env.tex
\startenvironment env
\define\testing{This is a test}
\stopenvironment
3. cmp.tex
\product prd
\startcomponent cmp
Testing \testing
\stopcomponent
When I compile cmp.tex, I get
On Tue, 16 Apr 2013, Wolfgang Schuster wrote:
Am 16.04.2013 um 09:32 schrieb Aditya Mahajan :
Has something changed recently on how product-component structure is supposed to
be used? I have three files:
1. prd.tex
\environment env
\startproduct prd
\component cmp
Am 16.04.2013 um 09:32 schrieb Aditya Mahajan :
> Has something changed recently on how product-component structure is supposed
> to
> be used? I have three files:
>
> 1. prd.tex
>
>\environment env
>
>\startproduct prd
>
>\component cmp
>
gt; be used? I have three files:
>
> 1. prd.tex
>
> \environment env
>
> \startproduct prd
>
> \component cmp
>
> \stopproduct
>
> 2. env.tex
>
>
> \startenvironment env
>
> \define\testing{This is a te
1 - 100 of 299 matches
Mail list logo