this is either a switch you turn on in ConTeXt, or something
that would still need to be implemented as a feature.
Best,
Augusto
On Mon, Jan 4, 2021 at 12:00 AM Henning Hraban Ramm
wrote:
> Am 03.01.2021 um 22:24 schrieb Hans Hagen :
>
> On 1/3/2021 10:02 PM, BPJ wrote:
>&g
ether ConTeXt is misbehaving:
\definefontfeature
[onumsmcp]
[script=latn,
onum=yes,
smcp=yes,
c2sc=yes]
\definefallbackfamily
[mainface]
[rm]
[GFS Heraklit]
[preset=range:greek,
force=yes]
\definefontfamily
[mainface]
[rm]
[TeX Gyre Pag
]
\starttext
\feature[+][onumsmcp]\tfb abc123ABC
\stoptext
If script=auto, current latest (2021.01.05 10:45) works fine. If it is
set to Latin (as above), I don’t get small caps.
Besides the potential issue in ConTeXt, I think that "script=auto" may
be safer than "script=latn"
Hans,
this sample shows an issue with script:
\definefontfeature
[default]
[default]
[script=latn]
\definefontfeature
[onumsmcp]
[onum=yes,
smcp=yes,
c2sc=yes]
\setupbodyfont
[pagella]
\starttext
\feature[+][onumsmcp]\tfb abc123ABC
\stoptext
On 1/5/21 11:01 AM, Hans Hagen wrote:
> Hi,
>
> A new version has been uploaded. This one has:
>
>\enableexperiments[fonts.compact]
>
> for the brave to test.
Hi Hans,
many thanks for your new release with the experimental feature.
I get a compilation time decrease f
{\nokerning whatever}\par
efficient ff fi\par
{\noligaturing efficient ff fi}\par
{\nokerning\noligaturing efficient ff fi}\par
{e{\noligaturing ffi}cient}\par
because this feature can be used local and because it actually has more
granularity than advertised, I added
}cient}\par
because this feature can be used local and because it actually has more
granularity than advertised, I added this in the next version
{ef{\noleftligaturing f}icient ff fi}\par
{ef{\norightligaturing f}icient ff fi}\par
(so, specific commands for left/right control
I could reproduce this occasionally occuring unexpected output in following MWE.Seems linked to calt=yes feature being set and ordn=yes being set and letter ‘f’ (some other letters such as ‘b’ work fine). Thanks as always for help. \definefontfeature[noteref][mode=node, ordn=yes
Dear list, Rare cases only but I thought it’d worth reporting this difference I could not understand.Could reproduce this problem with a simple MWE below. Kerning between ‘v’ and dot is doubled if \feature macro is used. Thanks \definefontfeature[xvicentury][mode=node]\definefontfeature[default
Hi, Hans and list. I want to know two things.
1. If the "option/content" pair could be enabled for hashes and arrays in
interfaces.definecommand:
\starttext
\startluacode
interfaces.definecommand{
name = "acommand",
--This doesn't work
--arguments = {"content", "array"},
arguments =
On 12/26/20 6:36 PM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 26.12.2020 um 12:58:
>> I have the following sample:
>> [...]
>> I’m not being able to get both lnum and no en-dashes: the defined font
>> feature seems to require the default and I cannot get
12123 -- 123\\
\tt 12123 -- 123
\stopTEXpage
\stoptext
I’m not being able to get both lnum and no en-dashes: the defined font
feature seems to require the default and I cannot get en-dashes disabled
when the default font feature set is enabled.
You need "script=auto" (or a vali
able to get both lnum and no en-dashes: the defined font
feature seems to require the default and I cannot get en-dashes disabled
when the default font feature set is enabled.
Does anyone what I am doing wrong here?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
so that we can link
that blob with the list.
A non referenced variant is:
\alwayscite[authoryear][angerer2016]
(there are more variants). So, it's actually a feature, not a bug.
Hans
math can be improved a bit, in general, unrelated
to this feature.)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69
that as the
font body gets bigger, the stroke gets thinner (so it's not just scaling).
I like this feature because it should make playing with sizes easier for
people while lighter for machines, even though fixed sizes to be
designed in advance enforce discipline and consistency in documents.
Of course we
gets thinner (so it's not just scaling).
I like this feature because it should make playing with sizes easier for
people while lighter for machines, even though fixed sizes to be
designed in advance enforce discipline and consistency in documents.
Massi
penalty in
performance, it
saves additional font instances. It is a good approach for the
occasional small
stretch of glyphs, like small capped logos and such.
We now can also do dynamic font scaling, which means that we don't need
to define
a new font instance when the same feature set
of some functions, and I would like to include the
SVGs in a ConTeXt document so it ends up as PDF. I started creating
the document by including the SVGs using the new LMTX MetaPost SVG
feature, however at this point I don't know how to proceed...
This is the situation: the source SVGs look fine
package
for drawing 2D plots.
> I started creating
> the document by including the SVGs using the new LMTX MetaPost SVG
> feature, however at this point I don't know how to proceed...
>
> This is the situation: the source SVGs look fine, but after including
> them in the docum
the
SVGs in a ConTeXt document so it ends up as PDF. I started creating
the document by including the SVGs using the new LMTX MetaPost SVG
feature, however at this point I don't know how to proceed...
This is the situation: the source SVGs look fine, but after including
them in the document
zed or
... seen all kind of variants) ... officially a rendering should listen
to some keys that relate to it but this is not always the case
(part of the problem is, i think, that esp for check fields a bugs or
behaviour has become a feature which makes it kin dof inconsisten twith
the rest of
d this is the text
> width by defalut unless you set one with the 'width' argument or when
> you pass [align=]
>
> (3) cropping takes place after all has been typeset but happens within
> the width, again, this could be made more tolerant but then other cases
> will fail
>
> with
=]
(3) cropping takes place after all has been typeset but happens within
the width, again, this could be made more tolerant but then other cases
will fail
with mechanisms like there is always a catch: handle this well and
something else will fail (when it works as expected it's seen as a
f
On 12/6/2020 6:24 PM, Pablo Rodriguez wrote:
On 12/6/20 1:03 PM, T. Kurt Bond wrote:
backend > blocked > function 'setmapfile' is not accessible
Using LMTX, it seems to be "Latin Modern Roman Math".
I wonder whether this is an intended new feature or an issue.
hm, seem
n Roman Math".
I wonder whether this is an intended new feature or an issue.
> When I run it through context it works and produces output that uses the
> EBGaramond font. The following also work: antykwapoltawskiego, asana,
> cambria, charter, ebgaramond, gentium, inconsolata, iwona,
gature) by the "dlig" (discretionary
ligatures) feature, so you'll need to disable that. Unfortunately,
this will also disable the Th ligature. This is a known, open issue
for the font: https://github.com/octaviopardo/EBGaramond12/issues/20
<https://github.com/octaviopardo/EBGaramond
onary
ligatures) feature, so you'll need to disable that. Unfortunately, this
will also disable the Th ligature. This is a known, open issue for the
font: https://github.com/octaviopardo/EBGaramond12/issues/20
<https://github.com/octaviopardo/EBGaramond12/issues/20>.
One of these exa
e:
>>
>>> On 12/2/2020 6:14 PM, T. Kurt Bond wrote:
>>> > It does help. Thanks.
>>> >
>>> > But how do I turn that font feature off in ConTeXt?
>>> You forget to add a MWE ...
>>>
>>> Hans
>>>
>>>
; \stoptext
>>
>>
>> On Wed, Dec 2, 2020 at 12:35 PM Hans Hagen wrote:
>>
>>> On 12/2/2020 6:14 PM, T. Kurt Bond wrote:
>>> > It does help. Thanks.
>>> >
>>> > But how do I turn that font feature off in ConTeXt?
>>> You f
Wed, Dec 2, 2020 at 12:35 PM Hans Hagen wrote:
>
>> On 12/2/2020 6:14 PM, T. Kurt Bond wrote:
>> > It does help. Thanks.
>> >
>> > But how do I turn
at 12:35 PM Hans Hagen wrote:
> On 12/2/2020 6:14 PM, T. Kurt Bond wrote:
> > It does help. Thanks.
> >
> > But how do I turn that font feature off in ConTeXt?
> You forget t
On 12/2/2020 6:14 PM, T. Kurt Bond wrote:
It does help. Thanks.
But how do I turn that font feature off in ConTeXt?
You forget to add a MWE ...
Hans
-
Hans Hagen | PRAGMA ADE
gt;
> On Wed, Dec 2, 2020 at 12:14 PM T. Kurt Bond wrote:
>
>> It does help. Thanks.
>>
>> But how do I turn that font feature off in ConTeXt?
>>
>> On Wed, Dec 2, 2020 at 11:55 AM Joey McCollum <
>> jmccollum20140...@gmail.com> wrote:
>>
>
I think it would look something like
\definefontfamily[english] [rm] [EB Garamond] [features={default,dlig=no}]
On Wed, Dec 2, 2020 at 12:14 PM T. Kurt Bond wrote:
> It does help. Thanks.
>
> But how do I turn that font feature off in ConTeXt?
>
> On Wed, Dec 2, 2020 at 11:55 A
It does help. Thanks.
But how do I turn that font feature off in ConTeXt?
On Wed, Dec 2, 2020 at 11:55 AM Joey McCollum
wrote:
> If you're using Octavio Pardo's version of EB Garamond (
> https://github.com/octaviopardo/EBGaramond12), then these ligatures are
> covered (along wi
If you're using Octavio Pardo's version of EB Garamond (
https://github.com/octaviopardo/EBGaramond12), then these ligatures are
covered (along with the Th ligature) by the "dlig" (discretionary
ligatures) feature, so you'll need to disable that. Unfortunately, this
will also disa
minimalistic as possible lua
> itself can do most). I don't want a bloated bianry with all kind of
> dependencies that force constant updates.
A very important consideration.
>
> > 2. Is this a trivial fix (and might be fixed soon -- time
> > permitting)?
>
> It's
n the \HR definition that should be
>
> \tolerant\protected\def\VR[#1]{\NC ...\NC}
>
>> \definemathmatrix[mymatrix]
>> [left={\left(\,},
>> right={\, \right)}]
>> \starttext
>> \startformula
>> \startmymatrix
>> \NC A \VR
={\, \right)}]
\starttext
\startformula
\startmymatrix
\NC A \VR B \NR
\HR
\NC C \VR D \NR
\stopmymatrix
\stopformula
\stoptext
Anyway, a feature like this should be in sync with other table
mechanisms, so
ror on line 4 in file ./scratch1.tex: Valid
keyword expected, likely 'plus'
pa
tch
1 \setuptagging[state=start]
2 \starttext
3 \obeyspaces\obeylines
4 >> patch
5 \stoptext
This may be a bug in the tagging feature.
ord
expected, likely 'plus'
pa
tch
1 \setuptagging[state=start]
2 \starttext
3 \obeyspaces\obeylines
4 >>patch
5 \stoptext
This may be a bug in the tagging feature.
Cheers,
and one can be pretty sure that we then
don't have a proper csname. This is why in luatex we have a catch for
running wild csname checking.
The original \ifcsname test was inherited from etex. The \protected
feature also comes from etex. But \csname is a tex natural.
In pdftex (and luatex
then don't have a proper
csname. This is why in luatex we have a catch for running wild csname
checking.
The original \ifcsname test was inherited from etex. The \protected
feature also comes from etex. But \csname is a tex natural.
In pdftex (and luatex) a protected macro inside an \(if)csname does
',
properties 'frozen instance protected', file './oeps.tex', line 4
because \infull is already used by the predefine abbreviations instance
no problem if you don't use that feature
Hans
-
infull is already used by the predefine abbreviations instance
no problem if you don't use that feature
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Nethe
or]
>> \starttext
>> \definedfont[file:notoserifcjkkrregular*default]
>> Korean sentences.
>> 한글이 아름답습니다.
>> \stoptext
>> fonts > 'fallback modern-designsize rm 12pt' is loaded
>> fonts > defining > font 'notoserifcjkkrregular', featu
fonts > 'fallback modern-designsize rm 12pt' is loaded
fonts > defining > font 'notoserifcjkkrregular', feature
'vert', script 'grek', no language 'kor'
fonts > defining > font 'notoserifcjkkrregular', feature
'vert', script 'latn', no langu
ern-designsize rm 12pt' is loaded
fonts > defining > font 'notoserifcjkkrregular', feature 'vert',
script 'grek', no language 'kor'
fonts > defining > font 'notoserifcjkkrregular', feature 'vert',
script 'latn', no language 'kor'
fonts > defining > font '
Sylvain Hubert schrieb am 08.11.2020 um 13:02:
On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez <mailto:oi...@gmx.es>> wrote:
Hi Sylvain,
this is the same as:
\definefontfamily[face1][rm][gabriola]
Just in case, "slanted" is an already defined feature. It
On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez wrote:
> Hi Sylvain,
>
> this is the same as:
>
> \definefontfamily[face1][rm][gabriola]
>
> Just in case, "slanted" is an already defined feature. It slants the font.
>
> > \definefontfamily[fa
[palatino] don’t seem to
work at all.
Results are different if feature ef1 is defined or not.
It's best to check these things first with \definefont to ensure it
isn't a problem of \definefontfamily.
With all features defined, paragraph width is wrong using
"effect={width=1.0}".
Ad
if feature ef1 is defined or not.
With all features defined, paragraph width is wrong using
"effect={width=1.0}".
Could you check this?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If you
]
Just in case, "slanted" is an already defined feature. It slants the font.
> \definefontfamily[face2][rm][gabriola][it={features:{default,
> effect={}}}]
> \definefontfamily[face3][rm][gabriola][it={features:{default,
> effect={width=1.0}}}]
BTW, the documentation is cl
. Indeed, googling 'context+tex+boldened' or 'contextgarden+boldened'
results in nothing useful.
Well, I asked for that feature
(https://mailman.ntg.nl/pipermail/ntg-context/2018/091128.html), which
Ulrike Fischer requested a year before
(https://mailman.ntg.nl/pipermail/ntg-context/2017/090091.html
xt+tex+boldened' or 'contextgarden+boldened'
> results in nothing useful.
Well, I asked for that feature
(https://mailman.ntg.nl/pipermail/ntg-context/2018/091128.html), which
Ulrike Fischer requested a year before
(https://mailman.ntg.nl/pipermail/ntg-context/2017/090091.html).
And that year,
inmodern's bold?
>
> Hi Sylvain,
>
> there is an already defined font feature that fakes boldened fonts:
> boldened (and also boldened-10, boldened-15, boldened-20 and boldened-25
> [boldened is actually boldened-30]).
>
> But I don’t use \definefont myself, so this is my sample:
&g
On 11/7/20 4:06 PM, Sylvain Hubert wrote:
> [...]
> Could anyone help me define a {\bf}-aware version of \fakebf which can
> render the "4 5 6" in the example above in latinmodern's bold?
Hi Sylvain,
there is an already defined font feature that fakes boldened fonts:
boldened
> \hbox to 20pt xoffset -3cm{\hss3}
>
> where previously the 'to' spec always came last and multiple 'to' are
> okay (offsets etc are a lmtx feature, and it means many more keywords
> have to be scanned, which was one reason for cooking up a better
> mechanism, even if right f
ously the 'to' spec always came last and multiple 'to' are
okay (offsets etc are a lmtx feature, and it means many more keywords
have to be scanned, which was one reason for cooking up a better
mechanism, even if right from the start that was already rather optimized).
now, in principle this br
> (PS: I would say that adding support for transliteration of the text
> from one script to the other would be a really nice feature. Then you
> could type your text for a book once and have it typeset in both
> versions without any extra effort :)
There is Philipp Gesang's transliter
nsliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
As for transliteration, cyrillic to latin is one-to-one, straightforward
with no exceptions.
A simple
ay that adding support for transliteration of the text
> from one script to the other would be a really nice feature. Then you
> could type your text for a book once and have it typeset in both
> versions without any extra effort :)
As for transliteration, cyrillic to latin is one-to-on
some new stuff (in the middle of fit)
(PS: I would say that adding support for transliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
just gimme the specs
ly.
Thank you,
Mojca
(PS: I would say that adding support for transliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
__
\setupinteraction[...style=\MyUrl...]` either it
> > doesn't work or displays a background which doesn't break well across
> > lines.
> > |
> >
> > |Is there a workaround or another method? Maybe a feature request for a
> > more customizable setup for references? I had the same problem so
across
lines.
|
|Is there a workaround or another method? Maybe a feature request for a
more customizable setup for references? I had the same problem some time
ago and I guess some others too.
\definebar
[urlbackground]
[color=yellow,
order=background,
continue=yes
\footnote{This should create links to same
page} and an external link: \from[aurl].\stoptext
When one tries to use `\setupinteraction[...style=\MyUrl...]` either
it doesn't work or displays a background which doesn't break well
across lines.
Is there a workaround or another method? Maybe a feature
with the other feature: some kind of protection
against macro abuse. This is actually related to the above because when
you want to see macros with readable names in error messages, you cannot
protect them with underscores and other ugly tricks that at the same
time make stuff unreadable and ugly
\setupcharacterkerning. I can match character kerning, but
inter-word spaces are different. What is the right option, command or
feature to change it for current font and/or in the font definition? I
haven't found any.
MWE
% macros=mkiv
\setupcharacterkerning[large][factor=0.1
in
identifying the Unicode range of the oldstyle numerals in STIX Two Text.
And that is something I need to take advantage of Wolfgang’s code.
You replace the normal digits but apply the oldstyle feature.
\definefontfamily
[alan] [rm] [STIX Two Text]
[features={default,f:oldstyle
gt; > \definefontfeature[f:oldstyle][onum=yes]
> >
> > \setupbodyfont[mainface, 18pt]
> > \addfeature{f:oldstyle}
> >
> > \starttext
> > 123456789
> > \blank[big]
> > $\sqrt{2} + 1234$
> > \stoptext
> >
> > Any pointers will
ptext
>
> Any pointers will be greatly appreciated.
mtxrun --script fonts --list --info stixtwomath
shows that STIX Two Math doesn’t provide the onum feature.
Hraban
___
If your question is of interest to
Hello,
trying to reproduce the hand-printed original as close as possible I'm
using \setupcharacterkerning. I can match character kerning, but inter-word
spaces are different. What is the right option, command or feature to
change it for current font and/or in the font definition? I haven't found
> improve it in a ConTeXt dependent way. This way ConTeXt more feature-rich
> and easier to maintain than carrying the technical burden of TeX. There are
> system like SILE typesetter (https://sile-typesetter.org/) which are
> developed from the ground up and also The
are in operation.
Also perhaps it might be best than just depend on TeX maybe fork TeX and
improve it in a ConTeXt dependent way. This way ConTeXt more feature-rich
and easier to maintain than carrying the technical burden of TeX. There are
system like SILE typesetter (https://sile-typesetter.org
ghly, but I've got these issues.
I have problems with the grid on such a page. The last column of three
does not align the lines at the grid. With columnsets the grid is ok.
These columnsets as described in the manual looked very promising to me
as I could change the column layout on the page. The colu
Hi,
as I'm almost done with my PDFs for the first volume of our journal, I'm
thinking about also publishing HTMLs. We have XSLTs almost ready for
this, but I was thinking if I could use ConTeXt also for this. A very
nice feature would be being able to add marking of page breaks
)?
no, it's a math font with a math table and math feature sonly
2. If so, do I still need the first line in my setup, namely the [rm]
line? Would not the [mm] be enough?
no, you need a text font with basic symbols and text features only
so, the setup you use is ok
Hans
I'm doing my first mkiv index (it took me a long time to upgrade from
mkii!) and I really like the processor feature to format elements
differently. But there are a couple of things I would really like to
achieve that I'm struggling with:
1. Elided numbers in an index range entry. For example
of the current (MkIV) implementation. In lmtx it should be possible
> to be smarter about this, but it needs an extension to ConTeXt.
If this is possible with LMTX, it would be a great feature to have.
Many thanks for y
[mm] [STIX Math] [rscale=1.10]
the upper bound of the integral is misplaced and I don't know how to fix it.
In the archives I saw that there is « mathnolimitsmode » which can be added as
a font feature, but its values and how to set it up are far from being clear to
me.
Thank you s
feature) while
\oldstyle does what you want: enable the oldstyle feature on top of others
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel
a while
as this is the only affected feature)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl
ming that it's somehow
> useful). We could predefine a bunch. As usual there might be issues but
> I'll sort them out when we run into them (it's a non critical feature
> with not much impact).
>
> Hans
>
> (who must not forget to document it somewhere)
>
>
> --
might be able to guess from this code what is supposed to happen.
I'll play a bit more with this later (assuming that it's somehow
useful). We could predefine a bunch. As usual there might be issues but
I'll sort them out when we run into them (it's a non critical feature
with not much impact
ct from
> what is required on screen (ii) I am using Mk IV (iii) I need spot colors set
> up for cmyk, and for now I need shades between black and white (e.g. light
> gray) for a simple design feature.
>
> My question is this: is the use of color keywords sufficient? Or in other
> words,
colors set up for cmyk, and for now I need shades
between black and white (e.g. light gray) for a simple design feature.
My question is this: is the use of color keywords sufficient? Or in
other words, have predefined color names like lighgray already been
defined in, say cmyk terms behind
On 8/21/20 2:59 PM, Hans Hagen wrote:
> On 8/20/2020 4:20 PM, Pablo Rodriguez wrote:
>
>>\replaceword[whatever][this or][no]
>>\replaceword[whatever][that][]
> this feature creep is in the next upload
Hans,
many thanks for the new feature.
Pablo
-
On 8/20/2020 4:20 PM, Pablo Rodriguez wrote:
\replaceword[whatever][this or][no]
\replaceword[whatever][that][]
this feature creep is in the next upload
Hans
-
Hans Hagen | PRAGMA
rtical[height=.75\textheight]
> > \MyFont
> > \setupalign[flushleft]
> > \setupinterlinespace[40pt]%
> > ᠣᠢᠷᠠ ᠵᠢᠨ ᠡᠳᠦᠷ᠂ ᠦᠪᠦᠷ ᠮᠣᠩᠭᠣᠯ ᠦᠨ ᠰᠢᠯᠢ ᠵᠢᠨ ᠭᠣᠣᠯ ᠠᠢᠮᠠᠭ ᠦᠨ ᠰᠢᠯᠣᠭᠣᠨ ᠬᠦᠬᠡ
> > ᠬᠣᠰᠢᠭᠣᠨ ᠦ ᠰᠢᠭᠦᠬᠦ ᠬᠣᠷᠢᠶᠠ ᠨᠢᠭᠡᠨ ᠬᠦᠴᠦᠷᠬᠡᠭᠯᠡᠨ ᠨᠦᠵᠢᠳᠯᠡᠭᠰᠡᠨ ᠶᠠᠯᠠᠲᠣ ᠬᠡᠷᠡᠭ ᠲᠦ
>
ᠣᠭᠣᠴᠠᠭᠠ ᠲᠠᠢ ᠬᠣᠷᠢᠬᠣ ᠡᠷᠡᠭᠦᠦ ᠪᠡᠷ
ᠰᠢᠳᠬᠡᠭᠰᠡᠨ ᠪᠠᠢᠨᠠ᠃
\stopvertical
\stoptext
But it's kind of a quick hack interface. We can have alignment,
interlinespace etc parameters to. Maybe definable verticals and so.
Hans
ps. for chinese one would probably kick in an extra feature
% \definefontfeatur
; Aside from luatools you can also use mtxrun to refresh the database
> (mtxrun --generate) which also works when you clear it (mtxrun --script
> cache --erase) where luatools fails.
>
> > is it a feature? thanks
>
> No.
>
> Wolfgang
>
> _
) which also works when you clear it (mtxrun --script
cache --erase) where luatools fails.
is it a feature? thanks
No.
Wolfgang
___
If your question is of interest to others as well, please add an entry
'
is it a feature? thanks
--
Dr YAHYAOUI Mohamed Kaddour, cardiologue .
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg
ings of your textbackground, as in
> >
> > \definetextbackground[fondpaille]
> > [background=color,
> > backgroundcolor=fondpaille,
> > frame=off,
> > location=paragraph, % or: text, always, paragraph
> > backgroundoffset=4pt] %
, paragraph
backgroundoffset=4pt] % change the value here
It's a float feature which can be disabled.
\setupfloats[freeregion=no]
Wolfgang
___
If your question is of interest to others as well, please add
with
the boldened feature. MkIV (from 2020.01.30 14:13) works just fine.
Am I missing something or have I hit a bug?
I have a fix. This kind of trickery is complicated by the fact that mkiv
and lmtx follow a bit different route and that there is still mkiv code
around that does the lmtx backend stuff
, boldened}}]
\setupbodyfont[mainface]
\starttext
\input{zapf}\\
{\it \input{zapf}}\\
{\bf \input{zapf}}\\
{\bi \input{zapf}}\\
\stoptext
I’m afraid that LMTX (current latest 2020.07.13 23:53) cannot deal with
the boldened feature. MkIV (from 2020.01.30 14:13) works just
I note the first method only works when \usecolors[xwi]
is present; otherwise, it prints an interesting "themaintextcolor".
Here is a nostalgic mkii accessor for such a list (color support is a
real old feature and conceptually hasn't changed that much):
\def\Wh
501 - 600 of 4828 matches
Mail list logo
