th the info you have given me! I have
difficulty understanding your comment 'This is not interfaced via
setuphead *or* setuplangauge *or* because the converter is not
configured that way'. The 'or' throws me out, I'm afraid. Were you
going to suggest somewhere el
On 2/11/2021 9:20 AM, jbf wrote:
I appreciate the response.
However, you are light years ahead of me in understanding ConTeXt, so I
don't quite know what to do with the info you have given me! I have
difficulty understanding your comment 'This is not interfaced via
set
I appreciate the response.
However, you are light years ahead of me in understanding ConTeXt, so I
don't quite know what to do with the info you have given me! I have
difficulty understanding your comment 'This is not interfaced via
setuphead *or* setuplangauge *or* because the co
On 1/14/2021 10:44 AM, Henning Hraban Ramm wrote:
Hi again,
the following example used to work with LMTX (but not MkIV) from September.
Now I get the "narrower" indentation only if I comment the first line (in both
versions) – apparently there’s a setup conflict, and I don’t know an
> Am 14.01.2021 um 10:44 schrieb Henning Hraban Ramm :
>
> Hi again,
> the following example used to work with LMTX (but not MkIV) from September.
>
> Now I get the "narrower" indentation only if I comment the first line (in
> both versions) – apparently there’
Hi again,
the following example used to work with LMTX (but not MkIV) from September.
Now I get the "narrower" indentation only if I comment the first line (in both
versions) – apparently there’s a setup conflict, and I don’t know any more why
I needed this setup.
Could you expla
You would set DIGESTIF_TEXMF to the (list of) directory(ies) containing
the ls-R file(s).
However, I gather from Hans's comment that lmtx does not have the ls-R
files. So something lmtx-specific has to be added to Digestif.
Best,
Augusto
On Sun, Jan 3, 2021 at 11:21, Saša Janiška
On Sat, Dec 26, 2020 at 10:54 AM Hans Hagen wrote:
> On 12/25/2020 9:47 PM, Christoph Reller wrote:
> > Hi,
> >
> > Consider the following MWE:
> >
> > \definefloat[combination][figure]
> > \setupcaptions[
> >number=no, %<- comment and table
On 12/25/2020 9:47 PM, Christoph Reller wrote:
Hi,
Consider the following MWE:
\definefloat[combination][figure]
\setupcaptions[
number=no, %<- comment and table appears
align=flushright]
\starttext
\startplacecombination[title=Combination]
\startfloatcombination
\startplaceta
Hi,
Consider the following MWE:
\definefloat[combination][figure]
\setupcaptions[
number=no, %<- comment and table appears
align=flushright]
\starttext
\startplacecombination[title=Combination]
\startfloatcombination
\startplacetable%[title=Table] %<- uncomment and table a
Hi,
I finally decided to start an experiment that I had on my todo list for
a while: dynamically scaling fonts. Below is an example of usage (plus
some comment). In that example some 2*200 different font sizes are used
which in mkiv demands 400 font definitions. This costs time and memory
Nice. It works again. Thank you very much!
Cordially,
Jairo
El lun., 21 de dic. de 2020 2:45 a. m., Hans Hagen
escribió:
> On 12/21/2020 4:46 AM, Jairo A. del Rio wrote:
> > While shading works with MkIV, with LMTX the following breaks:
> >
> >
> > \startMPpage
On 12/21/2020 4:46 AM, Jairo A. del Rio wrote:
While shading works with MkIV, with LMTX the following breaks:
\startMPpage
comment("two shades with named colors");
fill fullcircle scaled 5cm
withshademethod "circular"
withshadecolors ((1,0,0),(0,0,1,0))
;
fill f
While shading works with MkIV, with LMTX the following breaks:
\startMPpage
comment("two shades with named colors");
fill fullcircle scaled 5cm
withshademethod "circular"
withshadecolors ((1,0,0),(0,0,1,0))
;
fill fullcircle scaled 5cm shifted (6cm,0)
withshademethod &
ra
> code but to be honest, no one ever came up with a project that had
> any real demands on the engine that could not be met (the fact that
> tex is a good solution for rendering doesn't mean that there is
> demand for it ... it is seldom on the radar of those who deal with
>
ssor. Which will cost a lot, and use a lot of
> > power which has to be cooled, which uses even more power
>
> Startup time can be improved quite a bit with an SSD. Even a cheap
> SATA SSD is already much faster than a traditional harddisk. Doesn’t
> help with longer docume
quality doesn't really matter)
these kind of performance things are demand driven (read: i need a
pretty good reason to spend time on it)
I can’t comment on how to speed up the rest of what you are doing,
but generally multi-threading TeX typesetting jobs is so hard as to
be impossible in practi
a cheap SATA
SSD is already much faster than a traditional harddisk. Doesn’t help
with longer documents, but it could be a fairly cheap upgrade.
I can’t comment on how to speed up the rest of what you are doing,
but generally multi-threading TeX typesetting jobs is so hard as to
be impossible in pr
approach.
> >
> > The principle problem is, as you suggested below, "stopping" the
> > pipeline at the PDF stage (using for example the
> > `pre_output_filter`) corrupted the `*.tuc` data which is for my
> > purposes, critical.
> >
> > Your
I do need to implement it in ANSI-C wrapped in Lua (so that
> > it can be used from *inside* ConTeXt).
>
> I would have to see the 'kind of code involved' in order to comment
> on that.
>
> An option is to do most in lua and maybe some helpers for crititical
> code in
eXt).
I would have to see the 'kind of code involved' in order to comment on
that.
An option is to do most in lua and maybe some helpers for crititical
code in C.
Hans
-
overall
is not really significant enough to bother with this approach.
The principle problem is, as you suggested below, "stopping" the
pipeline at the PDF stage (using for example the `pre_output_filter`)
corrupted the `*.tuc` data which is for my purposes, critical.
Your comment was:
b
to bother with this approach.
The principle problem is, as you suggested below, "stopping" the
pipeline at the PDF stage (using for example the `pre_output_filter`)
corrupted the `*.tuc` data which is for my purposes, critical.
Your comment was:
> but keep in mind that multipass da
-implementation}\\
\hyphenatedword{reimplementation}
\stopTEXpage
\stoptext
If you comment the first line, only "||" allows hyphenation.
Another option is to add \setbreakpoints[compound] to the document.
Wolfgang
___
{reimplementation}
\stopTEXpage
\stoptext
If you comment the first line, only "||" allows hyphenation.
I hope it helps,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please
apport_maitriser-l-empreinte-carbone-de-la-france.pdf
>
> Any feedback is welcome (even if source code is not really clean)
Congratulations, Garulfo.
It’s a really good work.
Just a comment, to get clean bookmarks and PDF info, use:
\enabledirectives[references.bookmarks.prer
pictures for ConTeXt Wiki
filename
reference
owner
comment
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
problem is
different, but I couldn’t reproduce it in a MWE. I guess the interference of
different note types is the cause of both problems.
I tried using the same custom note for the last comment as a workaround, but it
gets placed twice: once at the bottom of the current page (i.e. like a normal
ce TeXpage with a
> "page"
> >> layout.
> >>
> >> \startlayout[page]
> >> \dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
> >> \stoplayout
> >
> > Thanks for the comment (also I didn't know about \startl
/context-blog/post/include-multi-page-pdf/
When both document have the same size you can replace TeXpage with a "page"
layout.
\startlayout[page]
\dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
\stoplayout
Thanks for the comment (also I didn't know abo
ttps://adityam.github.io/context-blog/post/include-multi-page-pdf/
>
> When both document have the same size you can replace TeXpage with a "page"
> layout.
>
> \startlayout[page]
> \dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
> \stoplayout
Tha
TeX Gyre Pagella Math]
\setupbodyfont[mainface]
-
ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that
the ss typeface is available. So if, for example, I comment out the
first line ([rm]) and change the Libris to rm instead, I am told:
mkiv lua stats >
--
>
> ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that
> the ss typeface is available. So if, for example, I comment out the
> first line ([rm]) and change the Libris to rm instead, I am told:
>
> mkiv lua stats > loaded fonts: 2 files: librisadfstd-re
for example, I comment out the
first line ([rm]) and change the Libris to rm instead, I am told:
mkiv lua stats > loaded fonts: 2 files: librisadfstd-regular.otf,
texgyrepagella-math.otf
In other words, only two, not three definitions are working at any one
time. Or is it not accepting [s
-module-basic.mkiv)
which is used to create the formatted source.
The same has to be done to disable the frame where you have to comment
the \showframe line in the module mentioned above.
Wolfgang
___
If your question
on fault".
> I append the console outputs of the context runs.
>
> If i comment out the input of luametafun-axis and luametafun-followtext
> i get a readeable pdf.
>
> So perhaps only the code is changing too rapidly.
>
> Greetings Lutz
>
> Am 14. August 2020
uns.
If i comment out the input of luametafun-axis and luametafun-followtext
i get a readeable pdf.
So perhaps only the code is changing too rapidly.
i found the issue ... i switched to a more efficient method of piping a
path back to mp
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux aarch64
i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i comment out the input of luametafu
\setfirstline is
not applied at all, i.e., there are no small caps. If I comment out the
first \setfirstline, then the second one does produce small caps, but
again, a whole paragraph is set in small caps, not just the first line.
$ context --version
mtx-context | ConTeXt Process Management 1.03
mtx
the main body for 'chapters' that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or wh
#x27; that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or whatever the page number is.
Is ther
> The luatools script was there to offer some kpse like functionality but it
> has been obsolete for ages (the generate was in mtx-base at that time). Just
> use
>
> mtxrun --generate
Should the comment in the engine file change?
Context is called with:
mtxrun -
ore thing:
Please look at environment variables starting with TEX and comment them, they
will cause problems.
And another one:
Please look into the home directory for a local .texlive2020 folder.
There shouldn’t be any and it shouldn’t co
On 8/9/20 9:59 PM, Joseph Canedo wrote:
> Hi Pablo,
> I've reported similar issue to Hans 2 days ago, from my checks he fixed
> it in LMTX version 2020.08.07 23:37. I have not downloaded more recent
> version yet.
> Hoping it helps
Hi Joseph,
many thanks for your comment and
whole example below.
Best regards: Otared
%%% sidenotes, or footnotes in the margin
%%% example given by Hraban:
%%% here the tweaking of the width of the sidenote is turned off
%%% remove the comment where there is \ColWidth
%%% in order to adapt to your layout
\showframe
\setuplayout
[cut
On Fri, 3 Jul 2020 08:40:22 +0200
Fabrice Couvreur wrote:
> Thanks, it works but only for a comment and a picture. Indeed, if I
> add a comment and an image, the first image is placed on the second
> comment. Fabrice
>
> \starttext
> \startuserdata[margintext]
> \input
Hi Marco,
Thanks, it works but only for a comment and a picture. Indeed, if I add a
comment and an image, the first image is placed on the second comment.
Fabrice
\starttext
\startuserdata[margintext]
\input ward
\stopuserdata
\marginfigure{\externalfigure[dummy][width=\rightmarginwidth,location
hit-or-miss, but in this case there are quite a few hits. Just
watch out (in much older messages) that you're not fully relying
on an answer based on ConTeXt Mk II, because many of those
solutions no longer work in the newer versions.
... which has accidentally led me to another document
Jan-Erik Hägglöf schrieb am 24.06.2020 um 21:05:
Hello All!
In the page https://wiki.contextgarden.net/Labels
I’ve tried with no success to run those examples given at the page. The
error complaint as the log shows below
Can you comment (or remove) the following two lines which load the IBM
On 6/24/2020 7:59 PM, Wolfgang Schuster wrote:
Hans Hagen schrieb am 24.06.2020 um 19:06:
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment
symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
Hans Hagen schrieb am 24.06.2020 um 19:06:
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment
symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type
n mind when you
> start with something like context:
>
> - you often bring with your experience (and exposure) to different
> systems and these don't translate; recently i was playing with some css
> setup for a rather complex xml -> html mapping and things that would
> have tak
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type{%%}}
\stoptext
It's actually a feature: in asc
Hi,
when asciimode is enabled the \type command ignores double comment symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type{%%}}
\stoptext
Wolfgang
On 6/17/20 11:26 PM, Henning Hraban Ramm wrote:
> [...]
> Pablo, do I understand right that you’re converting XML and the
> comment comes last in that structure, but you need it first?> I.e.
> the real question is how to process the XML structure in a different
> order, right?
\setupinterlinespace[1sp]
>>\stopsetups
This was from a previous form of the sample. If the paragraph is really
tiny, it would be easier not to have a page break between that paragraph
and the
>>\setupinteraction[state=start]
>>\showframe\showgrid
>>\sta
; \setupinterlinespace[1sp]
>> \stopsetups
>
> ???
>
>> \setupinteraction[state=start]
>> \showframe\showgrid
>> \starttext
>> \blank[force, 10em]
>> \section{Move comment above this heading}
>> \startparagraph[setups=tinytiny]
\blank[force, 10em]
\section{Move comment above this heading}
\startparagraph[setups=tinytiny]
\dontleavehmode
\comment[location={rightmargin}, color=orange]
{comment}
\stopparagraph
\stoptext
Is there a way to move the comment above the heading that
Dear list,
I have the following sample:
\startsetups[tinytiny]
\setupwhitespace[-2em]
\setupbodyfont[0.01pt]
\setupinterlinespace[1sp]
\stopsetups
\setupinteraction[state=start]
\showframe\showgrid
\starttext
\blank[force, 10em]
\section{Move comment above this
On 6/16/20 8:00 PM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 16.06.2020 um 19:20:
>> [...]
>> I think it might be a bug. Could anyone confirm this?
>
> Why is everything a bug?
>
> Some elements like margin blocks or register entries need an anchor.
Sorry, Wolfgang, I discovered after
Pablo Rodriguez schrieb am 16.06.2020 um 19:20:
Dear list,
when trying to report another issue, I found the following one (using
latest from 2020.06.12 17:43):
\setupinteraction[state=start]
\starttext
a\contextversion
\comment[location={rightmargin}]{comment}
\stoptext
need another approach. This sample reflects my problem:
\setupinteraction[state=start]
%~ \showframe\showgrid
\starttext
\dorecurse{41}{one line\par}
\ \comment[location={rightmargin}]{comment}
\stoptext
Since layers are problematic for the task, I insert the comments right
after the
ument.
I need another approach. This sample reflects my problem:
\setupinteraction[state=start]
%~ \showframe\showgrid
\starttext
\dorecurse{41}{one line\par}
\ \comment[location={rightmargin}]{comment}
\stoptext
Since layers are problematic for the task, I insert the comments rig
Dear list,
when trying to report another issue, I found the following one (using
latest from 2020.06.12 17:43):
\setupinteraction[state=start]
\starttext
a\contextversion
\comment[location={rightmargin}]{comment}
\stoptext
For some strange reason, \comment isn’t added when there
> \setupbackgrounds[page][background=pgnumber]
> \starttext
> \placelist[section][alternative=d]
> \dorecurse{16}{\section{Section}}
> \pagenumber/\lastpagenumber
> \setlayer[pgnumber]
> {\comment{\pagenumber}}
> \stoptext
>
> Could anyone confirm the iss
]
\starttext
\placelist[section][alternative=d]
\dorecurse{16}{\section{Section}}
\pagenumber/\lastpagenumber
\setlayer[pgnumber]
{\comment{\pagenumber}}
\stoptext
Could anyone confirm the issue?
\pagenumber is only reliable headers/footer texts or page backgrounds,
for
]
\dorecurse{16}{\section{Section}}
\pagenumber/\lastpagenumber
\setlayer[pgnumber]
{\comment{\pagenumber}}
\stoptext
Could anyone confirm the issue?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If
utput of
os.execute("locale") from context is different from that from my shell. But I
don't know why locale should affect UTF characters in R. Perhaps someone with more
knowledge of R can comment on that.
\starttext
\startluacode
lfs.mkdir("output/")
\s
would need to recompile the document again for each new required
/PrintPageRange.
Another approach would be to add PDF annotations (outside page
boundaries) to store the desired information.
So I created text annotations (using \comment) with author information
composed from unit number (such as
: \hideblocks[NLblok]%\hideblocks[ENblok] For the titles I use another method: %\def\NL#1{#1}\def\NL#1{{}}%\def\EN#1{}\def\EN#1{#1} You have to comment and uncomment, depending on the language, but I think you can put them in the NLblok or ENbloks instead. \definecomplexenumeration[Casus]… definition
comment and uncomment, depending on the language, but I think you
can put them in the NLblok or ENbloks instead.
\definecomplexenumeration[Casus]
… definition
\def\refno#1{{\em{(no. \small #1})}}
My files look like this:
\starttext
\startCasus[casus-349][\NL{Een moeilijke zaak}\EN{A complicated case
e.
>
>
> Index statistics:
>
> 4085 files processed, 178 skipped, 3744 with matches
> 120733 words found
> 119154 words exported to word.idx
> 37928 comment words found
> 36880 words exported to
sList{>>> \page[yes] \stopmode>>> }>>> \definestartstop[Questions][>>> before=\StartQuestionsList,>>> after=\StopQuestionsList>>> ]>>> >>> >>> \startQuestions>>> Question A….>>> Question B….>>> \stopQues
;>> \page[yes] \stopmode
>>>> }
>>>> \definestartstop[Questions][
>>>> before=\StartQuestionsList,
>>>> after=\StopQuestionsList
>>>> ]
>>>>
>>>>
>>>> \startQuestions
>>>> Question A….
>>>> Question B….
>>
ons
Question A….
Question B….
\stopQuestions
Some other text...
%
One of the oldest mechanism available ... blocks:
\enablemode[classroom] % comment this
\defineblock[Question]
\doifmode {classroom} {
\keepblocks[Question]
}
\starttext
Text A
stics:
4085 files processed, 178 skipped, 3744 with matches
120733 words found
119154 words exported to word.idx
37928 comment words found
36880 words exported to comment.idx
26756 documentation words found
26018 words exported to docs.idx
The word.idx is roughly 11 megabytes.
Have fun,
On Sat, 16 May 2020, Aditya Mahajan wrote:
On Sat, 16 May 2020, Nicola wrote:
On 2020-05-16, Aditya Mahajan wrote:
On Sat, 16 May 2020, Aditya Mahajan wrote:
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
[If you make a local co
On Sat, 16 May 2020, Nicola wrote:
On 2020-05-16, Aditya Mahajan wrote:
On Sat, 16 May 2020, Aditya Mahajan wrote:
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
[If you make a local copy of 2context.vim, then you need to run the
On 2020-05-16, Aditya Mahajan wrote:
> On Sat, 16 May 2020, Aditya Mahajan wrote:
> Moreover, if you comment line line 126 of `2context.vim`
>
> "let s:id = synIDtrans (s:id)
>
> [If you make a local copy of 2context.vim, then you need to run the
> file with
yntax
highlighting element, which in this case is `Function`. So, there is no tag
generated for `rubyMethodName` and that is why changing the syntaxhighlight
for that doesn't change anything.
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
:= (0.0*cm,19.935*cm);
for xord = 0 step 0.1 until 25:
show xord;
fails at xord = 13.5%
yord := ((-0.000268117) * pow(xord,4)) +(0.0136949 * pow(xord, 3)) +
((-0.16608) * sqr(xord)) + ((-0.771743) * xord) + 19.935;
%%%%%comment out above and uncomment below and it works%%%
quare scaled .1cm ;
path pat;
pat := (0.0*cm,19.935*cm);
for xord = 0 step 0.1 until 25:
show xord;
fails at xord = 13.5%
yord := ((-0.000268117) * pow(xord,4)) +(0.0136949 * pow(xord, 3)) +
((-0.16608) * sqr(xord)) + ((-0.771743) * xord) + 19.935;
%comment out abov
\definecolor[nearlywhite] [r=0.988, g=0.988, b=0.988]
\setupinteraction[state=start]
\setupcolors[textcolor=colorone]
\setupbackgrounds[page][background=color,backgroundcolor=nearlywhite]
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c
\hskip 1em
>> \vtop{\hsize\dimexpr\textwidth-3em\relax#2}
>> \egroup \par}
>>
>> % Comment out this next line to regain section hyperlinks in the ToC
>> \setuplist[section][alternative=command,command=\SectionListEntry]
>
> alternative
[option=bookmark]
\define[3]\SectionListEntry
{\par \leftaligned\bgroup
\hbox to 2em{#3}%
\hskip 1em
\vtop{\hsize\dimexpr\textwidth-3em\relax#2}
\egroup \par}
% Comment out this next line to regain section hyperlinks in the ToC
\setuplist[section][alternative
etupinteraction[state=start]
> \setupinteractionscreen[option=bookmark]
>
> \define[3]\SectionListEntry
> {\par \leftaligned\bgroup
> \hbox to 2em{#3}%
> \hskip 1em
> \vtop{\hsize\dimexpr\textwidth-3em\relax#2}
> \egroup \par}
>
> % Comment o
{\par \leftaligned\bgroup
\hbox to 2em{#3}%
\hskip 1em
\vtop{\hsize\dimexpr\textwidth-3em\relax#2}
\egroup \par}
% Comment out this next line to regain section hyperlinks in the ToC
\setuplist[section][alternative=command,command=\SectionListEntry]
\starttext
Table of
On Thu, 14 May 2020, Nicola wrote:
Quick question: Is \startcolorscheme... \stopcolorscheme (still)
supported by t-vim?
In a template I wrote long time ago to typeset code, I have:
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color
Quick question: Is \startcolorscheme... \stopcolorscheme (still)
supported by t-vim?
In a template I wrote long time ago to typeset code, I have:
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color={colortwo},\c!style=italic
local c1, c2 = string.find(xml, "", c2 + 1, true)
if c3 then
-- Remove comment.
xml = string.sub(xml, 1, c1 - 1) .. string.sub(xml, c4
+ 1, -1)
-- Search for next comment.
c1, c2 = string.find(xml, "
quot;]=true,
["pdftex"]=true,
["xetex"]=true,
},
["formats"]={
["cont-en"]=true,
["cont-nl"]=true,
["metafun"]=true,
},
["info"]={
["comment"]="this file contains the settings of the last 'mtxrun
They are just an option. The tilde (~) is added after the percent sign
(%), because “Geany” (the text editor I use) adds it after the comment
sign in different programming languages. It has no special meaning.
> What I try to do is to have english as the default (and fallback)
> language and
an entire issue of the journal in one go. (I
would simply comment out the \input line and add \startproject \startcomponent
etc lines as necessary from each received article.)
Problem:
I've created a custom chapter heading, but the font size changes depending on
whether I'm processin
uld simply comment out the \input line and add \startproject \startcomponent
etc lines as necessary from each received article.)
Problem:
I've created a custom chapter heading, but the font size changes depending on
whether I'm processing the \input version of the article or the \comp
d
> % !TEX root=../prd_\mystring.tex
Processing single components won’t work in your project, since I defined
several metadata macros in the product. More off list.
> with, e.g., \def\mystring{Name01} in the prd_Name01.tex file, but that does
> not seem to work—the various .tex files re not foun
\marking[TestMark]{4}(4) \input knuth\par
> > \marking[TestMark]{5}(5) \input knuth\par
> > \marking[TestMark]{6}(6) \input knuth\par
> > \marking[TestMark]{7}(7) \input knuth\par
> > \marking[TestMark]{8}(8) \input knuth\par
> > \stoppagecolumns
&
eased with
TeXLive 2020. As my comment in the MWE points out, there also seems to
be a bug in the key-value parsing of \definepagecolumns that causes it
not to parse the direction=reverse input unless it is followed by a comma.
Is there some way I can improve my syntax to avoid this issue, or
h\par
\marking[TestMark]{6}(6) \input knuth\par
\marking[TestMark]{7}(7) \input knuth\par
\marking[TestMark]{8}(8) \input knuth\par
\stoppagecolumns
\stoptext
```
I typeset this using ConTeXt version 2020.03.10, as released with TeXLive
2020. As my comment in the MWE points out, there
ot generate a perfect ConTeXt
source to build the file as some things are missing.
Annotations and eg. your classify.lua might be a second approach to
achieve what I want.
So thanks a lot for your work.
@all: Feel free to com
mplex. And this would be
the best way to scare newcomers.
If you aren’t scared, t-handlecsv.lua contains a complete list of
defined commands (as a huge comment near the end of the file). You might
be interested in reading them.
Or feel free to ask here for help, if you don’t find the command, it
301 - 400 of 2361 matches
Mail list logo
