From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: Why is only the first frame protruding into the margin?
Date: Sat, 18 May 2024 13:14:05 +0200 [thread overview]
Message-ID: <94a099dc-7b79-7232-5e8c-03ef3364bcf3@gmx.es> (raw)
In-Reply-To: <171597157579.1997.6597626626004504071@cgl.ntg.nl>
On 5/17/24 20:46, madiazm.eoicc@gmail.com wrote:
> [...]
> here is the last part of my script (the prior definitions are not
> problematic, since they worked when only using "miFuente". It seems to
> be something in "miCorm" that produces the protruding
Just a comment about typescripts.
At least in how I use ConTeXt, I live happily without having to use them.
See the following sample:
\definefontfamily[libertin][rm][Libertinus Serif]
\definefontfamily[libertin][ss][Libertinus Sans]
\definefontfamily[libertin][tt][Libertinus Mono]
\definefontfamily[cormora][rm][Cormorant]
\setupbodyfont[cormora]
\starttext
\input zapf\par
\switchtobodyfont[libertin]
\doloopoverlist{\rm,\ss,\tt}
{\recursestring\input zapf\par}
\stoptext
You may define font families (which are actually typeface families).
I think they may be easier to use than typefaces.
Just in case it might help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-05-18 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 22:05 [NTG-context] " madiazm.eoicc
2024-05-17 5:27 ` [NTG-context] " garulfo
2024-05-17 7:38 ` madiazm.eoicc
2024-05-17 7:46 ` Wolfgang Schuster
2024-05-17 9:02 ` madiazm.eoicc
2024-05-17 9:21 ` madiazm.eoicc
2024-05-17 14:44 ` Pablo Rodriguez via ntg-context
2024-05-17 18:22 ` madiazm.eoicc
2024-05-17 18:46 ` madiazm.eoicc
2024-05-18 11:14 ` Pablo Rodriguez via ntg-context [this message]
2024-05-17 21:41 ` Hans Hagen via ntg-context
2024-05-17 22:45 ` madiazm.eoicc
2024-05-18 10:57 ` Pablo Rodriguez via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a099dc-7b79-7232-5e8c-03ef3364bcf3@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).