From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: Question on style-italic vs style=italicface
Date: Sun, 26 Sep 2021 18:49:43 -0400 [thread overview]
Message-ID: <029e2fd1-44b2-7ca9-f678-55605a9bfef9@rik.users.panix.com> (raw)
In-Reply-To: <c93b1ca4-85f3-3431-3262-841c73af10cb@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1725 bytes --]
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.
--
Rik
On 9/26/2021 18:37, Wolfgang Schuster via ntg-context wrote:
> Rik Kabel via ntg-context schrieb am 27.09.2021 um 00:20:
>>
>> So, I am asking whether, in places where folks often use
>> style=italic, it might be better to consider style=italicface.
>>
>> Bug report: \meaning\italicface gives:
>>
>> protected macro:\relax \ifx \fontalternative \s!tf \it \orelse
>> \ifx \fontalternative
>> \s!bf \bi \else \tf \fi
>>
>> This leaves out the transition from bi to bf. That transition is done
>> by \emph, but \emph may give slanted while \italicface is always italic.
>>
>
> The \italicface command uses either \it or \bi as result but it never
> result in upright text and the "italic" in the name tells you this,
> there are commands (e.g. \boldface) with similar results. To get a
> slanted style you have to use the \slantedface command.
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3300 bytes --]
[-- Attachment #2: 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-09-26 22:49 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 [this message]
2021-10-02 8:34 ` Wolfgang Schuster via ntg-context
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=029e2fd1-44b2-7ca9-f678-55605a9bfef9@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.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).