From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \switchtobodyfont issue, also with newotf
Date: Thu, 20 Aug 2015 14:34:10 -0400 [thread overview]
Message-ID: <55D61DA2.9040100@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2462 bytes --]
While working to get italic smallcaps in a secondary font face, I came
across an issue with \switchbodyfont. When this is used in a certain
way, the \tf font-style is changed, but not the \it, \bf, and so on.
The example below compiles cleanly as presented, and the problem is not
present. Each test line shows the expected font name and text.
When the Oops! line is uncommented, the only test line for the test font
that is correct is the \tf line. Other lines use the default font face
in the specified font styles, but the font features are a mix (note that
some are onum, some lining, and that long-s t ligatures are inconsistent).
When the newotf module is enabled, the example fails to compile without
errors, but produces similar results to non-newotf when the errors are
ignored.
This is not a problem with individual fonts—I have tried a variety of
fonts both as default and secondary and get the same result.
%\usemodule[newotf]
\setupwhitespace[medium]
\define\testAlphabet{\purefontname\font\quad
ABCDEFGHIJKLmnopqrsſtuvwxyz \& 012345789}
\starttypescript[Secondary]
\definetypeface[Secondary][rm][serif][ebgaramond][default]
% \definetypeface[Secondary][rm][serif][palatino][default]
% \definetypeface[Secondary][rm][serif][libertine][default]
\stoptypescript
\setupbodyfont [modern, 10pt]
%\setupbodyfont [palatino, 10pt]
\starttext
% {\switchtobodyfont[Secondary]Oops!\par}% Oops!
Default tf: {\tf \testAlphabet}\par
Default bf: {\bf \testAlphabet}\par
Default it: {\it \testAlphabet}\par
Default sl: {\sl \testAlphabet}\par
Default bi: {\bi \testAlphabet}\par
Default bs: {\bs \testAlphabet}\par
Default sc: {\sc \testAlphabet}\par
Default xx: {\it\setff{smallcaps}\testAlphabet}\par
\switchtobodyfont[Secondary]
Secondary tf: {\tf \testAlphabet}\par
Secondary bf: {\bf \testAlphabet}\par
Secondary it: {\it \testAlphabet}\par
Secondary sl: {\sl \testAlphabet}\par
Secondary bi: {\bi \testAlphabet}\par
Secondary bs: {\bs \testAlphabet}\par
Secondary sc: {\sc \testAlphabet}\par
Secondary xx: {\it\setff{smallcaps}\testAlphabet}\par
\stoptext
Have I failed to properly specify the secondary typeface? Do I need a
more complete typescript? Or is there a bug here?
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 3587 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2015-08-20 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 18:34 Rik Kabel [this message]
2015-08-21 13:10 ` Hans Hagen
2015-08-21 21:50 ` Rik Kabel
2015-08-22 9:01 ` Hans Hagen
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=55D61DA2.9040100@rik.users.panix.com \
--to=context@rik.users.panix.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).