I get it now. Thanks to you both.
Julian
On 26/8/20 2:20 pm, Wolfgang Schuster wrote:
jbf schrieb am 26.08.2020 um 05:42:
MWE as follows:
\definefontfamily [mainface] [rm] [baskervaldadfstd]
[tf=file:BaskervaldADFStd.otf]
\definefontfamily [mainface] [ss] [librisadfstd]
jbf schrieb am 26.08.2020 um 05:42:
MWE as follows:
\definefontfamily [mainface] [rm] [baskervaldadfstd]
[tf=file:BaskervaldADFStd.otf]
\definefontfamily [mainface] [ss] [librisadfstd]
[tf=file:LibrisADFStd-Regular.otf]
\definefontfamily [mainface] [mm] [TeX Gyre Pagella Math]
MWE as follows:
\definefontfamily [mainface] [rm] [baskervaldadfstd]
[tf=file:BaskervaldADFStd.otf]
\definefontfamily [mainface] [ss] [librisadfstd]
[tf=file:LibrisADFStd-Regular.otf]
\definefontfamily [mainface] [mm] [TeX Gyre Pagella Math]
\setupbodyfont[mainface]
\starttext
\tf ffi,
\it
On Wed, 26 Aug 2020, jbf wrote:
> I intend to use it! So, yes, I had not used it at this point, and your
> explanation now makes sense.
>
> In the test example I have, I have now placed a line: \ss My text, and I see
> that it now loads the sans serif font. But can you explain why it loads the
I intend to use it! So, yes, I had not used it at this point, and your
explanation now makes sense.
In the test example I have, I have now placed a line: \ss My text, and
I see that it now loads the sans serif font. But can you explain why it
loads the math font, given that I have not, as
On Wed, 26 Aug 2020, jbf wrote:
> Can someone tell me why, when I define my typefaces as follows below, I get:
>
> mkiv lua stats > loaded fonts: 2 files: baskervaldadfstd.otf,
> texgyrepagella-math.otf
>
> when in fact my font definitions are:
>
> \definefontfamily [mainface] [rm]
Can someone tell me why, when I define my typefaces as follows below, I get:
mkiv lua stats > loaded fonts: 2 files: baskervaldadfstd.otf,
texgyrepagella-math.otf
when in fact my font definitions are:
\definefontfamily [mainface] [rm] [baskervaldadfstd]
[tf=file:BaskervaldADFStd.otf]
On Tue, Aug 25, 2020 at 04:48:27PM +0200, Hans Hagen wrote:
> > I noticed that recent LuaMetaTeX versions treats control sequences
> > defined using token.set_lua with `value` or `condition` as frozen and
> > does not allow redefining them. Given that these are not macros, we also
> > can't
Hi,
The current version of lmtx has some updated tracing of memory usage.
This is irrelevant for most users but some of you generat elarge an
complex files so ... (I'm talking about mf here).
There is a command line option
--usage
that will make a run report some more statistics. The
On 8/25/2020 3:59 PM, Marcel Fabian Krüger wrote:
Hi,
I noticed that recent LuaMetaTeX versions treats control sequences
defined using token.set_lua with `value` or `condition` as frozen and
does not allow redefining them. Given that these are not macros, we also
can't "unfreeze" them using
Hi,
I noticed that recent LuaMetaTeX versions treats control sequences
defined using token.set_lua with `value` or `condition` as frozen and
does not allow redefining them. Given that these are not macros, we also
can't "unfreeze" them using \unletfrozen.
1. Would it be possible to add a
On Mon, 24 Aug 2020, Taco Hoekwater wrote:
>
>
> > On 24 Aug 2020, at 19:59, Wolfgang Schuster
> > wrote:
> >> \setcounter[figure][5] % next figure is no.6
>
> For this subfigure stuff, perhaps this is useful?
>
> [...]
>
> I could not find a safe way to increment the subfigure number
Thanks all for useful tips. I ended up doing something similar as a short
term fix for my float number override issue, basically setting up a new
float type to use for the deviant ones and then resetting the numbering of
the existing ones. It would be great if there was a facility to just drop
in
13 matches
Mail list logo
