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
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 dictionary entry is a section that has be
Hi Joel,
I think you can achieve what you want by using \placelist[chapter,section]
instead of \completecontent. Then you can start the TOC by
\startchapter[Content] \placelist…. \stopchapter. The same approach can be used
for other lists/indexes.
Kind regards
Willli
> On 8 May 2022, at
:*}
\stopxmlsetups
\xmlregistersetup{xml:text}
\startxmlsetups xml:doc
\chapter{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:s
\section{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:ss
ever, when I comment grid again in my document, it does compile
the pdf.
Well that's why it was a beta :) Looks like I made some questionable
assumptions
about the order of the hlist/baselineskip nodes, so the module
completely broke
with things as simple as section headings.
Hopefully this ne
s compile the pdf.
Well that's why it was a beta :) Looks like I made some questionable assumptions
about the order of the hlist/baselineskip nodes, so the module completely broke
with things as simple as section headings.
Hopefully this new beta should fix things:
https://github.com/gu
pages, 1.213 pages/secondmtx-context | purged files: tst-taccount.log, tst-taccount.tucmtx-context | pdfview methods: auto default okular pdfxcview sumatra, current method: sumatra (directives_pdfview_method)pdfview | command: wine "sumatrapdf.exe" -reuse-instance -bg-color
ng on my file? Then you
can get a better idea of what I mean by the end of some pages when I
comment grid=yes (apart from the mischief that happens with the
horizontal spaces in some paragraphs of the bibliographic section).
Or, if you prefer, and you need more feedback, I can send you my
cu
h lwc actually acting on my file? Then you
can get a better idea of what I mean by the end of some pages when I
comment grid=yes (apart from the mischief that happens with the
horizontal spaces in some paragraphs of the bibliographic section).
Or, if you prefer, and you need more feedback, I can send y
the new pdf with lwc actually acting on my file? Then you
can get a better idea of what I mean by the end of some pages when I
comment grid=yes (apart from the mischief that happens with the
horizontal spaces in some paragraphs of the bibliographic section).
Or, if you prefer, and you need mo
be downloaded from the modules section of the
context wiki page is no longer supported.
I wrote a new version of the module a few years ago after I got a user
request but I haven't put the new version on the wiki. To use the new
version of the module you can download the file from my g
\stopxmlsetups
\xmlregistersetup{xml:text}
\startxmlsetups xml:doc
\chapter{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:s
\section{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:ss
\subsec
ntrol
sequence. That should include things like section titles and footnotes.
Though I'm afraid that might be asking for too much.
I'd rather not make it part of my editor (I use vim) and have it as an
extra step which I can add to something like a Makefile.
Do I need to install all of
Hi Alain,
Yes that's what I mean, spellchecking any content which is not a control
sequence. That should include things like section titles and footnotes.
Though I'm afraid that might be asking for too much.
I'd rather not make it part of my editor (I use vim) and have it as an
e
: the Iliad
I want to typeset the section title with some added information. Since I’m
processing in a loop, I thought this would be easier in Lua, so I have
something like this:
local i = 0
local sessions = { “April 2”, “April 9”, “April 16” } -- etc.
function xml.functions.section(t
wiki
article on a basic way to start one’s own custom definitions...
Best
Thomas
> On 26. Mar 2022, at 15:34, A A via ntg-context wrote:
>
> Hi Thomas,
>
> Yes, I was able to find the appropriate section in the manual, thanks. Please
> see my answer at SE.
>
> I don&#x
basic way to start one’s own custom definitions...
Best
Thomas
> On 26. Mar 2022, at 15:34, A A via ntg-context wrote:
>
> Hi Thomas,
>
> Yes, I was able to find the appropriate section in the manual, thanks. Please
> see my answer at SE.
>
> I don't think readi
Hi Thomas,
Yes, I was able to find the appropriate section in the manual, thanks.
Please see my answer at SE
<https://tex.stackexchange.com/questions/638481/getting-a-simple-bibliography-to-work-in-context>
.
I don't think reading the docs is far-fetched by the way. But I think
asking
setup of my book. — I am using now the solution presented by
> Sreeram.
>
> Again thank you so much!
> Kind regards
>
> Willi
>
>> On 22 Mar 2022, at 01:21, Adam Reviczky via ntg-context
>> wrote:
>>
>> Hi,
>>
>> There is a good ove
cessible variables at:
> https://tex.stackexchange.com/questions/134474/context-part-chapter-section-and-subsection-names
> >
> > Maybe you want something like this?
> >
> > \starttext
> > \setuphead[chapter][number=no]
> > \startchapter[title={My Chapter}]
>
presented by
Sreeram.
Again thank you so much!
Kind regards
Willi
> On 22 Mar 2022, at 01:21, Adam Reviczky via ntg-context
> wrote:
>
> Hi,
>
> There is a good overview of accessible variables at:
> https://tex.stackexchange.com/questions/134474/context-part-chapter-s
Hi,
There is a good overview of accessible variables at:
https://tex.stackexchange.com/questions/134474/context-part-chapter-section-and-subsection-names
Maybe you want something like this?
\starttext
\setuphead[chapter][number=no]
\startchapter[title={My Chapter}]
Hello world!
\startMPcode
if \somenamedheadnumber{chapter}{last} > 0 :
last_chap := \somenamedheadnumber{chapter}{last} ;
else :
last_chap := 1 ;
fi;
if \somenamedheadnumber{section}{current} > 0 :
curr_sect := \somenamedheadnumber{section}{current} ;
else:
curr_sect := 1 ;
f
u can get a section title (or another “mark”), you
can’t combine it with the variable commands, and you don’t need it for
your case.
https://wiki.contextgarden.net/Command/getmarking isn’t really helpful
since there’s no example with section titles, but it shows you can
also get previous or
Hello,
I am a little desperate… I have installed in a new directory the latest version
of ConTeXt.
I run the sample file I provided before. After enabling a second
chapter-section before the \setups{Thumb-picture} the metafun error reoccurs. —
Looking at the log I do net get really wiser
Hi Julian,
you’re right, the example didn’t do what you wanted, and it didn’t
intend to.
Using \getmarking you can get a section title (or another “mark”), you
can’t combine it with the variable commands, and you don’t need it for
your case.
https://wiki.contextgarden.net/Command
chapter]
\hfill
\llap{Un Nom}
\stopsetups
\startsetups[text left]
\rlap{Una Person}
\hfill
\getmarking[section]
\hfill
\llap{\pagenumber}
\stopsetups ___
If your question is of interest to others as well, please add an en
right]
\rlap{\pagenumber}
\hfill
\getmarking[chapter]
\hfill
\llap{Un Nom}
\stopsetups
\startsetups[text left]
\rlap{Una Person}
\hfill
\getmarking[section]
\hfill
\llap{\pagenumber}
\stopsetups
___
If your question is
left]
\rlap{Una Person}
\hfill
\getmarking[section]
\hfill
\llap{\pagenumber}
\stopsetups
HTH
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@n
Which could be translated in English !
\currentlistentrylocation = Consecutive number of the list entry
\namedstructureheadlocation{section} = Section number of the specified
hierarchy level (chapter, section, etc.) \currentlistentrynumber =
section number of the current list entry
Hi Julian,
have fun with:
\currentlistentrylocation
= Laufende Nummer des Listeneintrags \namedstructureheadlocation{section}
= Abschnittsnummer der angegebenen Hierarchiestufe (chapter, section usw.)
\currentlistentrynumber
= Abschnittsnummer des aktuellen Listen eintrags
la bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla}
\def\Fig{\placefigure{A figure.}{\framed{\vbox to 5cm{bla
\def\Tab{\placetable{A table.}{\framed{\vbox to 5cm{bla}}}}
\starttext
\section{Section}\Par\Par\P
la bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla}
\def\Fig{\placefigure{A figure.}{\framed{\vbox to 5cm{bla
\def\Tab{\placetable{A table.}{\framed{\vbox to 5cm{bla
\starttext
\section{Section}\Par\Par\Par\F
t fuzzy paragraphs
(forget about them).
To make it short it triggered a memory about a rather old thread, where
Hans mentioned that the exporter is not so fond of and keen about LaTeX
style \chapter, \section commands and that he advises to use
\startchapter \stopchapter, \startsection \stopsection, e
=exercici_color, title=yes,
titlestyle=\ss, titledistance=0em, left={\bgroup\bf}, right={\egroup},
after={\blank[big]}, prefix=yes, prefixsegments=section, way=section]
\starttext
\section{Operacions amb fraccions}
\subject{Preguntes}
\startexercici[exercici:operacions-amb-fraccions-1]{suma i resta} Opereu
, title=yes,
> titlestyle=\ss, titledistance=0em, left={\bgroup\bf}, right={\egroup},
> after={\blank[big]}, prefix=yes, prefixsegments=section, way=section]
> > [snip]
> >
> > Removing "alternative=serried" gives a more grid like layout and
> (possibly coinciden
headstyle=\ss,
> > distance=0.25em, width=fit, headcolor=exercici_color, title=yes,
> > titlestyle=\ss, titledistance=0em, left={\bgroup\bf}, right={\egroup},
> > after={\blank[big]}, prefix=yes, prefixsegments=section, way=section]
> [snip]
>
> Removing "altern
\bgroup\bf}, right={\egroup}, after={\blank[big]}, prefix=yes,
> prefixsegments=section, way=section]
[snip]
Removing "alternative=serried" gives a more grid like layout and (possibly
coincidentally) the problem of the 'c' and 'h' labels being orphaned at the
bot
text={Exercici},
stopper={.\space}, width=fit, headstyle=\ss, distance=0.25em, width=fit,
headcolor=exercici_color, title=yes, titlestyle=\ss, titledistance=0em,
left={\bgroup\bf}, right={\egroup}, after={\blank[big]}, prefix=yes,
prefixsegments=section, way=section]
\starttext
\section{Operacion
I have a section somewhat like this...I'm replacing the code with something
much simpler, but its basically doing a similar thing, running conditionals to
check which content to place:
\section{Brave Rabbits}
\ifnum\somenumber>3 Print this content about rabbits.
On 1/23/2022 8:58 AM, Alexandre Christe via ntg-context wrote:
Dear list,
I've noticed that in my document the linespacing (verified
with \the\baselineskip) is not consistent across the whole document.
In the first section, it's fine (no maths). Later on, it gets increased
by s
Dear list,
I've noticed that in my document the linespacing (verified
with \the\baselineskip) is not consistent across the whole document.
In the first section, it's fine (no maths). Later on, it gets increased by
some amount, which tends to depend on what kind of mathematics are in
b
will be tremendous. But
I would like to know what the "most common" counters are called, for
example the ones that control the different structural units (chapter,
section...) or the elements of a structured list, etc.
I have tried to apply \incrementcounter or \decrementcounter to some
ommon" counters are called, for
example the ones that control the different structural units (chapter,
section...) or the elements of a structured list, etc.
I have tried to apply \incrementcounter or \decrementcounter to some
counters that also exist in TeX as, for example, chapter, sect
Dear list,
I asked this some time ago
(https://mailman.ntg.nl/pipermail/ntg-context/2021/102394.html).
Using the following sample:
\starttext
\definereferenceformat[itsc][in]
\setupreferencestructureprefix[itsc][default]
[prefixsegments=section]
\chapter{Chapter}
\section[b
Michael Urban via ntg-context schrieb am 09.01.2022 um 17:25:
I want to put a book title above the Chapter title for the first chapter of a
book. I suppose that this can be accomplished with a 'before=' clause that
checks to see if it is the first chapter... but how do I look at the chapter
n
I look at the chapter number in order to set up the
> conditional?
Hi MIchael,
this might do the trick:
\starttext
\dorecurse{5}
{\chapter{Chapter \structurenumber}
\dorecurse{5}
{\section{Section \structurenumber}
\doifelse{\somenamedheadnumber{chapter}{current}}{1}
I want to put a book title above the Chapter title for the first chapter of a
book. I suppose that this can be accomplished with a 'before=' clause that
checks to see if it is the first chapter... but how do I look at the chapter
number in order to set up the conditional?
Mike
___
rhaps be
given a tiny bit better treatment on the wiki. I agree with him that
https://wiki.contextgarden.net/Use_the_fonts_you_want seems like the
best place to mention it, and even think that all of the last section
could be rewritten using \definefontfamily instead of a typescript
definition (whic
on the wiki. I agree with him that
https://wiki.contextgarden.net/Use_the_fonts_you_want seems like the
best place to mention it, and even think that all of the last section
could be rewritten using \definefontfamily instead of a typescript
definition (which can be moved elsewhere, it obviously d
twelve \Ntw}
I used pdflatex and memoir, which has paragraphed footnotes. Here is
the relevant section from the
preamble:
\renewcommand*{\@makefnmark}{}
\newfootnoteseries{P}
\paragraphfootstyle{P}
\renewcommand{\thefootnoteP}{}
\footmarkstyleP{}
\renewcommand{\@makefnmarkP}{\hskip-
necessary. The \lem produces the sign
> that divides the
> critical text and its witnesses from the variants, usually "]", the rest are
> sigla, like S1, S3
> etc.
>
> mumukṣuvyavahāroktimayāt prakaraṇād anu \danda
> athotpattiprakaraṇaṃ mayedaṃ parikathyate \slok
seven \Sft \lem \emph{param} \Sone \Sthree \Snine
\Ntwelve \Ntw}
I used pdflatex and memoir, which has paragraphed footnotes. Here is
the relevant section from the
preamble:
\renewcommand*{\@makefnmark}{}
\newfootnoteseries{P}
\paragraphfootstyle{P}
\renewcommand{\thefootnoteP}{}
\foot
ote with the authors'
> > affiliation for each section/chapter, by adapting things from the wiki
> > (https://wiki.contextgarden.net/Table_of_Contents#Author_in_ToC and
> > https://wiki.contextgarden.net/LaTeX_Thanks). However, one thing that
> > bugs me is that any note na
Youssef Cherem via ntg-context schrieb am 01.01.2022 um 13:10:
I've tried to implement a journal-like footnote with the authors'
affiliation for each section/chapter, by adapting things from the wiki
(https://wiki.contextgarden.net/Table_of_Contents#Author_in_ToC
I've tried to implement a journal-like footnote with the authors'
affiliation for each section/chapter, by adapting things from the wiki (
https://wiki.contextgarden.net/Table_of_Contents#Author_in_ToC and
https://wiki.contextgarden.net/LaTeX_Thanks). However, one thing that bugs
me i
.
When I use local footnotes within a tabulate section, the foot notes
gets placed unevenly. If I remove the "c" from
\starttabulate[|p(3cm)c|p|], then the footnotes are aligned. Is it a
bug? If not, how can I correct it?
1. Provide the correct number of columns in your table because in the
Hi,
I am trying to prepare a moderate sized document in Malayalam using
Context. Overall I have been successful. However, there are a few rough
edges for which I need help. This is the seventh (and the last one for
now) problem I face.
When I use local footnotes within a tabulate section, the
I've tried to implement a journal-like footnote with the authors'
affiliation for each section/chapter, by adapting things from the wiki here
<https://wiki.contextgarden.net/Table_of_Contents#Author_in_ToC> and here
<https://wiki.contextgarden.net/LaTeX_Thanks>. However, one
> > { type = "multiple",
> > data = { [ "f_i" ] = { "f", "i" } }
> > }
> >
> > }
> > rules = {
> >
> > { after = { { "o" } },
>
rectives [logs.errors]
%% missing font
\definefontfamily [foo] [serif] [no font here really]
\setupbodyfont [foo]
\starttext
%% missing characters
𝒜
%% missing figure
\externalfigure [foo]
%% missing references
See \in{section}[sec:none].
\stoptext
because these are not e
id wrong ?
Firstly, you have an extra } in the example above.
Secondly, rules need to come inside a data section. Thus (untested):
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
.errors]
%% missing font
\definefontfamily [foo] [serif] [no font here really]
\setupbodyfont [foo]
\starttext
%% missing characters
𝒜
%% missing figure
\externalfigure [foo]
%% missing references
See \in{section}[sec:none].
\stoptext
Marco
___
id wrong ?
Firstly, you have an extra } in the example above.
Secondly, rules need to come inside a data section. Thus (untested):
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
e example I posted on 2021-12-15 still returns success when it
should fail. So regarding the exit codes I see no change here.
> side float coming loose from section head issue solved; ...).
That's fixed indeed. Thanks for looking into that.
Marco
LMTX
On 12/24/2021 5:45 PM, Jason Ross via ntg-context wrote:
Dear list,
Is it possible to set the maximum table of contents depth to a number
rather than providing an explicit list of section names?
Background:
I am developing an exporter for Org mode. In Org, users can specify the
number of
liable; some low level tracing; side float
coming loose from section head issue solved; ...).
I'm experimenting with some more efficient low level state info
and in
the process ran into an issue / interference with (also low level)
attributes. I'm not sure if I solv
> On 24 Dec 2021, at 16:45, Jason Ross via ntg-context
> wrote:
>
> Dear list,
>
> Is it possible to set the maximum table of contents depth to a number rather
> than providing an explicit list of section names?
>
>
> Background:
>
> I am develop
{ 1 } }
> }
> }
> }
>
> Could someone please explain to me what I did wrong ?
Firstly, you have an extra } in the example above.
Secondly, rules need to come inside a data section. Thus (untested):
fonts.handlers.otf.addfeature{
name = "unfio"
escribió:
> Hi,
>
> When wrapping up before the weekend I uploaded a new lmtx (bottom floats
> fixed afaiks, but hat mechanism might see some improvements anyway next
> year; exit codes more reliable; some low level tracing; side float
> coming loose from section head issue solved
Does that make sense?
I understand. The issue I see is that this introduces a coupling between
section structure and table of contents that could be confusing for
users, and also makes the interface more complicated by adding another
keyword.
I am trying to take advantage of the flexibili
rieben:
On 12/24/21 1:29 PM, Denis Maier wrote:
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
it should be possible to map toc:2 to a combine
On 12/24/21 1:29 PM, Denis Maier wrote:
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are
ated to the
>> corresponding setting. (Here again, you can if course define
>> reasonable defaults.)
Actually, you don't need an alist. A simple quotes list should be enough:
#+Context_Sec
n, you can if course define
reasonable defaults.)
Actually, you don't need an alist. A simple quotes list should be enough:
#+Context_Section_Levels: '(chapter section subsection)
Denis
That isn't going to work. The interface needs to be the same as for the
other exporters f
lts.)
Actually, you don't need an alist. A simple quotes list should be enough:
#+Context_Section_Levels: '(chapter section subsection)
Deni
Hi,
When wrapping up before the weekend I uploaded a new lmtx (bottom floats
fixed afaiks, but hat mechanism might see some improvements anyway next
year; exit codes more reliable; some low level tracing; side float
coming loose from section head issue solved; ...).
I'm experimenting
401 - 500 of 7022 matches
Mail list logo
