Dear Wolfgang,
Thank you for the comment.
I made a mistake during the process of combining two files(a product file and a
component file).
Here is a working minimal sample file.
\definefontfamily[notoFont][rm][Noto Serif CJK KR]
[ it={style:regular,features:{*,slanted}},
sl
translate to:
>>
>> \usepath [asset,asset/tex,results,source]
>> \usepath [../asset,../asset/tex,../results,../source]
>>
>> which should work from root and one level down but probably not from two
>> levels down i.e. not from within ./asset/tex. For that yo
er using a product-component based solution.
You'll then be able to process each file indivdually while still having a
main file around. The page numbers in the individual file will be incorrect,
i.e. always start at 1, but for having a quick look that still might be
nice. (Hans or Wolfgang p
mmand=\groupedcommand{\blank[medium]}{},
numbercolor=,
textstyle=,
numberstyle=,
numbercommand=,
before=\startChapterFrame,
after=\stopChapterFrame,
header=nomarking]
\stopsetups
\startsectionblockenvironment [bodypart]
\directsetup{section:chapter}
\stopsectionblo
Hi,
Thanks for your help. I did several tests playing only with the code of
component 5 which interferes with that of component 14.
@Aditya
begingroup;
.
endgroup;
does not work.
@Hans
save defaultfont, defaultscale;
maybe also:
save circle, p, q, b ;
I get an empty rectangle in place of
it :
> Hi Hans and Taco,
> @Hans, I compiled by commenting and uncommenting one component at a time;
> it is component 5 which interferes with the metapost code of component 14
> All I have to do now is find out what the cause is.
> Fabrice
>
> Le jeu. 25 avr. 2024 à 16:40, Taco
Hi Hans and Taco,
@Hans, I compiled by commenting and uncommenting one component at a time;
it is component 5 which interferes with the metapost code of component 14
All I have to do now is find out what the cause is.
Fabrice
Le jeu. 25 avr. 2024 à 16:40, Taco Hoekwater a écrit :
>
>
>
> On 25 Apr 2024, at 16:08, Fabrice Couvreur
> wrote:
>
> 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 :
It is probably not related to the figur
On 4/25/2024 4:08 PM, Fabrice Couvreur wrote:
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 compi
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
it helps: I currently have
\startFMTitle[reference=\Reference, title={}][itemAuthor=AuthorName,
itemTitle=ShortTitle,...]
\setuplist[FMTitle][state=start, alternative=startendfmpages,
criterium=all,]
(\Reference is defined at the in the preamble to input of the
file/component
for a few high perfotmance cores over
dozens of so called efficient cores.
(that said: luametatex runs fine on my mobile phone)
Option 2: Split your book into a project with each chapter, or even part of a
chapter as a separate component and compile only the chapter you are working
on. Set up
ed-up far
faster than waiting for Hans to make changes, even assuming there is something
that can be changed. I'd recommend a Mac M3 :-)
Option 2: Split your book into a project with each chapter, or even part of a
chapter as a separate component and compile only the chapter you are working
Hi Shiv,
ConTeXt’s project structure has many benefits. One is speed. See
https://wiki.contextgarden.net/Project_structure.
My books and long papers are products, each containing many components
(chapters or sections). When I’m working, I have both the product and a
component open. I
ow.
The 9 elements of the grid will be
- such a diagram that explains the building blocks / general workflow
– the diagram of the layout areas
– the project structure (environment, product, component)
– some examples of code and results
I wanted to use the “christmas card” squares for borders around and
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
nk you for this hint. It works (almost) as expected:
Strangely, I had to add, explicitly,
\startfrontmatter
\component FrontMatterStuff
\page[yes,header,footer,right]
\stopfrontmatter
\startbodymatter
...
\stopbodymatter
In order to get the frontmatter end with a totally blank page befor
s expected:
Strangely, I had to add, explicitly,
\startfrontmatter
\component FrontMatterStuff
\page[yes,header,footer,right]
\stopfrontmatter
\startbodymatter
...
\stopbodymatter
In order to get the frontmatter end with a totally blank page before a
right Chapter 1 header. Using just the
It's chapter_5 that's the problem, but how do you know what's causing the
table of contents not to appear ?
Le ven. 21 avr. 2023 à 14:42, Fabrice Couvreur
a écrit :
> Hi Hans,
> Alright, I'll compile by integrating one component at a time to figure out
> whi
Hi Hans,
Alright, I'll compile by integrating one component at a time to figure out
which one is causing the problem.
Thanks.
Fabrice
Le jeu. 20 avr. 2023 à 15:52, Hans Hagen via ntg-context
a écrit :
> On 4/20/2023 6:59 PM, Fabrice Couvreur via ntg-context wrote:
> > Hi,
>
atter
\startbodymatter
\component[chapitre_1]
\component[chapitre_2]
\component[chapitre_3]
\component[chapitre_4]
\component[chapitre_5]
\component[chapitre_6]
\component[chapitre_7]
\component[chapitre_8]
\component[chapi
ive=c]
\stoptitle
\stopfrontmatter
\startbodymatter
\component[chapitre_1]
\component[chapitre_2]
\component[chapitre_3]
\component[chapitre_4]
\component[chapitre_5]
\component[chapitre_6]
\component[chapitre_7]
\component[chapi
e new feature with formula autosplitting looks
> > also very promising. For me it is important to obtain the high quality
> > without a lot of manual tweaks of each formula for each given document
> > format and figure placement.
> >
> > However, I have found a problem wit
n document
format and figure placement.
However, I have found a problem with references if I compile one
component only. The references to formulas in other components have
wrong prefixes, e.g. (2.1) instead of (3.1). Needless to say, the right
formula references are very important.
I start
t and figure placement.
>
> However, I have found a problem with references if I compile one
> component only. The references to formulas in other components have
> wrong prefixes, e.g. (2.1) instead of (3.1). Needless to say, the
> right formula references are very important.
>
oblem with references if I compile one component
only. The references to formulas in other components have wrong prefixes,
e.g. (2.1) instead of (3.1). Needless to say, the right formula references
are very important.
I started looking into this issue. The references to other components are
taken from
wbodyfont
% \showbodyfontenvironment
\useexternaldocument[m001][master001][Whispering of Inscriptions,
Vol.~{\sc ii}]
\startfrontmatter
\component tlpg000
{
\setupheadtext[content=Contents of Vol.~i.]
\setupheadertexts[Contents of
Vol.~i.][pagenumber][pagenumber][Contents of Vol.~i.]
\noheaderandfo
on to work (if that is
possible). If not, is it possible compile the whole product but only
output a certain page range?
You need a reference to the environment file from within the component
file, otherwise ConTeXt has no knowledge of the bib file.
Wol
useAlternatePath
> % !TEX useConTeXtSyncParser
>\setupsynctex[state=start, method=max]
>
> Syncing works well enough—though I can see no difference between method =min
> and method=max, both highlight only a few words and not the entire text to be
> synced, but perhaps m
between method
=min and method=max, both highlight only a few words and not the entire
text to be synced, but perhaps my expectations are out of line.
When I have these lines at the top of a component file and typeset the
product file, I get a rootfile.synctex file, but syncing itself goes awry.
Nothing
The setup I offered in the previous email was all correct, but in a
large project like a dictionary with 26 or more components there can
always be something else that goes wrong! Component 'D' had an extra {
in it, but oddly enough the component was compiling, except that I
picked u
Hi, I wonder what I might be doing wrong for \placelistofabbreviations
not to work in a project. Everything else about \definesysnonyms and
indeed the project is working, but I seem unable to place the list
correctly in the component that is intended to list all abbreviations.
The main
script.
https://github.com/Sandhi-IITBombay/Shobhika
The font also has a good Latin component based on PT Serif. This Latin part
has good support for the roman (IAST) transliteration for Sanskrit. But
strictly only the IAST spec character for Sanskrit are available.
It also has glyphs for some
tps://github.com/Sandhi-IITBombay/Shobhika
The font also has a good Latin component based on PT Serif. This Latin part
has good support for the roman (IAST) transliteration for Sanskrit. But
strictly only the IAST spec character for Sanskrit are available.
It also has glyphs for some commonly used mathemati
On Sat, 01 Jan 2022 09:48:53 +0530
kauśika wrote:
> On Friday, December 31, 2021 6:22:15 PM IST Ajith R via ntg-context
> wrote:
> > The conjuncts that are not formed
> > correctly are those where the second component is ര U+0D30,
> > followed by a symbol that is shown
On Friday, December 31, 2021 6:22:15 PM IST Ajith R via ntg-context wrote:
> The conjuncts that are not formed
> correctly are those where the second component is ര U+0D30, followed by
> a symbol that is shown on the right side of the conjunct viz ാ U+0D3E,
> ി U+0D3F, ീ U+0D40, ു
of conjuncts are not formed correctly, while
the rest are formed properly. The conjuncts that are not formed
correctly are those where the second component is ര U+0D30, followed by
a symbol that is shown on the right side of the conjunct viz ാ U+0D3E,
ി U+0D3F, ീ U+0D40, ു U+0D41, ൂ U+0D42. If no
Fabrice Couvreur via ntg-context schrieb am 28.12.2021 um 15:34:
Hi,
In my file cours_premiere.tex if I indicate
\startbodymatter
\component[probabilites.tex]
\stopbodymatter
I get the following error message
tex error > tex error on line 49 in file ./cours_premiere.
Hi,
In my file cours_premiere.tex if I indicate
\startbodymatter
\component[probabilites.tex]
\stopbodymatter
I get the following error message
tex error > tex error on line 49 in file ./cours_premiere.tex:
Undefined control sequence \pgfmath@settrigformat
\pgfm
been doing
years ago (but that book did not have parts and was done in mkii)
The modification of \chapter and \part setups with before= and after= never
worked in the \component setup in LMTX. Creating a separate command to run
immediately before a \chapter or \part, as suggested by Bruce, was
,
interaction=all,
alternative=c]
\stoptitle
\stopfrontmatter
\startbodymatter
\component[chapter_1]
\component[chapter_2]
\stopbodymatter
\stopproduct
##
tex
\startbodymatter
\component[chapter_1]
\component[chapter_2]
\stopbodymatter
\stopproduct
##
tex error > tex error on line 1 in file ./expertes.tex: Undefined
control sequence \undefi
) influences the pagebreaks in relation to inserts (footnotes)
in a more significant way than one would expect.
I also noticed that this stretch component is one of the reasons why
sometimes a side float shape will carry over to a next page in spite of
there being room. This relates to
% end project
Do you need a project file?
begin component
\project[terminale-environment]
\startcomponent[terminale_recurrence]
...
\endcomponent
end component
You ignored the order for \startcomponent and \project. The environment
(or project) file has to be loaded *after* \startcomp
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
.
Another approach would be:
[...]
Setting values for \title is a way to avoid the chapter setup for the
table of contents etc.
but there is a way to set values which are used only when you process a
component file.
To make it work one has to load the environment file after
\startcomponent
Joey McCollum via ntg-context schrieb am 07.08.2021 um 22:29:
Hi,
I'm interested in packaging a ConTeXt project in a self-contained way,
so that the environment/component/project .tex files, the bibliography
.bib file(s), and fonts used for typesetting are all provided in one
place.
> Am 07.08.2021 um 22:29 schrieb Joey McCollum via ntg-context
> :
>
> Hi,
>
> I'm interested in packaging a ConTeXt project in a self-contained way, so
> that the environment/component/project .tex files, the bibliography .bib
> file(s), and fonts used for ty
Hi,
I'm interested in packaging a ConTeXt project in a self-contained way, so
that the environment/component/project .tex files, the bibliography .bib
file(s), and fonts used for typesetting are all provided in one place. (The
goal is that others can generate the PDFs themselves from the s
to fit your own style.
1. File names
In the example all sub files (style + chapters) start with the
name of the main file and append a sub name. Another popular
naming scheme is to prefix the files with c_ (component),
p_ (product) or s_ (style/environment).
To avoid problems should also try to
component
Thanks. Maybe a change of how the wiki is worded is needed.
On 9 Jun 2021, at 12:07 PM, denis.ma...@unibe.ch<mailto:denis.ma...@unibe.ch>
wrote:
I’ve also struggled with this before as you can see if you search the mailing
list.
My question: https://www.mail-archive.com/ntg-c
d_ x
> Gesendet: Mittwoch, 9. Juni 2021 13:36
> An: ntg-context@ntg.nl
> Betreff: [NTG-context] Project structure: Specifying environment in component
>
> Hello everyone,
>
> I am creating a project of notes across different areas of mathematics I am
> studying and t
that no inheritance of
environments happens here.
Denis
Von: ntg-context Im Auftrag von mastermind_ x
Gesendet: Mittwoch, 9. Juni 2021 13:36
An: ntg-context@ntg.nl
Betreff: [NTG-context] Project structure: Specifying environment in component
Hello everyone,
I am creating a project of notes
://wiki.contextgarden.net/Project_structure
My question is: Why do I need to specify
\environment env_notes
before It works at the component level? The wiki didn’t say that. Plus it is
already specified at the product level. Thanks
Hi, Wolgang—
The mwe files in a product/component structure are attached.
Everything works as desired with the current env file.
If one comments out the startsetups...\stopsetups, the guillemets are not
properly spaced in the body text, while those in the footnote are fine.
If one comments out
Alan Bowen schrieb am 17.05.2021 um 21:50:
That is very good to know and it works in simple cases. But I am
finding that in a product/component structure, I get the
proper spacing only when
• the environment file has the \startsetups...\stopsetups
• either \setup[test] or \setuplanguage[fr
That is very good to know and it works in simple cases. But I am finding
that in a product/component structure, I get the proper spacing only when
• the environment file has the \startsetups...\stopsetups
• either \setup[test] or \setuplanguage[fr][setups=test] is in the
component file.
Is this
l file, YOUR CHANGES WILL BE LOST when it is
% updated. Instead, put your changes -- and only your changes, not an
% entire copy! -- in ../../texmf.cnf. That is, if this file is
% installed in /some/path/to/texlive/2020/texmf-dist/web2c/texmf.cnf,
% add your custom settings to /some/path/to/texlive
pbodyfont[schola,10pt]
\setupitaliccorrection [text]
What does it mean? Is there something I should do?
it's more for myself ... component lists done differently ... when you
nothing strange, just ig
rh...@t-online.de schrieb am 07.04.2021 um 20:20:
Hi list,
I typeset my first project with ConTeXt, a small booklet with some chapters,
frontmatter, no headers, but pagenumbers in the middle of the footers. I use
two environment files. The text is split into component TeX-files. All is
Hi list,
I typeset my first project with ConTeXt, a small booklet with some chapters,
frontmatter, no headers, but pagenumbers in the middle of the footers. I use
two environment files. The text is split into component TeX-files. All is
structured by a project and a product file.
Now I have
> and components. (OTOH, with components I probably wouldn't have noticed that
> things go off the rails here as \component doesn't complain about missing
> files...)
You’re right, that’s a common trap. Got me recently when I typeset a novel and
missed one chapter (component) bec
ngly suggest to use the project structure (environment,
> products, components) in such cases, but that doesn’t change this.
I use environments, but in that particular case there's no need for products
and components. (OTOH, with components I probably wouldn't have noticed that
things
Finally coming back to this.
> Am 31.01.2021 um 07:39 schrieb Aditya Mahajan :
>
>> I’m not yet sure what would make the most sense for this project (at least
>> sorting by chapter/component would), but I have an use case with LilyPond
>> where I could save several Li
t000
\project testproject
\startbodymatter
\component boo.tex
\stopbodymatter
\stopproduct
% master001.tex -- LMTX 2021.03.02
\startproduct testproduct001
\project testproject
\startbodymatter
\component foo.tex
\stopbodymatter
\stopproduct
% boo.tex -- LMTX 2021.03.02
\startcomponent
What exactly do you need? You can just process each component on its own. With
a makefile or shell script, batch file, that should be easy enough.
Or, do you need to have correct cross references, page numbers, etc.? I was
asking a similar question two days ago, and Hans showed me how to add
I have a project-component setup and need to produce a single PDF file
containing all the components as well as a PDF file for each component. The
single file is easy. Is there a way to automate the generation of the PDF
files for the individual components?
Alan
denis.ma...@ub.unibe.ch schrieb am 28.02.2021 um 23:09:
Hi,
I’m just having a look a project structure again. I am using the example
given in the wiki: https://wiki.contextgarden.net/Project_structure,
i.e., in my component I’m linking to the product, but not to the
project. Now I was
denis.ma...@ub.unibe.ch schrieb am 01.03.2021 um 17:54:
Hi,
another question regarding project structure. I want to put each
chapter of a book in a component or a distinct file loaded with
\input, but I don’t want to have a full project structure. Just a main
file and the chapters
On 3/1/2021 5:54 PM, denis.ma...@ub.unibe.ch wrote:
Hi,
another question regarding project structure. I want to put each chapter
of a book in a component or a distinct file loaded with \input, but I
don’t want to have a full project structure. Just a main file and the
chapters. Nevertheless
Hi,
another question regarding project structure. I want to put each chapter of a
book in a component or a distinct file loaded with \input, but I don't want to
have a full project structure. Just a main file and the chapters. Nevertheless,
I want to load the environment file in each su
Hi,
I'm just having a look a project structure again. I am using the example given
in the wiki: https://wiki.contextgarden.net/Project_structure, i.e., in my
component I'm linking to the product, but not to the project. Now I was
expecting that the component inherits the environment
or compose a song, it’s much
easier and faster to work in Frescobaldi and compile only LilyPond. If it’s
complete, I copy the melody into a ConTeXt component – not a perfekt workflow.
> I always used full-page scores, so I didn't really need support for short
> snippets either.
ere because at some point context used to delete \jobname-temp-.tmp files
if you passed the --purge option, but I see that it is no longer the case.
Maybe that can be removed from the default name. The last part are the numbers,
which are needed when caching results.
> I’m not yet sure what
ething like "COMPONENTNAME-##-example.tmp" or a path like
>> "COMPONENTNAME/example_##.tmp".
>> Is there a configuration hook in the module to change name generation?
>
> No. I don't quite understand the concern. How do you plan to use a
> `name=value
ut routine.
> It’s about a project with hundreds of diagrams that (in the current state)
> clutter the main directory with cryptically-named PDFs (at least sorted by
> component name) and that on each ConTeXt run take a lot of runtime (I guess
> also the many log lines slow the process
On 1/25/2021 4:42 PM, Henning Hraban Ramm wrote:
Hi,
did anyone succeed in externalizing TikZ graphics with ConTeXt?
It’s about a project with hundreds of diagrams that (in the current state)
clutter the main directory with cryptically-named PDFs (at least sorted by
component name) and that
Hi,
did anyone succeed in externalizing TikZ graphics with ConTeXt?
It’s about a project with hundreds of diagrams that (in the current state)
clutter the main directory with cryptically-named PDFs (at least sorted by
component name) and that on each ConTeXt run take a lot of runtime (I guess
Another LMTX/MkIV difference:
In a component, I include another file with \input, that starts with \page in
the first line.
With LMTX I get an error:
"""
I can't figure out why you would want to use a tab mark here. If some right
brace
up above has ended a previous a
On 12/4/2020 9:06 PM, Pablo Rodriguez wrote:
Hi Hans,
many thanks for your new upload that fixes the issue with scaled
external figures.
I have just accidentally realized:
\startbodymatter
\component luametatex-preamble
\component luametatex-differences
Hi Hans,
many thanks for your new upload that fixes the issue with scaled
external figures.
I have just accidentally realized:
\startbodymatter
\component luametatex-preamble
\component luametatex-differences
[...]
\stopbodymatter
\startbackmatter
;>
>>>> Thanks Tomás! Indeed \jobname does the job :-)
>>> In case you need the current component file in a project environment:
>>> \currentcomponent
>
> In some case \inputfilename is the better choice, e.g. when you process xml
> files with a
16:20 schrieb Otared Kavian :
Thanks Tomás! Indeed \jobname does the job :-)
In case you need the current component file in a project environment:
\currentcomponent
In some case \inputfilename is the better choice, e.g. when you process
xml files with a environment file for the style and proce
Kavian :
>>
>> Thanks Tomás! Indeed \jobname does the job :-)
>
> In case you need the current component file in a project environment:
> \currentcomponent
>
> Hraban
> ___
> If your
> Am 01.12.2020 um 16:20 schrieb Otared Kavian :
>
> Thanks Tomás! Indeed \jobname does the job :-)
In case you need the current component file in a project environment:
\currentcomponent
Hraban
__
r}
>
> You can have a filename with a space use
>
>\startproduct [foo bar]
>
> but you don't even need the filename when you replace it with *, e.g.
>
>\startproduct *
>
> or
>
>\startproduct [*]
Since I learned about *, I used it exte
Jairo :)
>
Hi Jairo,
Thank you very much for the suggestion and the thorough explanation.
I extracted the metapost code to a new file because I felt it would be a
bit lengthy and noisy to stay with the text content.
But you're right, an extra compilation step is not any better. I should
p
Aditya Mahajan schrieb am 24.09.2020 um 23:48:
On Thu, 24 Sep 2020, Alan Bowen wrote:
I need to include several documents in a single paginated file. Treating
the source file (.tex) of each document as a component file in a .prd file
is one way to go. But I was wondering if it might be
On Thu, 24 Sep 2020, Alan Bowen wrote:
> I need to include several documents in a single paginated file. Treating
> the source file (.tex) of each document as a component file in a .prd file
> is one way to go. But I was wondering if it might be possible to do get the
> same result us
I need to include several documents in a single paginated file. Treating
the source file (.tex) of each document as a component file in a .prd file
is one way to go. But I was wondering if it might be possible to do get the
same result using the .pdf files of each document instead.
\copypages is
hould be able to copy and adapt to your needs. There are lot of things which can be improved in your example. 1. Pass the filename of the component/product to \startcomponent and not some dummy name (or just use *), this allows you to print the filename with \currentcomponent or \currentproduct 2.
filename of the component/product to \startcomponent and not
some dummy name (or just use *), this allows you to print the filename
with \currentcomponent or \currentproduct
2. Use \setvariables or \setupdocument to set the document title,
revision etc.
3. Use \startsectionblockenvironment to move
frontmatter \component fm-frontpage \component fm-titlepage \component fm-tableofcontents\stopfrontmatter % Load bodymatter file\startbodymatter\setupbackgrounds [leftpage] [setups=pagenumber:left]\setupbackgrounds [rightpage] [setups=pagenumber:right]\setuppagenumber[number=1]
efine\MySubtitleTwo{Subtitle 2}
\define\MyRevnumber{Revision number}
% Load frontmatter files
\startfrontmatter
\component fm-frontpage
\component fm-titlepage
\component fm-tableofcontents
\stopfrontmatter
% Load bodymatter file
\startbodymatter
\setupbackgrounds
[leftpage]
[setups=pagenumber
\MyManual{Course Manual}\define\MyTitle{Title}\define\MySubtitleOne{Subtitle 1}\define\MySubtitleTwo{Subtitle 2}\define\MyRevnumber{Revision number} % Load frontmatter files\startfrontmatter \component fm-frontpage \component fm-titlepage \component fm-tableofcontents\stopfrontmatter % Load
Hi,
I'm having an issue where \doublehyphendemerits=2 doesn't seem to have
an effect when I put it in the environment file, only when it's in the
component file. What's going on? I would prefer to not have to repeat this
line in every component..
T
ixes can
> be useful (e.g. to avoid component and style files with the same name) but
> aren't necessary.
Usually my project and environment have the same name, but different prefix (in
my weird nomenclature).
>>> 2. Use the result option on the command line, e.g. "context
for your
>>> product.
>> I force nobody to use that.
> No and everybody has to find a system which fits best for him, prefixes can
> be useful (e.g. to avoid component and style files with the same name) but
> aren't necessary.
>>> 2. Use the res
myfilename for your
product.
I force nobody to use that.
No and everybody has to find a system which fits best for him, prefixes
can be useful (e.g. to avoid component and style files with the same
name) but aren't necessary.
2. Use the result option on the command line, e.g. "contex
Denis Maier schrieb am 08.05.2020 um 11:49:
Hi
Am 07.05.2020 um 16:01 schrieb Aditya Mahajan:
On Thu, 7 May 2020, Fabrice Couvreur wrote:
context chapter-4-seconde
There is a MyWay which shows how you can share cross-refs etc.
Aditya
Where is that? I would be very interested in learning ab
1 - 100 of 934 matches
Mail list logo
