From: Sylvain Hubert <champignoom@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: weird behavior of font.feature.effect
Date: Sun, 8 Nov 2020 00:57:23 +0100 [thread overview]
Message-ID: <CACNy3ND4r55aBwbRGjMbE1jCSJSR9Qs7+biY3mdrHY3=J3HQWg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]
Dear List,
I'm confused by the result of the following example (see attached):
\definefontfamily[face1][rm][gabriola][it={features:{default}}]
\definefontfamily[face2][rm][gabriola][it={features:{default,
effect={}}}]
\definefontfamily[face3][rm][gabriola][it={features:{default,
effect={width=1.0}}}]
\starttext
\startitemize[n, packed]
\item \switchtobodyfont[face1]\it\dorecurse{100}{a b c }
\item \switchtobodyfont[face2]\it\dorecurse{100}{a b c }
\item \switchtobodyfont[face3]\it\dorecurse{100}{a b c }
\stopitemize
\stoptext
Could someone explain:
1. What does "effect" mean? Why does "effect={}" embolden the fonts even
though nothing ({}) is given as arguments?
2. Similarly, what does "width" do? Why does "width=1.0" shrink the width
of the line instead of doing nothing?
Thanks in advance.
Best,
Sylvain
[-- Attachment #1.2: Type: text/html, Size: 1159 bytes --]
[-- Attachment #2: Untitled.png --]
[-- Type: image/png, Size: 63580 bytes --]
[-- Attachment #3: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-11-07 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 23:57 Sylvain Hubert [this message]
2020-11-08 10:19 ` Pablo Rodriguez
2020-11-08 12:02 ` Sylvain Hubert
2020-11-08 12:14 ` Wolfgang Schuster
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='CACNy3ND4r55aBwbRGjMbE1jCSJSR9Qs7+biY3mdrHY3=J3HQWg@mail.gmail.com' \
--to=champignoom@gmail.com \
--cc=ntg-context@ntg.nl \
/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).