From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: Question on style-italic vs style=italicface
Date: Sat, 2 Oct 2021 10:34:29 +0200 [thread overview]
Message-ID: <ea448203-da7a-0391-8a43-4b431ad15a60@gmail.com> (raw)
In-Reply-To: <029e2fd1-44b2-7ca9-f678-55605a9bfef9@rik.users.panix.com>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Rik Kabel via ntg-context schrieb am 27.09.2021 um 00:49:
>
> Wolfgang (off-list),
>
> It is simply wrong to say that \italicface as defined gives only \it
> or \bi as a result. Look at the definition. If the current
> fontalternative is it \it it will give a \tf result. It is sensitive
> to the current state in a similar way that \em and \emph are, but it
> will always give an italic or roman result.
>
If we leave the comparisons between \em and \italicface aside and talk
only about the results from \italicface we have a common ground.
You're right the results from \italicface aren't predictable and a fix
is needed but the same applies also to \boldface, \slantedface and
\typeface.
Attached is the output from a modified version of the styling command
(the \sc column is the fallback style). \swapface is unchanged and I'm
not sure about its output because it uses the \em code for italic and
slanted which means \setupbodyfontenvironment[default][em=blue] affects
also the \swapface results.
Wolfgang
[-- Attachment #2: emphasis.pdf --]
[-- Type: application/pdf, Size: 21405 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 prev parent reply other threads:[~2021-10-02 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 20:13 Rik Kabel via ntg-context
2021-09-26 20:29 ` Wolfgang Schuster via ntg-context
2021-09-26 22:20 ` Rik Kabel via ntg-context
2021-09-26 22:37 ` Wolfgang Schuster via ntg-context
2021-09-26 22:49 ` Rik Kabel via ntg-context
2021-10-02 8:34 ` Wolfgang Schuster via ntg-context [this message]
2021-10-02 9:46 ` Henning Hraban Ramm via ntg-context
2021-10-24 15:35 ` Wolfgang Schuster 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=ea448203-da7a-0391-8a43-4b431ad15a60@gmail.com \
--to=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).