Am 20.12.22 um 19:44 schrieb Pawel Urbanski via ntg-context:
Dear Friends,
I spent some time searching and coding simple documents, but failed and
therefore I'm asking for help...
A section such as chapter cn have custom keys with values. One uses the:
\structureuservariable command to a
Dear Friends,
I spent some time searching and coding simple documents, but failed and
therefore I'm asking for help...
A section such as chapter cn have custom keys with values. One uses the:
\structureuservariable command to access such values.
How can I use such a value to create a custom h
On 12/6/2022 6:33 PM, Pablo Rodriguez via ntg-context wrote:
On 12/6/22 09:05, Hans Hagen via ntg-context wrote:
On 12/6/2022 1:39 AM, Joel wrote:
Thanks so much! It took some work for me to figure out how to make it
work, but it now works great!
i added \firstsectionpage and \lastsectionpage
On 12/6/22 09:05, Hans Hagen via ntg-context wrote:
> On 12/6/2022 1:39 AM, Joel wrote:
>> Thanks so much! It took some work for me to figure out how to make it
>> work, but it now works great!
> i added \firstsectionpage and \lastsectionpage that (i guess) Pablo will
> document at the wiki
Many
On 12/6/2022 1:39 AM, Joel wrote:
Thanks so much! It took some work for me to figure out how to make it
work, but it now works great!
i added \firstsectionpage and \lastsectionpage that (i guess) Pablo will
document at the wiki
Hans
---
rom a PDF:
>
> \externalfigure[filename.pdf][page=5]
>
> I am making a teacher's guide for a workbook (workbook.pdf). I need to
> be able to display on the page all pages of a particular section.
>
> The teacher's guide uses the same section titles as the workb
... we're talking about a rather special
application, so what I can add is a simple helper that returns the first
and last page of a section
That would be great for me.
keep in mind that it is also a biut fragile as one never know where the
last one ends
I wondered whether \doifrefe
ing about a rather special
> application, so what I can add is a simple helper that returns the first
> and last page of a section
That would be great for me.
> keep in mind that it is also a biut fragile as one never know where the
> last one ends
I wondered whether \doifreferenc
On 12/5/2022 5:39 PM, Pablo Rodriguez via ntg-context wrote:
On 12/5/22 13:13, Hans Hagen via ntg-context wrote:
On 12/4/2022 11:30 PM, Joel via ntg-context wrote:
I can use this code to display page 5 from a PDF:
[...]
\externalfigure[filename.pdf][section=17A]
prototype attached (first
On 12/5/22 13:13, Hans Hagen via ntg-context wrote:
> On 12/4/2022 11:30 PM, Joel via ntg-context wrote:
>> I can use this code to display page 5 from a PDF:
>> [...]
>> \externalfigure[filename.pdf][section=17A]
>
> prototype attached (first process crap, then load)
On 12/4/2022 11:30 PM, Joel via ntg-context wrote:
I can use this code to display page 5 from a PDF:
\externalfigure[filename.pdf][page=5]
I am making a teacher's guide for a workbook (workbook.pdf). I need to
be able to display on the page all pages of a particular section.
The teac
Am 04.12.22 um 23:30 schrieb Joel via ntg-context:
I can use this code to display page 5 from a PDF:
\externalfigure[filename.pdf][page=5]
I am making a teacher's guide for a workbook (workbook.pdf). I need to
be able to display on the page all pages of a particular section.
The teac
Don’t know about ConTeXt. But maybe you might want to have a look at pdftk. You
could try to produce per-section pdfs and include those.
Best,
Denis
Von: ntg-context Im Auftrag von Joel via
ntg-context
Gesendet: Sonntag, 4. Dezember 2022 23:31
An: Mailing List for ConTeXt Users
Cc: Joel
I can use this code to display page 5 from a
PDF:\externalfigure[filename.pdf][page=5]I am making a teacher's guide for a
workbook (workbook.pdf). I need to be able to display on the page all pages of
a particular section.
The teacher's guide uses the same section titles as the wor
]
\setupbodyfont[mainface]
\definestructureconversionset
[sectionnumbers]
[0,n,Characters,g,n]
[n]
\definefontfeature[section]
[smcp=yes,
c2sc=yes]
\setupheads[sectionconversionset=sectionnumbers]
\setuphead[section][style={\feature[+][section
[sectionnumbers]
[0,n,Characters,g,n]
[n]
\definefontfeature[section]
[smcp=yes,
c2sc=yes]
\setupheads[sectionconversionset=sectionnumbers]
\setuphead[section][style={\feature[+][section]}]
\starttext
\section{Just text}
{\feature[+][section]Just text}
\stoptext
out variable fonts,
axes are only accesible using their name (not their tag) in the axis
section (not in the design axis section), aren't they?
And each font feature requires a new font instance (unlike other font
features such as small caps or many other OpenType features), doesn't it?
>
alled a few days ago.
>> Is it possible for me to use \starthangaround ?
>
> Apparently not.
> The CD_Booklet page is more than 10 years old.
> And the section on the Unexpected_behavior page links to a section in
> Using_graphics that’s deleted. It also says “This
\starthangaround is undefined. It isn’t in any of my context installation
files, including cont-new.tex. I'm using LMTX, installed a few days ago.
Is it possible for me to use \starthangaround ?
Apparently not.
The CD_Booklet page is more than 10 years old.
And the section on the Unexpected_beh
On 2022-11-15 21:49, Joel via ntg-context wrote:
I need to make a section of text in my document narrower, about
.\textwidth.
Basically the text has normal alignment and everything, just instead
of filling \textwidth, its compressed so there is a larger white space
to the right.
I&#x
I need to make a section of text in my document narrower, about .\textwidth.
Basically the text has normal alignment and everything, just instead of filling
\textwidth, its compressed so there is a larger white space to the right.
I've tried dozens of things, but cannot get a good sol
On 11/14/2022 7:28 PM, Pablo Rodriguez via ntg-context wrote:
On 11/14/22 14:00, Denis Maier via ntg-context wrote:
Hi,
most examples in the mkiv-xml manual use #1 with \xmlsetsetup, e.g.
\startxmlsetups xml:demo:base
\xmlsetsetup{#1}{document|section|p}{xml:demo:*}
\stopxmlsetups
However
On 11/14/22 14:00, Denis Maier via ntg-context wrote:
> Hi,
>
> most examples in the mkiv-xml manual use #1 with \xmlsetsetup, e.g.
>
> \startxmlsetups xml:demo:base
> \xmlsetsetup{#1}{document|section|p}{xml:demo:*}
> \stopxmlsetups
>
> However, in quite a few
Hi,
most examples in the mkiv-xml manual use #1 with \xmlsetsetup, e.g.
\startxmlsetups xml:demo:base
\xmlsetsetup{#1}{document|section|p}{xml:demo:*}
\stopxmlsetups
However, in quite a few occasions I've noticed the usage of \xmldocument
instead of #1.
What exactly is the difference ?
cker.ietf.org/doc/html/rfc3986#section-2.3).
Other ones (such as "ö") have to be escaped. This is why only the sample
containing the escaped "ö" (as "%C3%B6" [which TeX needs to escape
again]) worked for you.
It seems that depending on the PDF viewer (and I guess the
On 10/14/22 23:24, Pablo Rodriguez via ntg-context wrote:
> Hi Hans,
>
> I have the following sample:
>
> \setupinteraction[state=start,
> focus=standard]
> \starttext
> \completecontent
> \section{section}
> a\footnote{\contextversion}
> \stoptext
Hi Hans,
I have the following sample:
\setupinteraction[state=start,
focus=standard]
\starttext
\completecontent
\section{section}
a\footnote{\contextversion}
\stoptext
With version from 2022.09.11 20:44, the link from the TOC reads in the
PDF file:
4 0 obj
<<
/D [
list,
>>
>> attached is an example taken from the luametafun manual.
>> The letter o looks odd. When I compile the manual the examples in section 4
>> look also bad (different font; page 10 attached).
>> It seems like the paths miss one point.
>>
>> This
h links here:
>
> \setupinteraction[state=start,
> color=darkred,
> contrastcolor=darkred,
> focus=standard]
> \starttext
> \completecontent
> \section[a]{b}
> \about[a]
> \stoptext
>
> And this is a regression. I think it was introduced in
Its worring now. I have to add \setuplist[subsection][alternative=d] after
\setupcombinedlist[content] etc. before that line it has no effect here.
\definecombinedlist[content][part,chapter,section,subsection]
\setupcombinedlist[content][alternative=c,partnumber=no,placehead=yes,color=black
\hairline
\section{Section}
\subsection{Subsection}
\subsubsection{Subsubsection}
\stoptext
Check if your braces/brackets are right.
Hraban
___
If your question is of interest to others as well, please add a
de octubre de 2022 09:55
Para: Horacio Suárez via ntg-context
Cc: Henning Hraban Ramm
Asunto: Re: [NTG-context] alternative en TOC
Am 06.10.22 um 13:37 schrieb Horacio Suárez via ntg-context:
> hello
>
> it is possible to list chapters and section as "alternative=c" and
> s
Am 06.10.22 um 13:37 schrieb Horacio Suárez via ntg-context:
hello
it is possible to list chapters and section as "alternative=c" and
subsections as "alternative=d" in the same TOC?
Did you try
\setuplist[subsection][alte
hello
it is possible to list chapters and section as "alternative=c" and subsections
as "alternative=d" in the same TOC?
Thankyou very much in advance.
---
Horacio Suárez
Editorial Antropofagia
mpare both links here:
\setupinteraction[state=start,
color=darkred,
contrastcolor=darkred,
focus=standard]
\starttext
\completecontent
\section[a]{b}
\about[a]
\stoptext
And this is a regression. I think it was introduced in latest from
2022.07.06 21:42, since latest from
Thanks for the pointers, but unfortunately I cannot reproduce the second
fix with either the system pdf viewer or the browser one.
\usemodule[ipsum]
\setupinteraction[state=start,focus=standard]
\starttext
\completecontent
\section{s1}\ipsum
\section{s2}\ipsum
> On 28 Sep 2022, at 09:18, Sylvain Hubert via ntg-context
> wrote:
>
> Dear list,
>
> \usemodule[ipsum]
> \setupinteraction[state=start]
>
> \starttext
> \completecontent
> \section{s1}\ipsum
> \section{s2}\ipsum
> \sec
Dear list,
\usemodule[ipsum]
\setupinteraction[state=start]
\starttext
\completecontent
\section{s1}\ipsum
\section{s2}\ipsum
\section{s3}\ipsum
\section{s4}\ipsum
\section{s5}\ipsum
\section{s6}\ipsum
\stoptext
In the table of contents, s1 and s2 (at
On Thu, Sep 22, 2022 at 11:15 AM Jacob Kauffmann via ntg-context
wrote:
>
> Dear list,
>
> attached is an example taken from the luametafun manual.
> The letter o looks odd. When I compile the manual the examples in section 4
> look also bad (different font; page 10 attached
Dear list,
attached is an example taken from the luametafun manual.
The letter o looks odd. When I compile the manual the examples in section 4
look also bad (different font; page 10 attached).
It seems like the paths miss one point.
This is with the latest version 2022.09.11 20:44.
Cheers
t (9.2, 9.5, 9.6, 3, "Schwanz");
annotb (3, -.5, 3.1, .9, "Huf");
annotb (3, -.5, 3.9, 1.1, "");
\stopMPpage
\stoptext
%%%
There are still some further ideas and a lot to learn for me:
- multi line annotations
- a transparent white background
- a
> > doc for example:
> >
> > ```lmtx
> > \setscript[hanzi]
> > \usetypescriptfile[mscore]
> > \usebodyfont [mschinese,20pt]
>
> can you upgrade the chiese section in that file for windows 10+ as the
> old fonts are gone
>
> (i tested with \defin
\setupinteraction[state=start,focus=standard] was what I wanted.
Thanks.
--- Original Message ---
On Thursday, September 1st, 2022 at 4:42 PM, Pablo Rodriguez via ntg-context
wrote:
> On 9/1/22 14:36, amano.kenji via ntg-context wrote:
>
> > I just created a reference t
On 9/1/22 14:36, amano.kenji via ntg-context wrote:
> I just created a reference to a \section with \in.
>
> Clicking the \in reference doesn't go to the \section, but to the
> page that has the \section.
>
> Does ConTeXt lack the ability to go to an exact point of a numbe
On Thu, Sep 1, 2022 at 2:37 PM amano.kenji via ntg-context
wrote:
>
> I just created a reference to a \section with \in.
>
> Clicking the \in reference doesn't go to the \section, but to the page that
> has the \section.
>
> Does ConTeXt lack the ability to go to an
I just created a reference to a \section with \in.
Clicking the \in reference doesn't go to the \section, but to the page that has
the \section.
Does ConTeXt lack the ability to go to an exact point of a numbered element on
a
Hello!
based on the answer Hans posted on my question how to correctly setup header
texts in a ConTeXt Lua Document I added a section on the Wiki:
https://wiki.contextgarden.net/CLD#Setting_up_Header_Texts
Kind regards
Willi
> On 25 Aug 2022, at 19:45, Hans Hagen wrote:
>
> On 8/
I have some settings like this, which define the part, chapter, and section
titles within a file that contains all of my common settings for all files.
\definepagebreak[chapterpagebreak][yes, right]
\setuphead[part][style=\sse, placehead=yes, expansion=yes]
\setuphead[chapter][style=\sse
that line breaks work properly)
(b) some section titles are missing
Ad (a). The source that looks similar to this:
int main()
{
return 0;
}
should be converted into some kind of equivalent of
% on top
\usemodule[vim]
\definevimtyping [CPP] [syntax=cpp]
\startCPP
int main()
{
solutions fail on generic input.
>> Sorry, out of clues
> \startbuffer[demo]
> ...
That puts the whole content inside the \section, and I don’t think that
was the intent. I understood that Pablo only wants the “h3” node.
In the original request, the CSS “{h3 + blockquote}” matches
etups xml:p
\startpar\xmlflush{#1}\stoppar
\stopxmlsetups
\startxmlsetups xml:blockquote
\startblockquote\xmlflush{#1}\stopblockquote
\stopxmlsetups
\startxmlsetups xml:section:level3
\xmldoif{#1}{/blockquote} {
\xmldoifnot{#1}{/p} {
\section{\xmlflush{#1}}
:*}
\xmlsetsetup{#1}
{(div|section)[contains(@class,'level3')]/h3/../!p/../h3}
{xml:section}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:p
\startpar\xmlflush{#1}\stoppar
\stopxmlsetups
\startxmlsetups xml:blockquote
\startblockquot
,
> }
>
>
Thanks to your guidance, I solved the problem. And I would like to look
into some other related issues that I have doubts about and get back to you
together. So I need some more time.
> > doc for example:
> >
> > ```lmtx
> > \setscript[hanzi]
> > \uset
= nobreak_autoshrink_break_stretch,
}
doc for example:
```lmtx
\setscript[hanzi]
\usetypescriptfile[mscore]
\usebodyfont [mschinese,20pt]
can you upgrade the chiese section in that file for windows 10+ as the
old fonts are gone
(i tested with \definedfont[file:mingliu.ttc*chinese @ 10pt])
Hans
>
> > 2. Can the \bookmark[list]{text} command be somehow used for multi-level
> > bookmarking?
> >
> > While the first question would make up for a more consistent solution,
> > the second question would do the job as well.
> >
> > I hope some of yo
something {Denis Maier}{ —\
}\IndexAuthor Denis Maier
structures > bookmark: Introduction
structure > sectioning > section @ level 3 : 1.0.1 -> Introduction
fonts > defining > unable to define
'IBMPlexSansHebrew-regular' as 'dummy--5
make up for a more consistent solution,
the second question would do the job as well.
I hope some of you can enlighten me.
Cheers, k
%%% START of MWE
\definehead[VisiSection][section]
\setuphead[VisiSection][number=no]
\definehead[InvisiSection][VisiSection]
\setuphead[InvisiSection][placehe
e job as well.
I hope some of you can enlighten me.
Cheers, k
%%% START of MWE
\definehead[VisiSection][section]
\setuphead[VisiSection][number=no]
\definehead[InvisiSection][VisiSection]
\setuphead[InvisiSection][placehead=no]
\definelist[CustomBMarks]
\setupinteraction[state=
301-BT-ligatures]
\definefontsynonym [SerifItalic] [file:Venetian301BT-Italic]
[features=venetian-301-BT-ligatures]
\stoptypescript
%% end
Note that the names v1, v2 and v3 are entirely arbitrary. Also, the
\starttypescript section sets the font features to be just those I've defined -
es,v3=yes]
>> Note that the names v1, v2 and v3 are entirely arbitrary. Also, the
>> \starttypescript section sets the font features to be just those I've
>> defined - potentially losing whatever 'default' would provide. But since the
>> font doesn'
Am 20.07.22 um 21:40 schrieb Bruce Horrocks via ntg-context:
\definefontfeature [venetian-301-demi-ligatures] [v1=yes,v3=yes]
\definefontfeature [venetian-301-BT-ligatures] [v2=yes,v3=yes]
Note that the names v1, v2 and v3 are entirely arbitrary. Also, the
\starttypescript section sets the
ian-301-BT-ligatures] [v2=yes,v3=yes]
\starttypescript [serif] [myBookFont]
\definefontsynonym [Serif] [file:venetian-301-demi-bt]
[features=venetian-301-demi-ligatures]
\definefontsynonym [SerifBold] [file:Venetian301BT-Bold]
[features=venetian-301-BT-ligatures]
\definefontsynonym [SerifItalic
;
> You’re welcome!
>
> >
> > \definestructureconversionset[mySet][A,n,A,n][n] % starts at part!
> > \setuphead[section,subsection][sectionconversionset=mySet]
> > \setuphead[subsection][sectionsegments=section:subsection,
> stopper={.}]
> >
> >
Am 10.07.22 um 22:25 schrieb Alan Bowen via ntg-context:
Thank you, Hraban, for the solution and the link!
You’re welcome!
\definestructureconversionset[mySet][A,n,A,n][n] % starts at part!
\setuphead[section,subsection][sectionconversionset=mySet]
\setuphead[subsection
letters and my
> > subsections with Arabic numbers. So far, no joy. What am I missing?
> >
> > Alan
> >
> > Mwe: with ConText ver: 2022.01.21 20:13 LMTX fmt: 2022.2.1. (The
> > problem persists when I run ConTeXt online)
> >
> > \setuphead[s
ConTeXt online)
\setuphead[section][conversion=A]
\setuphead[subsection][conversion=n, sectionsegements=section:subsection,
stopper={.}]
\definestructureconversionset[mySet][A,n,A,n][n] % starts at part!
\setuphead[section,subsection][sectionconversionset=mySet]
\setuphead[subsection
I’m trying to get my sections numbered with capital letters and my
subsections with Arabic numbers. So far, no joy. What am I missing?
Alan
Mwe: with ConText ver: 2022.01.21 20:13 LMTX fmt: 2022.2.1. (The problem
persists when I run ConTeXt online)
\setuphead[section][conversion=A]
\setuphead
]
\setupenumeration
[definition]
[way=bysection,
prefix=yes,
prefixsegments=section]
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
Hey there,
please consider:
\starttext
\defineenumeration[definition][text=Definition, alternative=serried]
\setupnumber[definition][way=bysection, numbersection=yes]
\section{My section 1}
\startdefinition
My fist definition
\stopdefinition
; www.pragma-ade.com @1.1.1.1
>;; global options: +cmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33675
>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>
>;; OPT PSEUDOSECTION:
>; EDNS: version: 0, fl
ags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.pragma-ade.com.IN A
;; ANSWER SECTION:
www.pragma-ade.com. 7200IN A 208.91.197.132
;; Qu
just preload it, as in:
\usebodyfont[modern]
\setupbodyfont[plex]
\setuphead
[section]
[style={\switchtobodyfont[modern]}]
\starttext
\section{A}
A
\stoptext
That seems to have fixed it. Thanks!
-- Max
On 6/30/2022 10:36 AM, Max Chernoff via ntg-context wrote:
If you load the Plex typescript, a spurious space is added on the first
switch to another font, messing up any alignment. This doesn't happen
with any other fonts; only with Plex.
MWE:
\setuphead[section][style={\switchtobod
If you load the Plex typescript, a spurious space is added on the first
switch to another font, messing up any alignment. This doesn't happen
with any other fonts; only with Plex.
MWE:
\setuphead[section][style={\switchtobodyfont[modern]}]
\setupbodyfont[plex]
\star
Works, thanks!
On Fri, 2022-06-24 at 12:44 +0200, Wolfgang Schuster via ntg-context wrote:
> Johann Birnick via ntg-context schrieb am 24.06.2022 um 11:59:
> > Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
> > anymore. Any ideas?
&g
Johann Birnick via ntg-context schrieb am 24.06.2022 um 11:59:
Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
anymore. Any ideas?
What happens with
\cite[righttext={{, section 2.1}}]
or
\cite[righttext={\textcomma\ section 2.1}]
Wol
Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
anymore. Any ideas?
Johann
On Fri, 2022-06-24 at 09:24 +0200, Henning Hraban Ramm via ntg-context wrote:
> Am 24.06.22 um 02:09 schrieb Johann Birnick via ntg-context:
> > Hi there,
> >
> >
Am 24.06.22 um 02:09 schrieb Johann Birnick via ntg-context:
Hi there,
using \cite[myreference] I will get a result like "[1]", or I could also change
the "1" into some more detailed information such as a tag.
However, I want to obtain something like "[1, section 2.1]&
Hi there,
using \cite[myreference] I will get a result like "[1]", or I could also change
the "1" into some more detailed information such as a tag.
However, I want to obtain something like "[1, section 2.1]".
How can I achieve this
On 6/17/22 18:33, Wolfgang Schuster via ntg-context wrote:
> [...]
> To create separate styles for chapters within the frontmatter and
> bodymatter you have to create a new section command where you can apply
> different list settings.
Many thanks for your reply, Wolfgang.
Now I have
you have to create a new section command where you can apply
different list settings.
\starttext
\completecontent
You're now placing \completecontent (and the associated \title) outside
of any sectionblock.
Wol
I have a document with conditionally-generated content.
There are some situations when I need the section title to change according to
the content displayed within that section.
For instance, the 14th section that appears in *every* chapter is either called
"Cause and Effect" if the
se issues:
>
> 1. As far as I understand, the `\section` syntax currently produced by
>pandoc should be considered mkii legacy syntax. We're likely going to
>switch to the modern `\startsection`/`\stopsection` syntax instead.
>Are there any concerns about retiring
-context] Contractions in ligature suppression word list
Thanks for the response, Bruce.
1) The file you attached doesn't include the word "wolfing", nor "wolfin". I
assume they need to be
The suffixes section accounts for this. Wolfing and wolfish both suppress th
Thanks for the response, Bruce.
1) The file you attached doesn't include the word "wolfing", nor "wolfin".
> I assume they need to be
The suffixes section accounts for this. Wolfing and wolfish both suppress
the ligature correctly.
I removed the comma separator
in’,
> ing
> ]],
>
> See https://wiki.contextgarden.net/Ligatures#Word_suppression for an example
> usage.
>
> Thank you!
>
I'm probably missing something here but...
1) The file you attached doesn't include the word "wolfing", nor &quo
]
\startcolor[darkred]
\dorecurse{10}{\section{Knuth}\pushoutputstream
\inouter{first}\input knuth\footnote{note}\par\pushoutputstream}
\stopcolor
\stopoutputstream
\startoutputstream[two]
\startcolor[darkgreen]
\dorecurse{10}{\section{Zapf}\pushoutputstream
\inouter{second
shing possible)
>
> Someone who maintains an export programme for ConTeXt uses
> sectionlevels.
>
> You get the incremental subsections and subsubsection like this.
>
> \startsectionlevel
> \startsectionlevel
> \startsectionlevel
> \stopsectionlevel
>
xperts on
these issues:
1. As far as I understand, the `\section` syntax currently produced by
pandoc should be considered mkii legacy syntax. We're likely going to
switch to the modern `\startsection`/`\stopsection` syntax instead.
Are there any concerns about retiring the old sy
programme for ConTeXt uses
> sectionlevels.
>
> You get the incremental subsections and subsubsection like this.
>
> \startsectionlevel
> \startsectionlevel
> \startsectionlevel
> \stopsectionlevel
> \stopsectionlevel
> \stopsectionlevel
>
> This makes it possible t
subsubsection like this.
\startsectionlevel
\startsectionlevel
\startsectionlevel
\stopsectionlevel
\stopsectionlevel
\stopsectionlevel
This makes it possible to ignore the part-chapter-section naming
convention and be more flexible. You can leave it to the style files to
decide which l
Hi all,
I'm currently trying to improve the ConTeXt output generated by pandoc,
the document convert. There are two questions that we haven't decided
on, and I'd be grateful to receive some feedback from ConTeXt experts on
these issues:
1. As far as I understand, the `\section` s
Hi,
testing this mwe I’d expect some indicators detecting overfull lines.
At least on my machine (ConTeXt ver: 2022.01.21 20:13 LMTX) nothing happens:
\setuppapersize[A6]
% Tell ConTeXt where the windmill picture is
\setupexternalfigures[location={default}]
\version[temporary]
\section{Slithy
hich was added
>> to avoid problems like in your example.
>>
>> \startsetups headertext
>> \bTABLEnested[setups=headertable,option=stretch]
>> ...
>> \eTABLEnested
>> \stopsetups
>
> Splendid (as always)! Definitely a better solution for Stefan&
Enested
> \stopsetups
Splendid (as always)! Definitely a better solution for Stefan's document.
I added a section in the wiki making a note of this:
https://wiki.contextgarden.net/TABLE#Headers_with_TABLEs
Thanks Wolfgang! Until now, I did not even know of the 'n
Hi,
the automatic reference prefix for section etc. with the setup
\setuphead[chapter][referenceprefix=+]
doesn't work anymore (broken since a while).
The following patch for strc-sec.mkxl fixes the missing prefix:
begin fix
\def\strc_sectioning_set_reference_prefix
{\if
l
> >
> >
> > \stopbuffer
> >
> > \startxmlsetups xml:text
> > \xmlsetsetup{#1}{doc|s|ss}{xml:*}
> > \stopxmlsetups
> >
> > \xmlregistersetup{xml:text}
> >
> > \startxmlsetups xml:doc
> > \chapter{\xmlp
10.05.22 um 04:03 schrieb jbf via ntg-context:
Hi list,
In an attempt to make a dictionary interactive in certain ways,
perhaps I am misusing the \in{}[] command here, but sometimes a
reference works and sometimes it doesn't. I have no idea why it
doesn't. Here is the situation:
Each
> On 10 May 2022, at 04:03, jbf via ntg-context wrote:
>
> Can anyone give me a hint as to what I might be doing wrong? I realise that
> usually these references call on page numbers or section numbers, but I don't
> want/need (or do I?) to use those. I simply the reader
dictionary interactive in certain ways, perhaps
I am misusing the \in{}[] command here, but sometimes a reference works
and sometimes it doesn't. I have no idea why it doesn't. Here is the
situation:
Each dictionary entry is a section that has been defined as 'entry',
hence we hav
301 - 400 of 1001 matches
Mail list logo
