\sc{\addff{smallcaps}}
This works for all styles that have the smcp feature, but I don't like
having to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all
styles?
\setupbodyfont[pagella]
\starttext
\tf Upright, \it Italic
for all styles that have the smcp feature, but I don't like having
to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all styles?
2) Are there any edits you would recommend to the above typescript template?
Once we're clear
of view. Nothing else.
>>
>> I have no clue of what you talk about here.
>>
>>>
>>> from the TeXbook 380-381
>>>
>>> «\obeylines doesn’t say ‘\def^^M{\par}’, so we must make any desired
>>> changes to
>>> \par before invoking \obeyl
> > > changes a
> > > space to category 12; but the \tt font has the character ‘␣’ in the
> > > ⟨space⟩ position, so we
> > > don’t really want ␣12 . (3) The \obeyspaces macro in Appendix B merely
> > > changes the
> > > ⟨space⟩ character to cate
macro in Appendix B merely
> > changes the
> > ⟨space⟩ character to category 13; active character ␣13 has been defined to
> > be the same
> > as \space, a macro that expands to ␣10 . This is usually what is desired;
> > for example,
> > it means
but the \tt font has the character ‘␣’ in the ⟨space⟩
> > position, so we
> > don’t really want ␣12 . (3) The \obeyspaces macro in Appendix B merely
> > changes the
> > ⟨space⟩ character to category 13; active character ␣13 has been defined to
> > be the same
>
is usually what is desired; for
> example,
> it means that spaces in constructions like ‘\hbox to 10 pt {...}’ won’t cause
> any
> trouble. But in our application it has an undesirable effect, because it
> produces spaces
> that are affected by the space factor. To defeat this feat
but Hans suggestion to provide a hook which can be used to
re-enable the feature, e.g.
\startsetups [typing:mine]
\setbreakpoints[compound]
\stopsetups
\setuptyping [CUSTOM] [setups=typing:mine]
The only flaw I can see in the suggestion is the use
,
it means that spaces in constructions like ‘\hbox to 10 pt {...}’ won’t cause
any
trouble. But in our application it has an undesirable effect, because it
produces spaces
that are affected by the space factor. To defeat this feature, it’s necessary
either to
say \frenchspacing or to redefine ␣13
e 12pt roman
%D bodyfont.
-)
> well, in type-imp-latinmodern.mkiv i can find 'designsize' ... you're
> not relying on some gpt driven search machine are you?
No just the search files feature in Notepad++ -)
Ok, looking at type-imp-latinmodern.mkiv, under latin-modern-designsize, I see
base,
mirror and -scale or scale,
mirror and -scale or scale
},
},
}
end
end
end
-- in principle one can have some extra parameters for shifts but this
-- is suboptimal anyway and only meant for minion
local function in
This thread about downsampling external images on the fly is a really helpful
feature! Thanks, Hraban for sharing the code!
I was wondering if it was possible to downscale also raster images embedded in
pdf/svg files loaded via \externalfigure?
I found a ghostscript solution online
(https
defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less overhead)
\definefontfeature
[default]
[default]
[expansion=quality,
protrusion=quality,
itlc=yes]
% vertical expansion
\widowpenalty 1
\frozen\clubpenalty 1
\frozen\displaywidowpenalty 1
\frozen\brokenpenalty 0 % \defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less
% \defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less overhead)
\definefontfeature
[default]
[default]
[expansion=quality,
protrusion=quality,
itlc=yes]
% vertical expansion
On 7/18/2023 4:12 PM, Hans Hagen wrote:
Hi,
In todays upload there is a follow up on a new feature that is already
present in the previous upload (but that was not yet advertised):
context --parallel test1.tex test2.tex test3.tex
context --parallel --pattern=test*.tex
context
Hi,
In todays upload there is a follow up on a new feature that is already
present in the previous upload (but that was not yet advertised):
context --parallel test1.tex test2.tex test3.tex
context --parallel --pattern=test*.tex
context --parallellist myfile.cmd (filters context
in these
containers. (It was when the mp to pdf conmverter showed up in context
mkii.) One or these now obsolete sub projects; it was kind of fun
anyway. Other experiments, like with saving positions (which originally
was a context feature that involved betweeen run dvi parsing with
dvipos) did make
?
> No, it's an independent feature of the linebreak mechanism. You can run
> this and see how it kicks in
>
> \starttext
>
> \definecolor[ttest][a=1,t=.5]
> \definecolor[rtest][a=1,t=.5,r=1]
>
> \dostepwiserecurse{80}{120}{1}{
> \startTEXpage[of
On 6/23/2023 11:54 AM, Marcus Vinicius Mesquita via ntg-context wrote:
Should then \setupalign[granular] be used before defining font features?
No, it's an independent feature of the linebreak mechanism. You can run
this and see how it kicks in
\starttext
\definecolor[ttest][a=1,t=.5
f primary badness now.
>
> (2) As side effect of (3) initialization of expansion (as well as
> compression and protrusion) is delayed till it kicks in. This means that
>
> \definefontfeature[default][default][expansion=quality]
>
> has become cheaper and might as well become the default.
]
has become cheaper and might as well become the default.
(3) The biggest new feature (already known to some of you as we chat
about it) is that in addition to the (upto three) passes that create a
paragraph we can now have extra ones. This is discussed in
lowlevel-lines.pdf (preliminary
t see the video, it's distracting, but as I said, is a valid
request on your part
Perhaps `\setuphead` can have such of a feature in the future — that
of different settings for different chapters, and if one exists now,
I'm just simply unaware of, but either way, you're dealing mainly
here with
Pro has them. So far, so
good (or not).
The hotline of fontshop.com thinks that there is an OpenType feature
that creates so-called
Composits out of the elements. I can understand the mechanism, I guess I
have tweaked something
similar in pdflatex or OmegaTeX in the pre-otf era, but I have
(or not).
The hotline of fontshop.com thinks that there is an OpenType feature
that creates so-called
Composits out of the elements. I can understand the mechanism, I guess
I have tweaked something
similar in pdflatex or OmegaTeX in the pre-otf era, but I have no idea
whether one of these
mechanism can
As the names suggest, it's a bit weird feature but so is \looseness. It
might evolve from playground into some interfaced feature. Of course
changing the text gives different results. But then, \looseness also
assumes a stable paragraph.
Hans
(a byproduct of more advanced experiments
same number of lines (single char moves have little impact).
- The \lastlinefit (etec) feature is now controlled by the "fit" option
in \setupalign etc; i'm still pondering how to control the orphan
penalty feature that has been around for a while now but never really
configured)
ted. When all modules are
consistently packages I can make a 'remove old' feature.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
stall.sh
> (I assume that, as of today,
> it is already the most up-to-date version
Correct.
> if and when it is
> required or desired to do so?
You only need to update ConTeXt if a new update fixes a bug that affects
you or adds a new feature that you want. Most updates are announced
wasting too much time on that.
if you know what the bugs are you can make a pseudo feature that fixes
it (there are examples in the test suite)
Hans
-
Hans Hagen | PRAGMA ADE
interferes
The problem is, the EB Garamond version that is included seems to have a
bug: the c-t and s-t ligatures (and maybe others) are triggered when
enabling `dlig` even though they are supposed to be in the `hlig`
feature. I also would like to include the Hack font that isn't
others) are triggered when
enabling `dlig` even though they are supposed to be in the `hlig`
feature. I also would like to include the Hack font that isn't in the
distribution.
So, I'm looking for a way to embed the fonts into the project in a
portable way instead of installing them in a system
On 4/3/23 09:07, Peter Münster via ntg-context wrote:
> Hi,
>
> I'm quite sure, that this worked some time ago with the standard font (LM):
I had the same impression, Peter.
But LM fonts don‘t have the OT feature smcp:
\setuppapersize[A8]
\starttext
\doloopoverlist{lm, pagell
tachments/20230401/1f8c6cc9/attachment-0001.pdf.
According to type-imp-concrete.mkiv, text has the feature boldened-10
applied to it.
Even with a variable font (which might not be the case in the link
above), extending the font fakes the bold, such as in:
\definefontfamily
[mainface]
Hi Hans,
> it is more side effect of removing the (declared obsolete some years
> ago) `` '' input which catched it later
>
> i tend to remove
>
> for k, v in next, ligaturemapping do
> hash[k] = v
> end
>
> in favor of an explic
'' input which catched it later
i tend to remove
for k, v in next, ligaturemapping do
hash[k] = v
end
in favor of an explicit 'tquo' feature that one can enable if wanted
\definefontfeature[default][default][tlig=yes,tquo=yes,trep=yes]
\startbuffer[test-bib]
@arti
all through the wiki, thinking this was a basic feature, but
couldn't get anything to work. I even tried my own custom macros, see below,
but strangely, it won't give me the correct title, it tells me the title of the
current chapter, instead of the title in which the reference was placed:
\define[1]\
I've set a \pagereference in a chapter, and want to print its chapter title and
page number, ex.
"You can find more information in "Fish" on p. 1" (where "Fish" is the title of
the chapter or section).
I've tried looking all through the wiki, thinking this was a ba
Hi,
Indeed you are right. However, Hans said the feature would be added in the next
update: so you have to wait a little bit :-)
Best regards: Otared
> On 27 Feb 2023, at 12:33, Jan-Erik Hägglöf via ntg-context
> wrote:
>
> I tested the code and the separator di
as Natural Tables.
I want to keep the headers in the CSV files so they're useful in other contexts.
The `m-database` module doesn't have a feature to suppress the header row, from
what I can see.
(I know `handlecsv` can do this, but I'm having troubles with that; if the
`m-database` line of inquiry
page for a custom head section
with uservariables defined.
I'd like to have the chapter page start on a right page. I'd like this page to feature
the title of the chapter (here: an interview) along with some other info like the
interviewee name and bio. All in a "fancy" layout.
I'm ha
om head
> section with uservariables defined.
>
> I'd like to have the chapter page start on a right page. I'd like this page
> to feature the title of the chapter (here: an interview) along with some
> other info like the interviewee name and bio. All in a "fancy" layout.
&g
Hello,
I'm trying to figure out how to design a chapter page for a custom head
section with uservariables defined.
I'd like to have the chapter page start on a right page. I'd like this
page to feature the title of the chapter (here: an interview) along with
some other info like
!
There is a little thing that I can't figure out though... In one of my
document I have makeup pages. But inserting them result in wrong page
numbering of subsequent pages. It appears that makeups do not increment
page numbers.
Is this a feature? How could re-establish the right page number for the
rest
s do not increment
> page numbers.
>
> Is this a feature? How could re-establish the right page number for the
> rest of the document?
>
> Thank you in advance,
>
> Alex
Can you show a small example of this behavior?
/Mikael
___
figure out though... In one of my
document I have makeup pages. But inserting them result in wrong page
numbering of subsequent pages. It appears that makeups do not increment
page numbers.
Is this a feature? How could re-establish the right page number for the
rest of the document?
Thank you
Hi,
We were considering to drop the virtual math fonts mechanism (which has
served its purpose in the transition in the very early days of luatex
but became obsolete as math fonts evolved) but in the end we were forced
keep this feature and even upgrade it because we liked iwona, kurier
o obtain high quality
> > documents. I'm a theoretical physicist and I'm going to write a book. I
> > think ConTeXt is the right choice to work with a number of formulas,
> > figures and cross-references. The visual quality of formulas is better
> > than in regular LaTeX. The new feat
of formulas,
figures and cross-references. The visual quality of formulas is better
than in regular LaTeX. The new feature with formula autosplitting looks
also very promising. For me it is important to obtain the high quality
without a lot of manual tweaks of each formula for each given document
rences. The visual quality of formulas is
> better than in regular LaTeX. The new feature with formula
> autosplitting looks also very promising. For me it is important to
> obtain the high quality without a lot of manual tweaks of each
> formula for each given document format and figu
of formulas is better than
in regular LaTeX. The new feature with formula autosplitting looks also
very promising. For me it is important to obtain the high quality without a
lot of manual tweaks of each formula for each given document format and
figure placement.
However, I have found a problem
ake it "consistent",
>> there are too many symbols that are at the moment different). But in
>> your example you can use \colonequals and \colon if you prefer. They
>> are centered around the math axis.
>> Best, Mikael
>> \setupbodyfont[lucidaot,12pt]
>> \star
topformula
\stoptext
There is a (experimental as we played with it and then got distracted)
feature that makes some symbols adapt to spacing in the input.
\starttext
\setupmathematics[autospacing=yes]
\setupmathematics[collapsing=2]
\im{A:B} and \im{A : B}\par
\im{A:=B} and \im
or this
> release. And we must thank Chuck Bigelow and Kris Holmes (they approved
> this release, as always), without whom nothing could be done.
>
> Bug reports and character/feature requests are welcome (email to this
> list is best), though, as usual, we cann
. And we must thank Chuck Bigelow and Kris Holmes (they approved
this release, as always), without whom nothing could be done.
Bug reports and character/feature requests are welcome (email to this
list is best), though, as usual, we cannot promise any particular
timeline for the next release.
Happy
On 1/20/2023 1:59 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I wanted to use a font with slightly wider effect, such as in:
\definetweakedfont[wider][xscale=1.075]
Is there any way that it could be applied as a font feature?
Or how could I apply this effect everytime
Dear list,
I wanted to use a font with slightly wider effect, such as in:
\definetweakedfont[wider][xscale=1.075]
Is there any way that it could be applied as a font feature?
Or how could I apply this effect everytime a \definefontfamily is used?
Many thanks for your help,
Pablo
On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
from what I understand is that undefined TeX commands cannot be added to
Lua comments.
Indeed. Of course we could have some 'ignore undefined command' feature
but that cripples the engine as well as then also never gives warning
> LuaTeX+MKIV, probably because there is code to fallback to other fonts?)
> and if you want to quit:
>
> \enabledirectives[logs.errors=missing characters]
Ok, this is useful.
I looked around, but I couldn't find a similar feature for when a font
[ '¿' ] = 1000,
[ '¡' ] = 1000,
}
}
\stopluacode
\definefontfeature[ktest][gpost_tes=yes]
\starttext
\startTEXpage[offset=1em]
\feature[+][gpos_test]
¿? ¡!
\stopTEXpage
\stoptext
This tries to move vertically the opening question and e
}
\stopluacode
\definefontfeature[ktest][gpost_tes=yes]
\starttext
\startTEXpage[offset=1em]
\feature[+][gpos_test]
¿? ¡!
\stopTEXpage
\stoptext
This tries to move vertically the opening question and exclamation
marks, so they are at the same height that its closing counterparts.
I thought
with ConTeXt ver: 2022.12.07 20:24 LMTX fmt: 2022.12.7,
except for the new cross page feature.
fixed in next upload
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH
: 2022.12.7,
except for the new cross page feature.
Gavin
> On Dec 18, 2022, at 4:03 AM, Alexandre Christe via ntg-context
> wrote:
>
> Hi Hans,
>
> On osx-64 I'm not getting a single connector printed when compiling
> anchor-002.tex. I've attached the log in case. Am I
school
tex math feature is still needed in context)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma
List,
>>>> 2) Can I tell \connectboxanchors to use my MetaPost code and pass
>>>> key=value pairs like I do with \setMPpositiongraphic?
>>> see attached ... the 'cross pages' feature is in the upcoming
>> This indeed passes key=value pairs, but I cannot ge
On 12/15/2022 5:15 PM, Gavin wrote:
Hi Hans and List,
2) Can I tell \connectboxanchors to use my MetaPost code and pass key=value
pairs like I do with \setMPpositiongraphic?
see attached ... the 'cross pages' feature is in the upcoming
This indeed passes key=value pairs, but I cannot get
Hi Hans and List,
>> 2) Can I tell \connectboxanchors to use my MetaPost code and pass key=value
>> pairs like I do with \setMPpositiongraphic?
> see attached ... the 'cross pages' feature is in the upcoming
This indeed passes key=value pairs, but I cannot get it to pass mine.
hout the \connectboxanchors interface
2) Can I tell \connectboxanchors to use my MetaPost code and pass key=value
pairs like I do with \setMPpositiongraphic?
see attached ... the 'cross pages' feature is in the upcoming
-
On 12/4/22 13:34, Hans Hagen via ntg-context wrote:
> On 12/3/2022 2:04 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Am I missing something or have I hit a bug in LMTX?
> more a bug in your approach: you specify a range where you also
> overwrite private slots (that happen to be used
]
\setupbodyfont[mainface]
\definestructureconversionset
[sectionnumbers]
[0,n,Characters,g,n]
[n]
\definefontfeature[section]
[smcp=yes,
c2sc=yes]
\setupheads[sectionconversionset=sectionnumbers]
\setuphead[section][style={\feature[+][section
[sectionnumbers]
[0,n,Characters,g,n]
[n]
\definefontfeature[section]
[smcp=yes,
c2sc=yes]
\setupheads[sectionconversionset=sectionnumbers]
\setuphead[section][style={\feature[+][section]}]
\starttext
\section{Just text}
{\feature[+][section]Just text}
\stoptext
variable fonts,
axes are only accesible using their name (not their tag) in the axis
section (not in the design axis section), aren't they?
And each font feature requires a new font instance (unlike other font
features such as small caps or many other OpenType features), doesn't it?
> btw, we don't chec
}
Since `` and "' map to the same character, only "' works.
The table has only 5 entries, not 6! (This took me a while to realize. ;))
> best not use an existign feature because we accumulate ... features
> come in order (you can force order if needed as you probably saw in
> one of the
On 11/11/2022 10:19 PM, Leah Neukirchen via ntg-context wrote:
Hi,
as Hans recommended in the last video meeting, I tried to implement
the texquotes feature using OTF features, and hit two problems:
1) To support German quotes as well, I have two ligatures that end
up as the same glyph
Hi,
as Hans recommended in the last video meeting, I tried to implement
the texquotes feature using OTF features, and hit two problems:
1) To support German quotes as well, I have two ligatures that end
up as the same glyph:
`` -> “
"' -> “
This can't be in the sa
ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 1234567890 1/4 2/8
3/9 ffi ft fi fl ffl
]]
local Font_Name = os.resultof("otfinfo -a " .. My_Font)
context.definefontfamily( { "Test" }, { "serif" }, { Font_Name }, {} )
context.setupbodyfont{ "Test, 12pt&q
On 11/3/2022 12:52 PM, Herbert Voss via ntg-context wrote:
Am 03.11.22 um 12:37 schrieb Thomas A. Schmitz via ntg-context:
Hi,
is there an easy way to get a list of all features that a font has and
typeset a sample text to see the result of every single feature? There
probably is, but I
i ft fi fl ffl
]]
local Font_Name = os.resultof("otfinfo -a " .. My_Font)
context.definefontfamily( { "Test" }, { "serif" }, { Font_Name }, {} )
context.setupbodyfont{ "Test, 12pt" }
COMMENTS
Again, this works; the font is set as bodyfont.
COD
Am 03.11.22 um 12:37 schrieb Thomas A. Schmitz via ntg-context:
Hi,
is there an easy way to get a list of all features that a font has and
typeset a sample text to see the result of every single feature? There
probably is, but I couldn't find anything...
You get a lot of information
Am 03.11.22 um 12:37 schrieb Thomas A. Schmitz via ntg-context:
Hi,
is there an easy way to get a list of all features that a font has and
typeset a sample text to see the result of every single feature? There
probably is, but I couldn't find anything...
You'll get only the features
Hi,
is there an easy way to get a list of all features that a font has and
typeset a sample text to see the result of every single feature? There
probably is, but I couldn't find anything...
All best
Thomas
, we can keep it as depricated feature (as there is no measurable
overhead when it's not used) .. although i might come up with some plain
mode in lmtx (when i'm really bored as it makes little sense) i'm not
going to worry much about / cq. follow old-school usage and
compatibility wrt dvi driver
.
> Do I need any setup, was this discarded in LMTX, or what’s wrong?
I have no idea if ConTeXt would ever follow redirects before, but I
agree that it would be a useful feature.
Thanks,
-- Max
___
If your question is of
t on Linux, but a Linux version does exist. Okular also lets you add
> some annotations.
Annotations may be part of a PDF viewer, but the problem is that in some
projects they understand that the feature to add them is part of a PDF
editor (so annotations won’t be added).
I think this is
s exist. Okular also lets you add some
annotations.
> > I've been using pdf.js almost exclusively for the past few years either
> > via Firefox or VS Code, and I've never really had any problems. The only
> > real issue that I've had is that it gets fairly slow with documents ov
, that could shift our focus to add/enable features for pdf.js
in TeX editors.
- PDF 2.0 compatible
It can open PDF 2.0 files, but I doubt that it supports every single
feature.
I won’t expect every feature, there are too many. Actually I don’t know
which features of PDF 2.0 Hans was missing
cuments over a few thousand pages long. Otherwise, it
> seems pretty fast and stable, and it supports nearly every feature
> that I tend to need.
I have never used firefox to display pdf files. I just tried it and
find that it has an interesting feature of caching rendered pages.
Page
t can open PDF 2.0 files, but I doubt that it supports every single
feature.
> - proper color and transparency display (respect color profiles)
It supports all of the PDF colour models/profiles for vectors, although
it ignores embedded colour profiles in images.
https://github.com/mozilla/pdf.
sure that these missing accented chars in fonts have been discussed
> before and you can use this feature (made for Mojca long ago):
>
> \definefontfeature[default][default][compose=yes]
>
> \starttext
> ḵ
> \stoptext
>
> So, unless yo
discussed
before and you can use this feature (made for Mojca long ago):
\definefontfeature[default][default][compose=yes]
\starttext
ḵ
\stoptext
So, unless you wikify it, I bet the same question will come up again.
Hans
\autofences \fourier{(z+\frac12)} + \courier{(z+\frac12)} +
\xourier{(z+\frac12)} $
$ \widehat{x^2 + 2x + 2} $
\stoptext
This example also shows a new \autofences feature and widehats
(widetilde and widecheck also work that way) that overcome limitations
in fonts, so
{\left(z+\frac12\right)} $
>
> $ \autofences \fourier{(z+\frac12)} + \courier{(z+\frac12)} +
> \xourier{(z+\frac12)} $
>
> $ \widehat{x^2 + 2x + 2} $
>
> \stoptext
>
> This example also shows a new \autofences feature and widehats
> (widetilde and widecheck also
the problem. Is this a bug or a feature?
The call to gm convert was lacking quoting of the file names. Fixed in
attachment.
While the code does some downsampling, the calculation is not always
right, because it doesn’t consider scaling (or something like that).
Hraban
if not modules
Thanks for this code Hraban. I tried this last night and it worked really
well. I did have one stumbling block when I noticed that those image files
with a space in their names were not found, however renaming without a
space solved the problem. Is this a bug or a feature?
Thanks
Keith McKay
ing for ConTeXt.
I mean, it is optimized for speed. As the author states:
Main feature of this module: it was heavily optimized for speed.
I think it may be interesting to be considered for ConTeXt.
Just in case it might help,
Pablo
___
dule patches or overloads core functionality withoutr mentioning it.
Here I'm mainly thinking about my lua-widow-control module, which
produces a visual effect, although it can be quite subtle if you're not
paying very close attention.
but i assuem that one has to explcitly enable that feature via a com
} + \courier{(z+\frac12)} +
\xourier{(z+\frac12)} $
$ \widehat{x^2 + 2x + 2} $
\stoptext
This example also shows a new \autofences feature and widehats
(widetilde and widecheck also work that way) that overcome limitations
in fonts, so
\def\CrappyHack#1{\im{#1{a} + #1{a+b} + #1{a+b+c} + #1
to figure it out).
The only problem is that the offsets of glyphs are a bit inaccurate,
which may be related to the font,
and I will look into it further.
in the vertical feature one can tune a bit.
The examples I have adjusted are attached,
and the output PDF of them is not attached
need to add it as a
feature if it's not already available in some way.
—
Bruce Horrocks
Hampshire, UK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@nt
On 7/20/2022 9:40 PM, Bruce Horrocks via ntg-context wrote:
On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
wrote:
Aside from purchasing a real font product from Linotype at enormous expense and
hoping it is better equipped, is there a way to coerce ConTeXt into using the
101 - 200 of 4840 matches
Mail list logo
