;>>> Dear List members,
>>>> For my academic work with context I need the following cite according to
>>>> Apa standards:
>>>> Knuth (1984, p. 12) mentions ….
>>>> The matrix is this:
>>>> AUTHOR (, p.~n).
>>>> I
matrix is this:
AUTHOR (, p.~n).
I reckon this can somehow be accomplished with the \setupbtx command.
(Standard these and other variants are possible: AUTHOR () and
AUTHOR , p. n.)
I tried different setups: \setupbtx[apa:cite:authoryear], and
\setupbtx[apa:cite:authoryears], I played
to Apa
>> standards:
>> Knuth (1984, p. 12) mentions ….
>> The matrix is this:
>> AUTHOR (, p.~n).
>> I reckon this can somehow be accomplished with the \setupbtx command.
>> (Standard these and other variants are possible: AUTHOR () and AUTHOR
>>
. n.)
I tried different setups: \setupbtx[apa:cite:authoryear], and
\setupbtx[apa:cite:authoryears], I played with the lefttext, righttext and
other options, but none of them give the desired result.
Thank you for any suggestions.
Regards,
Robert
@article{Knuth1984,
author={Knuth, Donald E
possible: AUTHOR () and AUTHOR ,
p. n.)
I tried different setups: \setupbtx[apa:cite:authoryear], and
\setupbtx[apa:cite:authoryears], I played with the lefttext, righttext and
other options, but none of them give the desired result.
Thank you for any suggestions.
Regards,
Robert
cKay wrote:
Thanks Hraban, didn't think of that so will give it a try.
Best Wishes
Keith
On Fri, 28 Jul 2023, 17:28 Henning Hraban Ramm, wrote:
Am 28.07.23 um 17:04 schrieb Keith McKay:
> I played around with the setups for the align:pass:test4 code
below, as
> Hans
I
use \setuptyping for the general style with a background box. But that
conflicts with the setups for special cases like code and result side by
side.
I guess I’ll also include this in the CGJ setup.
... attached an extension that supports inheritance (via category),
still honors 'b
Thanks Hraban, didn't think of that so will give it a try.
Best Wishes
Keith
On Fri, 28 Jul 2023, 17:28 Henning Hraban Ramm, wrote:
> Am 28.07.23 um 17:04 schrieb Keith McKay:
> > I played around with the setups for the align:pass:test4 code below, as
> > Hans suggested,
Am 28.07.23 um 17:04 schrieb Keith McKay:
I played around with the setups for the align:pass:test4 code below, as
Hans suggested, and it was changing the \tolerance value which made the
difference. Increasing the \tolerance value to 1000 eliminated all
overfull hboxes but still left 79
Hi all!
Using the example below I have completed a test using a larger book.
This time I downloaded War and Peace from the Gutenberg Project and
extracted the individual xhtml files for Context.
I played around with the setups for the align:pass:test4 code below, as
Hans suggested, and it
files so that my setup for xml was very simple.
Here are my setups for the layout of the novels showing some trackers
that were used as well:
\definepapersize[pagee][width=5.06in,height=7.81in]
\setuppapersize[pagee]
% XML setups here
\startsetups[grid][mypenalties]
\setdefaultpenalties
simple.
Here are my setups for the layout of the novels showing some trackers
that were used as well:
\definepapersize[pagee][width=5.06in,height=7.81in]
\setuppapersize[pagee]
% XML setups here
\startsetups[grid][mypenalties]
\setdefaultpenalties
\setpenalties\widowpenalties{1}{150
lmt_outline is shifted to
the right, if I use it in a macro?
no time now but you can do this instead of the lmt_text:
draw lmt_outline [
text = "\bf\strut #1",
kind = "fillup",
fillcolor = "white",
rulethickness = rulesize,
[
text = "\bf\strut #1",
kind = "fillup",
fillcolor = "white",
rulethickness = rulesize,
];
(maybe spaces creep in due to loading font files / setups or so)
Thank you!
Yes, this works, and with rulethickness=0 it
p in due to loading font files / setups or so)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pra
Am 06.07.23 um 11:58 schrieb Alan Braslau:
Maybe it’s also a problem of \startdocument – I always get a first
empty page and don’t understand why.
One gets an empty first page if there is *any* text content anywhere in
the setups or environment files before the \startdocument.
My problem
ent – I always get a first empty
page and don’t understand why.
One gets an empty first page if there is *any* text content anywhere in
the setups or environment files before the \startdocument.
--
Alan
___
If
Hi,
if I use \startdocument, the setups "document:start" and "document:stop"
get inserted at the beginning and end. But if I define my own document,
it doesn’t work. What’s wrong?
"""
\definedocument[presentation]
\startsetups[presentation:start]
{\bfd\d
[file:LucidaBrightItalic]
> \definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold]
> \definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic]
> \stoptypescript
>
> \starttypescript [mylucidaserif]
> \setups[font:fallback:serif]
>
DemiItalic] [file:LucidaBrightDemiItalic]
\stoptypescript
\starttypescript [mylucidaserif]
\setups[font:fallback:serif]
\definefontsynonym[Serif][LucidaBrightRegular]
[features=default]
\definefontsynonym[SerifItalic] [LucidaBrightItalic]
[features=default]
\defi
more adaptive tricks (although I bet he can figure them out himself).
>
> \starttext
>
> % \setupexternalfigures
> % [location={default,global}]
>
> % \startsetups adaptive:test
> % \setbox\usedadaptivebox\hbox to \usedadaptivewidth yoffset
> -\usedadaptivedepth \bgroup
> %
idth,0)) randomized
(ExHeight/2);
\stopMPcode
\egroup
\stopsetups
\dorecurse{5}{
\dostepwiserecurse{1}{150}{1}{%
this~#1.##1 is~#1.##1 test~#1.##1
{\adaptivebox[strut=yes,setups=adaptive:test]{\strut}}
}
\blank
}
\stoptext
(2) If someone wants a plain (or
It's a tough problem for sure.
I'm wondering if there's a general solution?
That is, a way to tell ConTeXt to "protect the lettrine" regardless of the
source document text? Nothing can be hard-coded because the setups (take a
look at keenwrite themes
https://github
PM linguafalsa--- via ntg-context <
> ntg-context@ntg.nl> wrote:
>
> > On Tue, Jun 13, 2023 at 02:01:14PM -0700, Thangalin via ntg-context wrote:
> > > Thanks Otared,
> > >
> > > Unfortunately, that's adding content between \starttext and \stoptext,
&g
-context wrote:
> > Thanks Otared,
> >
> > Unfortunately, that's adding content between \starttext and \stoptext,
> > which isn't tenable in my situation. The user is writing in Markdown,
> which
> > is automatically converted to XHTML then passed to ConTeXt, and so t
d to XHTML then passed to ConTeXt, and so the
> setups need to account for this scenario without modifying the source
> document.
>
Yeah yeah yeah, tenable. A lot of things aren't tenable. Anyhow,
What source document are you talking about here?
You're already sourcing the line
at 2:01 PM Thangalin wrote:
> Thanks Otared,
>
> Unfortunately, that's adding content between \starttext and \stoptext,
> which isn't tenable in my situation. The user is writing in Markdown, which
> is automatically converted to XHTML then passed to ConTeXt, and so t
Thanks Otared,
Unfortunately, that's adding content between \starttext and \stoptext,
which isn't tenable in my situation. The user is writing in Markdown, which
is automatically converted to XHTML then passed to ConTeXt, and so the
setups need to account for this scenario without mod
he lettrine such that regardless
> of whether the first paragraph spans multiple lines, a short first paragraph
> will still prevent the second paragraph from overlapping the lettrine?
>
> That is, the setups should work in both cases, without any knowledge about
&
spans multiple lines, a short
first paragraph will still prevent the second paragraph from overlapping
the lettrine?
That is, the setups should work in both cases, without any knowledge about
the first paragraph length being added between \starttext and \stoptext.
ConTeXt LMTX version: 2023.06.04 1
Gerben Wierda via ntg-context 于2023年6月2日周五 19:37写道：
> For Japanese I currently use
>
> \startsetups [japanese]
> \setscript [nihongo]
> \stopsetups
> \setuplanguage [ja] [setups=japanese]
> \definefallbackfamily
> [archimate]
> [ss]
> [Hiragino Sans]
>
For Japanese I currently use
\startsetups [japanese]
\setscript [nihongo]
\stopsetups
\setuplanguage [ja] [setups=japanese]
\definefallbackfamily
[archimate]
[ss]
[Hiragino Sans]
[preset=range:japanese,
tf=style:W3,
it=style:W3,
bf=style:W5,
bi=style:W5,
force=yes
cause this behavior? For what should I look in my setups?
In this instances, location=opposite causes the float to disappear.
Hraban
___
If your question is of interest to others as well, please add an entry to the
t
\dorecurse{2}{\samplefile{tufte}}
\startplacefigure[location=page,title={Pagefloat}]
\framed[width=\textwidth,height=.5\textheight]{TEST}
\stopplacefigure
\dorecurse{5}{\samplefile{knuth}}
\stoptext
"""
What could cause this behavior? For what shoul
setupbodyfont[archimate]
>
> \startsetups [japanese]
> \setscript [nihongo]
> \stopsetups
> \setuplanguage [ja] [setups=japanese]
> \mainlanguage [ja]
>
> \starttext
> \setupindenting[none]
> \setupindenting[no]
> \framed[width=\textwidth,frame=off,align=flushleft]{作図
> [Hiragino Sans]
> [preset=range:japanese,
>tf=style:W3,
>it=style:W3,
>bf=style:W5,
>bi=style:W5,
>force=yes]
>
> \definefontfamily [archimate] [ss] [Optima]
>
> \setupbodyfont[archimate]
>
> \startsetups [japanese]
>
bi=style:W5,
force=yes]
\definefontfamily [archimate] [ss] [Optima]
\setupbodyfont[archimate]
\startsetups [japanese]
\setscript [nihongo]
\stopsetups
\setuplanguage [ja] [setups=japanese]
\mainlanguage [ja]
\starttext
\setupindenting[none]
\setupindenting[no]
\framed[width=\textwidth,fram
empty,
footerstate=empty,
setups={toclist},
before=\setups{toc:setups},
]
\startsetups toc:setups
\setupbackgrounds[page][background=color, backgroundcolor=blue]
\stopsetups
\definemakeup
[standard]
[
doublesided=no,
page=right,
pagestate=start,
headerstate=
de [JA]
\setscript [nihongo]
\mainlanguage [ja]
\stopmode
but for documents which use multiple script/languages at the same time
replace the previous setup with
\startsetups [japanese]
\setscript [nihongo]
\stopsetups
\setuplanguage [ja] [setups=japanese]
a
site but to collect code in a
place where we could gradually fix possible errors or introduce improvements.
This can be done on the wiki as well.
I agree that it makes most sense to keep examples and (font) setups in
the wiki.
Projects with several files, like modules, should have their own
4.23 um 23:36 schrieb jbf via ntg-context:
I tried all those Hraban, unsuccessfully, but finally 'happened' upon
a solution by trying whitespace instead in the setups. Except that I
had read somewhere in the mailing list (Pablo I think) that I would
need to use \directsetup. I don'
Am 23.04.23 um 23:36 schrieb jbf via ntg-context:
I tried all those Hraban, unsuccessfully, but finally 'happened' upon a
solution by trying whitespace instead in the setups. Except that I had
read somewhere in the mailing list (Pablo I think) that I would need to
use \directsetu
I tried all those Hraban, unsuccessfully, but finally 'happened' upon a
solution by trying whitespace instead in the setups. Except that I had
read somewhere in the mailing list (Pablo I think) that I would need to
use \directsetup. I don't actually understand why, have never b
I tried all those Hraban, unsuccessfully, but finally 'happened' upon a
solution by trying whitespace instead in the setups. Except that I had
read somewhere in the mailing list (Pablo I think) that I would need to
use \directsetup. I don't actually understand why, have never b
=2.4ex]
\stopsetups
\setupnote[footnote][setups=footnote:interlinespace]
but it doesn't. I had hoped there might be something like
\setuplocalfootnotes but there is not. I also tried placing the setups
locally, either with
\startlocalfootnotes[setups=footnote:interlinespac
style={\switchtobodyfont[roboto-flex,20pt]\ss}]
While the Garamond is embedded and text is styled, the chapter tible is
typeset with Garamond not Roboto.
Any hints or feed back will be very appriciated.
\usetypescriptfile[ebgaramond]
\starttypescript [sans] [robotoflex]
\setups[font:fallback
experimenting to get a simple workflow for the conversion of docx
> files to simple (x)html files.
>
> Thanks again for the code.
>
> Best Wishes
>
> Keith
>
> On 12/04/2023 09:05, denis.ma...@unibe.ch wrote:
> > Hey Keith,
> >
> > the code below shoul
't
appear as there are no setups for the elements yet.
By the way, where is the HTML coming from? The dual structure for footnotes
looks a bit odd and a bit too complicated for me.
==
\startxmlsetups xml:initialize
\xmlsetsetup{\xmldocument}{*}{
Hey Keith,
the code below should get you started. Obviously, the links in the footnotes
don't appear as there are no setups for the elements yet.
By the way, where is the HTML coming from? The dual structure for footnotes
looks a bit odd and a bit too complicated f
Hard to tell, if you don't show us what you've tried so far.
In one of my setups I use the lua based approach described on page 86/87. But
again, we'll probably need more information to figure it out.
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von
Fair comment Denis.
I decided to try the lookup based approach on pages 85 - 86 of the xml
manual and my setups are based on those pages. I have to admit that I
find the xml manual a wee bit difficult in places since xml is outside
my expertise. I attach my tex and html files which should
\setuppapersize[A4]
\starttypescript [serif] [myfont]
\setups[font:fallback:serif]
\definefontsynonym [Serif] [name:palatinoltstdlight] [features=default]
\definefontsynonym [SerifItalic] [name:palatinoltstdlightitalic]
;
> > and not with the file specification as in:
> >
> >
> > \starttypescript [mylucidaserif] % or mylucidasans
> >\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
> >\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic
onym[LucidaBrightItalic] [file:LucidaBrightItalic]
\definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold]
\stoptypescript
and \setups[font:fallback:serif:sans] wouldn't be needed either
you'd end up with
in mkxl (lmtx)
\setupbodyfont[lucida]
will load open type defin
t [mylucidaserif] % or mylucidasans
\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
\definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold]
\stoptypescript
and \setups[font:fallback:serif:sans] wouldn&#
e.
All intermediate rows have gray.
I have no difficulty achieving the first row, and the black
bottomframe for the last row, but I have been unable to get the last
row sides to be gray. Here is the current setups that I have:
\setupTABLE[frame=off]
\setupTABLE[row] [first] [topfram
k frame. All intermediate
> rows have gray.
> I have no difficulty achieving the first row, and the black bottomframe for
> the last row, but I have been unable to get the last row sides to be gray.
> Here is the current setups that I have:
> \setupTABLE[frame=off]
> \setupTABLE[row
gray.
I have no difficulty achieving the first row, and the black bottomframe
for the last row, but I have been unable to get the last row sides to be
gray. Here is the current setups that I have:
\setupTABLE[frame=off]
\setupTABLE[row] [first] [topframe=on,bottomframe=on,style=bold]
\setupTA
w, and the black bottomframe
for the last row, but I have been unable to get the last row sides to be
gray. Here is the current setups that I have:
\setupTABLE[frame=off]
\setupTABLE[row] [first] [topframe=on,bottomframe=on,style=bold]
\setupTABLE[row][2][topframe=on]
\setupTABLE[row][2][to
what I
> > get for trying to write readable code.
> >
> You can use the = to align keys and values, e.g.
>
> \setuplayout
>[backspace=2.5cm,
>margin=0.5cm,
> width=16cm,
>header=1cm,
>footer=1cm]
>
> Another useful metho
r=1cm,
footer=1cm]
Another useful method is to put large settings into a setups-blocks and
pass the block to a setup-command.
\startsetups [apage]
\startMPcode
StartPage;
...
StopPage;
\stopMPcode
\stopsetups
\defineoverlay[apage][\directsetup{apage}]
Wol
s, some positioning keys had not the intended effect
> > > (e.g. top), «page» moved the float more than seemed necessary for
> > > me... I know, TeX’s float positioning algorithm should be rather
> > > reliable and stable, and it’s quite possible that I’m messing things
>
y hints how I could debug that issue?
As I'm again working with XML files: Is it possible that this behaviour is
caused by some sort of nested setups which makes the footnotes not bubble up?
Best,
Denis
\startbuffer[test]
a2
b
y for extreme tables. Is
that correct?
I'll try to narrow it down. Any hints how I could debug that issue?
As I'm again working with XML files: Is it possible that this behaviour is
caused by some sort of nested setups which makes the footnotes not bubble up?
Best,
Denis
\s
algorithm should be rather
> > reliable and stable, and it’s quite possible that I’m messing
> > things up in my setups–especially since my source files are XML.
> >
> > Anyway, I’d like to learn more about the whole float issue. Is
> > there anything particular I could
positioning keys had not the intended effect (e.g. top), «page»
moved the float more than seemed necessary for me... I know, TeX’s float
positioning algorithm should be rather reliable and stable, and it’s
quite possible that I’m messing things up in my setups–especially since
my source files
it up at weird points, some
> positioning keys had not the intended effect (e.g. top), «page» moved the
> float more than seemed necessary for me... I know, TeX’s float positioning
> algorithm should be rather reliable and stable, and it’s quite possible that
> I’m messing things up in my
. top), moved the float more than
seemed necessary for me... I know, TeX's float positioning algorithm should be
rather reliable and stable, and it's quite possible that I'm messing things up
in my setups-especially since my source files are XML.
Anyway, I'd like to learn more ab
ge in footer
==
I tried placing that all into a macro called "\introduction" then
calling with this
\setupheadertexts[\introduction]
Better use setups instead of a macros, like in
https://wiki.contextgarden.net/Headers_and_Footers
In setups, you must use explicit space commands, sin
lucidacasual normal normal normal normal lucidacasual
/home//.fonts/LucidaCasual.ttf
Then the following code should work :
\starttypescript [myserif]
\definefontsynonym[LucidaCasual-Regular] [file:LucidaCasual.ttf]
\stoptypescript
\starttypescript [myserif]
\setups
m your error message (\currentbtxloctext) seems
to be defined in four setups from tex/publ-imp-sbl.mkvi:
\def\currentbtxloctext{\btxparameter{loctext}}
The setups containing the definitions are btx:sbl:cite:inlinelong,
btx:sbl:cite:inlineshort, btx:sbl:cite:inline and btx:sbl:cite:shorthand.
You
\stopsetups
\setuphead[chapter]
[style=\tfa,
after={\blank\setups{chapter:headings}},
]
\starttext
\startchapter[title=Nothing special]
\dorecurse{10}{\input knuth\par}
\stopchapter
\startchapter[title=Something special][custom={Hi there!}]
\do
: Freitag, 16. Dezember 2022 11:01
An: mailing list for ConTeXt users
Cc: Pawel Urbanski
Betreff: Re: [NTG-context] Project structure with nested subfolders and shared
environments.
Thank you for responses. While the ability to sort of inherit setups would be
very useful it looks like as of
Thank you for responses. While the ability to sort of inherit setups would
be very useful it looks like as of time of posting this message in December
2022 it is not possible.
As a workaround I will create a shead environment file and just bulk copy
it to subfolders. In case when I'll ne
ise (this was fairly easy,
should have seen it earlier):
instead of loading the file "examples.xml," I simply include it via
xmlinclude into the tree; this way the proper setups are applied.
All best
Thomas
chapter:example")
or
xml.sprint (lxml.id (current_example))
or
local problem = xml.text (lxml.id (current_example), "./[text()]")
xml.sprint (problem)
I was expecting at least the last version to retrieve the pure text, but
it typesets again with the tags included.
So I gues
Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06:
On 11/15/22 13:22, Denis Maier via ntg-context wrote:
Hi,
if I process an XML buffer, I’ve noticed I need to wrap the
\xmlprocessbuffer in a \starttext ... \stoptext pair.
[]
However, if I have the XML and the setups in dedicated
Denis Maier via ntg-context schrieb am 15.11.2022 um 13:22:
Hi,
if I process an XML buffer, I’ve noticed I need to wrap the
\xmlprocessbuffer in a \starttext ... \stoptext pair.
[...]
However, if I have the XML and the setups in dedicated files, there
seems to be no need for \starttext
d implicit \starttext ...
> \stopttext
>
> On 11/15/22 13:22, Denis Maier via ntg-context wrote:
> > Hi,
> >
> > if I process an XML buffer, I’ve noticed I need to wrap the
> > \xmlprocessbuffer in a \starttext ... \stoptext pair.
> > []
> > However, if I have the XM
On 11/15/22 13:22, Denis Maier via ntg-context wrote:
> Hi,
>
> if I process an XML buffer, I’ve noticed I need to wrap the
> \xmlprocessbuffer in a \starttext ... \stoptext pair.
> []
> However, if I have the XML and the setups in dedicated files, there
> seems to be n
e XML and the setups in dedicated files, there seems to be
no need for \starttext ... \stoptext.
%%% text.xml
a paragraph of text
another paragraph of text
%%%
%%% setups.tex
\startxmlsetups xml
document id. There is
also \xmlself which expands to the current node number (#1 in setups).
Now I think that I have abused \xmldocument too much, since I should
have used #1. But I’m afraid I haven’t got much different results.
I must also confess that a proper explanation would be helpful (to me
t id. There is
also \xmlself which expands to the current node number (#1 in setups).
Now I think that I have abused \xmldocument too much, since I should
have used #1. But I’m afraid I haven’t got much different results.
I must also confess that a proper explanation would be helpful (to me in
ord
'sequence')
\starttypescriptcollection[myfonts]
% Mono - iosevka (Iosevka SS09 — Terminal, Hinted)
% Source: https://github.com/be5invis/Iosevka/blob/v16.3.6/doc/PACKAGE-LIST.md
\starttypescript [mono] [iosevka] [name]
\setups[font:fallback:mono]
\definefontsynonym [Mono][fi
?
In my "real work" layout, the above approach was not always possible.
I looked into “TeX by topic”, but Eijkhout shows only how to use
\multiply and \advance. (Tried that, worked only partly.)
I was also thinking about doing the whole thing in Lua (CLD), but it’s
mostly setups, and
me effort going on to turn them opentype so we can ditch their setups
too (we can't test anyway; to some extend that is also true for minion
math).
High on the agenda is euler (in combination with pagella). This also
relates to upgraded mixed script and calligraphic support in math. It
le to define 'lato-regular' as
'lato-12pt-ss-tf-0--0'
---
If I change the file: reference I get it working with both MKIV/LMTX:
\starttypescript [\s!sans] [lato] [\s!name]
\setups[\s!font:\s!fallback:\s!sans]
% \definefontsynonym [\s!Sans] [\
book that doesn't have to be heavily modified in
> order to become a physical book? I want almost no modification at all.
I think you can use modes: https://wiki.contextgarden.net/Modes.
Simply do different setups in different modes. Then choose t
welcome.
hm, i can have a look at it but we shouldn't break japanese and korean
once you finished all we can see how it can either be integrated or
become some third party module (has to do with maintainance)
can you also make a noto typescript for the different chinese setups
(for some re
operators into the
new line:
\setupmathematics[setups=math:spacing:split]
\setupformulas[split=yes,align=flushleft]
\startformula
x\dorecurse{30}{ + #1x^{#1x}} = 10
\stopformula
Would it be possible to achieve this via a custom setup like
math:spacing:split to get an output like this?
𝑥 + 1𝑥1𝑥
Hi,
Since there has been a lot of work done on the math side of things, I
wanted to ask if there is an automated way to have binary operators
repeated when splitting a formula.
From the MKIV math manual there is an option to move the operators into the
new line:
\setupmathematics[setups
ion is something like this :
- How could a painless solution for such a scenario look like?
- Should you just load multiple environment files and override earlier
settings? (How would that work with xml setups?)
Best,
Denis
___
Good point, Wolfgang.
The Markdown is translated to XHTML then typeset as XML using the setups
listed here:
https://github.com/DaveJarvis/keenwrite-themes/tree/main/xhtml
Having an XML string replacement solution would be great. I suppose that
would help prevent substitutions within pre and code
Am 26.07.22 um 12:41 schrieb Bruce Horrocks via ntg-context:
If I use \definehead [Chapter] [chapter] and then \setuphead[Chapter][...] I
can specify setups to run before and after \startChapter.
Is there any way to specify setups that are run before & after \stopChapter?
\setuphead[Cha
If I use \definehead [Chapter] [chapter] and then \setuphead[Chapter][...] I
can specify setups to run before and after \startChapter.
Is there any way to specify setups that are run before & after \stopChapter?
My real problem is that I have a double-sided book with new chapters starting
1.png][png][#2]%
}{% \old_externalfigure[#1][#2][#3]% }% }% } \protect |
See: https://tex.stackexchange.com/a/650221/2148
I was wondering if there was a simpler or a solution that's more the
ConTeXt-way?
When you use XML as input you can add additional code to the setups block
, etc. citations; for the
purposes of your MWE (and for most citations) a righttext with the page
number citation should also work just fine, so the lack of a loctext
parameter in the \cite command shouldn't be a problem. The
\currentbtxloctext macro is defined in most of the btx:sbl:cite setup
erent external figure setups based on image type?
Thank you!
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinf
tium]
\definefontfallback
[alegreyagentium-fallback]
[name:gentium]
[greekandcoptic,greekextended]
\starttypescript [serif]
[alegreya-serif,alegreya-light-serif,alegreya-medium-serif] [name]
\setups[font:fallback:serif]
\definefontsynonym[Serif] [name:alegreyaregular]
[features=def
se for Greek characters (I guess
> ‘greekandcoptic’ which I’ve seen mentioned somewhere).
>
> Correct?
Hi Gerben,
\language[gr], but beware since it uses patterns for ancient Greek.
preset=range:greek is what you intend.
Another approach would be to use \setuplanguage[gr] and confi
101 - 200 of 1009 matches
Mail list logo
