skutočne nepreložiteľný), snažia dorozumievať
sa v angličtine?
Será por isso que os europeus, apesar de tão orgulhosos da sua
própria língua (realmente intraduzível), procuram fazer-se entender
em inglês?
To pewnie dlatego Europejczycy, mimo że są tak dumni ze swojego
języka (który na
k (ktorý je skutočne nepreložiteľný), snažia dorozumievať sa v
angličtine?
Será por isso que os europeus, apesar de tão orgulhosos da sua própria
língua (realmente intraduzível), procuram fazer-se entender em inglês?
To pewnie dlatego Europejczycy, mimo że są tak dumni ze swojego języka
(który
ους (η οποία είναι πραγματικά αμετάφραστη),
> προσπαθούν να επικοινωνούν στα αγγλικά.
>
> Je to snáď dôvod, prečo sa Európania, ktorí sú tak hrdí na svoj vlastný
> jazyk (ktorý je skutočne nepreložiteľný), snažia dorozumievať sa v
> angličtine?
>
> Será por isso que os europeus,
ν στα αγγλικά.
Je to snáď dôvod, prečo sa Európania, ktorí sú tak hrdí na svoj vlastný
jazyk (ktorý je skutočne nepreložiteľný), snažia dorozumievať sa v
angličtine?
Será por isso que os europeus, apesar de tão orgulhosos da sua própria
língua (realmente intraduzível), procuram fazer-se entend
ntent=webmail>
<#m_-8229328929494425726_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sun, 6 Jul 2025 at 17:12, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:
> Am 06.07.2025 um 16:19 schrieb John Was:
> > Hello
> >
> > Is there a way in ConTeX
Am 06.07.2025 um 16:19 schrieb John Was:
Hello
Is there a way in ConTeXt to allow line-breaking by default after an en
or em dash (-- or ---)? The equivalent of \XeTeXdashbreakstate=1
I couldn't see anything after trying various searches.
Conversely, is there a way of inhibiting Co
On 7/6/2025 4:19 PM, John Was wrote:
Hello
Is there a way in ConTeXt to allow line-breaking by default after an en
or em dash (-- or ---)? The equivalent of \XeTeXdashbreakstate=1
I couldn't see anything after trying various searches.
Just try:
\starttext
\hsize1mm
test-tes
Hello
Is there a way in ConTeXt to allow line-breaking by default after an en or
em dash (-- or ---)? The equivalent of \XeTeXdashbreakstate=1
I couldn't see anything after trying various searches.
Conversely, is there a way of inhibiting ConTeXt from hyphenating an
already hyphe
t the correct placement of the macron?
> >
> > Best,
> >
> > Denis
> >
> > %%%%
> >
> > \definefontfamily[cardo][rm][Cardo]
> >
> > \setupbodyfont[
> >
> > mainface,
> >
> >
ght. How can I get the correct placement of the macron?
Best,
Denis
\definefontfamily[cardo][rm][Cardo]
\setupbodyfont[
mainface,
11pt,
]
\starttext
{\em ḵabc} (with macron)
{\em ḵabc} (with combining macron)
\switchtobodyfont[ca
,
]
\starttext
{\em ḵabc} (with macron)
{\em ḵabc} (with combining macron)
\switchtobodyfont[cardo]
{\em ḵabc} (with macron)
{\em ḵabc} (with combining macron)
{ḵabc} (with combining macron)
\stoptext
,
11pt,
]
\starttext
{\em ḵabc} (with macron)
{\em ḵabc} (with combining macron)
\switchtobodyfont[cardo]
{\em ḵabc} (with macron)
{\em ḵabc} (with combining macron)
{ḵabc} (with combining macron)
\stoptext
on=default,
authorconversion=normal]
\definebtxdataset[default]
\definebtx[default:cite]
[default=,
specification=default,
separator:2={ and },
otherstext={\btxspace\em{et al.}},
etallimit=3,
]
\definebtx[default:c
On 2025-03-20 18:29, jbf wrote:
At least for the Index, Joel, here is how I achieved that:
\defineprocessor[special][style=italic]
And then by way of an example in the text referring to a newspaper:
\index{special->Age, The} {\em The Age} of 31 July 2018
Julian
On 21/3/25 03:28, Joel
At least for the Index, Joel, here is how I achieved that:
\defineprocessor[special][style=italic]
And then by way of an example in the text referring to a newspaper:
\index{special->Age, The} {\em The Age} of 31 July 2018
Julian
On 21/3/25 03:28, Joel via ntg-context wrote:
Its com
Am 04.02.2025 um 19:12 schrieb Rik Kabel:
On 2025-02-04 11:59, Hans Hagen wrote:
Hi,
NOTA BENE:
The next upload is kind of special so best save the old tex tree if
you update.
Indeed. The following
\normalizefontwidth \FontA {ABCDEF} {\textwidth} {SerifItalic}
\starttext
\
the first sentence in the demonstration.\\
{\em Then} the next sentence in the paragraph follows.\\
You can see that the italic {\em T} appears to be a bit indented.\\
{\em There } might be a way to shift it to the left that little bit.\\
Perhaps a protrusion setting.\\
{\em This} does appear to depend
]
[default]
[protrusion=quality,expansion=quality]
\setupalign [hz,hanging]
\startbuffer
Here is a line of text, the first sentence in the demonstration.\\
{\em Then} the next sentence in the paragraph follows.\\
You can see that the italic
and/or add the number of items to be expected:
\starttexdefinition protected thisiymylist [#1]
\getcommalistsize[#1]
\doifelse{\commalistsize}{1}
{Read the prompt below:\par}
{Read {\em all} the \the\numexpr \commalistsize -1\relax\ prompts
below:\par}
\startitemize[n
ears in my code:
\startxtable[option=stretch, align={middle,lohi}, frame=off, distance=0.5em]
\startxrow
\startxcell \em Ambrosianus\footnote{Cf.
\cite[alternative=entry][Bibliography::mai1]} \stopxcell
\stopxrow
\stopxtable
All preliminary declarations into the file are made correctly, as is the
\setupheadertexts[section][pagenumber][pagenumber][chapter]
\mainlanguage[en]
Not necessary because english is the default language.
\setupbodyfontenvironment [default][em=italic]
Not necessary for charter because there is only a italic style, you need
this only for fonts which have an italic and slant
page numbers enabled? This would enabled /See also/
entries to be generated with something like
\setregisterentry[TopicIndex][keys:2=zzz,entries:1=punctuation,entries:2={{\em
See also} marking}]%
I do see that there is an alternative key defined for the command,
but no explanation of what the
start]
\setupheadertexts[section][pagenumber][pagenumber][chapter]
\mainlanguage[en]
\setupbodyfontenvironment [default][em=italic]
\definefontfeature[default][default][fakecombining=yes,compose=yes,itlc=yes,protrusion=quality,expansion=quality,onum=yes]
\setupbodyfont[xcharter,10pt]
\setupali
=punctuation,entries:2={{\em
See also} marking}]%
I do see that there is an alternative key defined for the command, but
no explanation of what the alternatives are and if any would help.
You have to set "ownnumber=yes" but I don't think the feature is
supported at the moment
Hello experts,
Is there a way to generate an entry without a page number in an register
that has page numbers enabled? This would enabled /See also/ entries to
be generated with something like
\setregisterentry[TopicIndex][keys:2=zzz,entries:1=punctuation,entries:2={{\em
See also
ouldn't be necessary to add "itlc" anymore to get italic correction
for \em etc.
is there some stuff like the extrafeatures option or anything that you would
recommend i enable? might there be options for extrakerns that would be seen as
something that one should enable?
also,
> is slanted), such as in:
>
> \setupbodyfontenvironment [default] [em=italic]
>
> \define\somename{HX{\em print}\autoinsertnextspace}
>
> I hope it helps,
>
> Pablo
Thank you, that works for the minimal example and in my case but has the side
effect t
ll ConTeXt to combine them, so that it is bold
> _and_ italic?
Hi Gerion,
you may combine emphasis with bold and set emphasis to italic (default
is slanted), such as in:
\setupbodyfontenvironment [default] [em=italic]
\define\somename{HX{\em print}\autoinsertnextspace}
ys:" means?
> Italic correction is fixed (for \/ and \italiccorrection) but there hasn't
> been a new context release since then.
> The \em variant didn't work because it inserts \/ (which was broken) at the
> end of the text.
Thanks Wolfgang.
I rea
ever, since the second two don't work, can anyone speculate as to what I
might be doing wrong? Or, did I somehow misinterpret what "There are three
ways:" means?
Italic correction is fixed (for \/ and \italiccorrection) but there
hasn't been a new context release since
In short, I cannot seem to produce italic correction like I could in
>> plain TeX or even LaTeX.
> There are three ways:
> the{\sl air\/}port
> the{\em air}port
> the{\sl\shapecorrection[right]air}port
> % shape correction can be left right both
> the first one doesn
d after some initial testing I
> > noticed an unexpected behavior regarding italic correction.
> >
> > In short, I cannot seem to produce italic correction like I could in plain
> > TeX or even LaTeX.
>
> There are three ways:
>
> the{\sl air\/}port
>
> t
.
There are three ways:
the{\sl air\/}port
the{\em air}port
the{\sl\shapecorrection[right]air}port
% shape correction can be left right both
the first one doesn't work but is fixed in next upload (sometime this week)
On 8/25/2024 2:15 PM, Wolfgang Schuster wrote:
How differs "1" from "2"?
* em fs
\startbuffer[dimensions]
\starttabulate
\NC em \EQ \the\dimexpr1em\relax \NC\NR % \emwidth
\NC fs \EQ \the\dimexpr1fs\relax \NC\NR % \globalbodyfontsize
\stoptabulate
\stopbuffer
\s
I didn’t guess “registers”
was relevant.
Questions:
How differs "1" from "2"?
* em fs
\NC em \EQ \the\dimexpr1em\relax \NC\NR % \emwidth
\NC fs \EQ \the\dimexpr1fs\relax \NC\NR % \globalbodyfontsize
Ok, so they can differ minimally; in my 10pt setup I get the same v
Henning Hraban Ramm schrieb am 25.08.2024 um 13:45:
At the meeting I noted a few units that I didn’t know about, while I
already knew many.
* general units: in, m, cm, mm (ft?)
* typographical units: pt, dd, bp, pc, cc, sp
* font related: em, ex, fs, fa, fd, fc, ch
* layout related: pw, ph, tw
At the meeting I noted a few units that I didn’t know about, while I
already knew many.
* general units: in, m, cm, mm (ft?)
* typographical units: pt, dd, bp, pc, cc, sp
* font related: em, ex, fs, fa, fd, fc, ch
* layout related: pw, ph, tw, th, cw, cd, lw, hs, vh
* frame related: fw, fh, fo
On 5/27/24 19:10, Kip Warner wrote:
> [...]
> Thanks Wolfgang. I gave it a try on https://context-on-web.eu/, but it
> failed:
>
>Dimensions can be in units of em, ex, in, pt, pc, cm, mm, dd, cc,
>bp, dk, or54sp; but yours is a new one! I'll assume that you me
round,
radius=.5fw,
offset=none]
\starttext
\dostepwiserecurse{0}{9}{1}{#1 = \textcircled{#1}\blank}
\stoptext
Thanks Wolfgang. I gave it a try on https://context-on-web.eu/, but it
failed:
Dimensions can be in units of em, ex, in, pt, pc, cm, mm, dd, cc,
bp, dk, or54sp; but yours
; radius=.5fw,
> offset=none]
>
> \starttext
> \dostepwiserecurse{0}{9}{1}{#1 = \textcircled{#1}\blank}
> \stoptext
Thanks Wolfgang. I gave it a try on https://context-on-web.eu/, but it
failed:
Dimensions can be in units of em, ex, in, pt, pc, cm, mm, dd, cc,
bp, dk
([[\luaescapestring{#1}]])}}
\PrintTheThing{a \em b {c}}
\stoptext
I wonder whether there is a proper way in the Lua code to avoid
[[\luaescapestring{}]] in \ctxlua.
BTW, [[\luaescapestring{}]] in \ctxlua works better for me, since in my
real world document, I’m using str:match() to check
Dear list,
I have the following sample:
\starttext
\startluacode
function document.print_the_thing(str)
context(str)
end
\stopluacode
\unexpanded\def\PrintTheThing#1{%
\ctxlua{document.print_the_thing([[\luaescapestring{#1}]])}}
\PrintTheThing{a \em b {c}}
\stoptext
I
On 4/6/2024 1:38 PM, Wolfgang Schuster wrote:
Henning Hraban Ramm schrieb am 06.04.2024 um 12:23:
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type
tree hyphens. If I use the command \emdash, no p
Henning Hraban Ramm schrieb am 06.04.2024 um 12:23:
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type
tree hyphens. If I use the command \emdash, no problem but when I use
the hyphens some day
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type tree
hyphens. If I use the command \emdash, no problem but when I use the hyphens
some days it works... and somedays I see three small hyphens.
I t
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type tree
hyphens. If I use the command \emdash, no problem but when I use the hyphens
some days it works... and somedays I see three small hyphens.
I tried it on overleaf and of ContextOnWeb with the same inc
.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The
[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The only way to mask the effect is to create a new
umulate, like
> [...]
> which you will now wikify...
Many thanks for your reply, Hans.
I will wikify this, once I figure out where it can fit in the wiki (in
due time, since ConTeXt is more and more complex for me lately and my
free time is less and less these days).
I only used \enableexpe
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by def
On 3/9/24 16:04, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
>> [...]
>>\enableexperiments[fonts.compact]
>>
>> Which seeems weird to me. Or at least, I thought I read that Hans
>> enabled it by default in LMTX.
>
> AFAIR Hans uses the setting in h
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which i
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected output.
Sorry, my LuaTeX is getting
={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only
=doublesided, location={header, inmargin}]
\setupmargindata[inmargin][location=inner,
style={\ssx\setupinterlinespace[line=2.8ex]}]
\setupmarginframed[inmargin][align=right]
\setupbodyfontenvironment[default][em=italic]
% Use Theano Didot as Ancient Greek font
\definefallbackfamily[mainface][serif
(see
> > https://www.w3.org/TR/jlreq/#possibilities_for_linebreaking_between_character
> > ) and eventually more, which I didn't test.
> > It might be useful to define three scripts nihongo_loose, nihongo_strict
> > and nihongo_very_strict which each implement one o
ing_between_character
> ) and eventually more, which I didn't test.
>
> It might be useful to define three scripts nihongo_loose, nihongo_strict
> and nihongo_very_strict which each implement one of the 3 cases described
> here: https://www.w3.org/TR/jlreq/#addendum_a
>
&
x27;t test.
>
> It might be useful to define three scripts nihongo_loose, nihongo_strict and
> nihongo_very_strict which each implement one of the 3 cases described here:
> https://www.w3.org/TR/jlreq/#addendum_a
>
> According the line gap (Otared uses \setupwhitespace[big]
://www.w3.org/TR/jlreq/ :
/It is common that the line gap for the kihon-hanmen is set to a value
between half-em spacing and the one em spacing of the character frame
used for the kihon-hanmen. Half-em spacing can be chosen in cases
where the line length is short, but one em spacing or close
quote from https://www.w3.org/TR/jlreq/ :
It is common that the line gap for the kihon-hanmen is set to a value between
half-em spacing and the one em spacing of the character frame used for the
kihon-hanmen. Half-em spacing can be chosen in cases where the line length is
short, but one em spacin
=40mm]
\setuppagenumbering[alternative=doublesided, location={header, inmargin}]
\setupmargindata[inmargin][location=inner,
style={setupinterlinespace[line=2.8ex]}]
\setupmarginframed[inmargin][align=right]
\setupbodyfontenvironment[default][em=italic]
\definefallbackfamily[mainface][rm][Theano
[rm]
[TeX Gyre Pagella]
\setupbodyfont[mainface, 11pt]
\setupbodyfontenvironment[default][em=italic]
\starttext
Socrate est descendu au Pirée et affirme sa satisfaction du culte rendu Ã
cette nouvelle déesse par les Thraces; néanmoins, {\em il ne nous dit rien
des prières} qu'il a
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspaci
n ex and
> horizontal spaces in em; maybe it's not widely accepted).
As far as I know, em is defined by the width of the capital 'M' and ex
is defined by the height of the lowercase 'x'.
With your requirements, I think it is easier to set line spacing to one
and a ha
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspaci
somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing of wordprocessors to be sure it is not
such different.
Sorr
ng a style description like /em/, /\em/, /bf/, /\bf/,
/\sc,/ does produce the suggested result. The wiki and mail repository
are full of examples with the former style names.
Using /style=cap/ (which would change the number as well) also results
in a failed compilation, while using /style=bolditalic/ w
iki
(https://wiki.contextgarden.net/Commands_with_optional_arguments).
It seems that the command has to be defined as unexpanded, such as in:
\setupinteraction[state=start]
\setupattachments[method=hidden]
\usemodule[database]
\starttext
\unexpanded\def\ItemContents#1#2#3{\doiftext{#2}
uals/bidi.pdf";
"Flowcharts","charts-mkiv.pdf",
Faking a command such as \cA, \cB and \cC (for contents of columns A, B
or C) I would like to create a source document with an enumeration that
contains:
\doiftext{\cB}
{\item {\em\cA}\attachment[file=\cB]%
\doift
his):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
\setupbodyfont
[mainface, 100pt]
\starttext
\startTEXpage[offset=1ex]
a {\em b}
\stopTEXpage
\stoptext
Many thanks for your help again,
Pablo
][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX
:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not
]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
Many
Mikael, Wolfgang:
This is in reference to the prior
Re: redefine space to be the same as \␣ similar to knuthian approach
> Maybe your system is broken?
>
> >
> > > 2. The example below results in a correct output for \TEX.
> > >
> >
> > Not in my end with any font other than latin modern
>
ollowing for a notes chapter at the end of a book. It
produces headings that indicate the pages for which the notes apply.
Perhaps you can adapt it to your needs:
In the environment file:
\definemarking [notePage] \startsetups noteHeadingsText {\em
Notes for page
\doifelse
kday,{ },day,{
},month,{ },year] a les \currenttime, usant programari lliure
(\goto{\Context}[url(http://wiki.contextgarden.net)] versió
\contextversionnumber, \goto{\texenginename}[url(http://www.luatex.org)] versió
\texengineversion\space i \goto{PGF/Ti{\em
k}Z}[url(http://sourceforge.net/projects/pgf/)
ramari lliure
(\goto{\Context}[url(http://wiki.contextgarden.net)] versió
\contextversionnumber, \goto{\texenginename}[url(http://www.luatex.org)] versió
\texengineversion\space i \goto{PGF/Ti{\em
k}Z}[url(http://sourceforge.net/projects/pgf/)]) sota un entorn
\goto{GNU/Linux}[url(https://www.linuxfounda
f 02BE and 02BF (ʿ ʾ). So we still need something like
\defineactivecharacter ʿ {\high{c}}
\defineactivecharacter ʾ {\kern.07 em
\high{\rotate[rotation=180,location=high]{c}}}
or better
\definecharacter ʿ {\high{c}}
\definecharacter ʾ {\kern.07 em \high{\rotate[rotation=180,location=high]{c}}}
T
On Fri, 19 May 2023, Jeroen via ntg-context wrote:
> Many thanks. Is there a proper way to add some space (a couple of pt or em)
> to the left and the right of the text itself so the frame does not get so
> close to the text?
\framed[loffset=0.2ex, roffset=0.2ex]{...}
Also s
Many thanks. Is there a proper way to add some space (a couple of pt or em)
to the left and the right of the text itself so the frame does not get so
close to the text?
Op vr 19 mei 2023 om 14:10 schreef Wolfgang Schuster via ntg-context <
ntg-context@ntg.nl>:
> Jeroen via ntg-context s
ns] (see: Not-so-short Intro to ConTeXt (J.
>>> Ataz-Lopez;English, page 114))
>>> • $ mtxrun (mtxrun is the ConTeXt TDS Runner Tool) command from a
>>> terminal window it has has a large number of options for finding the fonts
>>> installed, and for queryi
ptions for finding the fonts
>> installed, and for querying their characteristics (see: Fonts out of ConTeXt
>> (Hans Hagen, pg 52 and ff))
>> Em
>>
>> On 2023-04-25 08:50, Werner Schmidt via ntg-context wrote:
>> Hi conTeXt folks,
>>
>> may I ask ag
Xt (_J.
> Ataz-Lopez;English, page 114))
> * $ MTXRUN (mtxrun is the _ConTeXt TDS Runner Tool_) command from a
> terminal window it has has a large number of options for finding the fonts
> installed, and for querying their characteristics (SEE: _Fonts out of ConTeXt
> _(Hans Hagen
fonts installed, and for querying their characteristics (SEE: _Fonts out
of ConTeXt _(Hans Hagen, pg 52 and ff))
Em
On 2023-04-25 08:50, Werner Schmidt via ntg-context wrote:
> Hi conTeXt folks,
>
> may I ask again. How could I debug the font typesetting of PDF files with
> conTeXt?
&
rline},
translators={foo,bar,baz}
]
{\em authors} \\
\commalistsentence[\structureuservariable{authors}][{ \crlf },{ \crlf }]
{\em translators} \\
\processcommacommand[\structureuservariable{translators}]\dosomethingtwo
\doloopoverlist {\structureuservariable{translators}} {
(#1) \\
}
\stopchapter
\sto
>
> This will be the content of the second chapter.
>
>
>
>
> \stopbuffer
>
> \startxmlsetups xml:testsetups
> \xmlsetsetup{#1}{*}{-}
> \xmlsetsetup{#1}{document|chapters|chapter|content|emph}{xml:
> *}
> \stopxmlsetups
\startxmlsetups xml:chapter
\xmlfunction {#1} {chapter}
%\xmlflush {#1}
\stopxmlsetups
\startxmlsetups xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.funct
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.functions.chapter (t)
local ch_id = t.at.ch:id
local ch_id = t.at["ch:id"]
local metadata = xml.filter (t,
'../../topics/t
xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.functions.chapter (t)
local ch_id = t.at.ch:id
local metadata = xml.filter (t,
'../../topics/topic[@t:id=="%s
1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapters
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter
> \xmlfunction {#1} {chapter}
> \xmlflush {#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter:content
> \xmltext
}
\stopxmlsetups
\startxmlsetups xml:chapter
\xmlfunction {#1} {chapter}
\xmlflush {#1}
\stopxmlsetups
\startxmlsetups xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function
is is all settled down, we can improve
specific font related issues based on {\em realistic} user mwe's as we go.
Concerning large operators .. it worked before so ... the main reason
why in e.g. euler it failed was a configuration option (euler fonts will
be fixed too) which is a side effe
[footnote]
[numberconversion=set 2]
\setupnotation [footnote]
[align=hanging]
\setupwhitespace [medium]
\setupbodyfont [libertinus]
\showframe
\starttext
\quotation{{\em Cantharides}} is the reported message from Sir Francis
Drake upon def
ar text.
\stopbuffer
\startxmlsetups xml:xhtml
\xmlsetsetup{\xmldocument}{*}{-}
\xmlsetsetup{\xmldocument}{html|p|em}{xml:*}\stopxmlsetups
\startxmlsetups xml:html
\startdocument
\xmlflush{#1}
\stopdocument\stopxmlsetups
% Paragraphs are followed by a paragraph break, bu
etsetup{\xmldocument}{*}{-}
\xmlsetsetup{\xmldocument}{html|p|em}{xml:*}\stopxmlsetups
\startxmlsetups xml:html
\startdocument
\xmlflush{#1}
\stopdocument\stopxmlsetups
% Paragraphs are followed by a paragraph break, but only if not
nested.\startxmlsetups xml:p
\xmlfunction{#1}{p}
used the
following code to add them (and add en and em dash substitution as well).
%% start
\startluacode
fonts.handlers.otf.addfeature {
name = "v1", -- these character substitutions will be applied to
venetian-301-demi-bt
type = "liga
enetian 301 Italic
Venetian301BT-Bold.otf Venetian 301 Bold
venetian-301-demi-bt.ttfVenetian Dm BT Demi
They each had the fi and fl ligatures, but at different character positions
depending on which file, and they weren't recognised by default. So I used the
following code to add
1 - 100 of 1373 matches
Mail list logo
