From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Support for Bold Small Caps font alternative
Date: Sun, 17 Nov 2013 13:58:16 +0100 [thread overview]
Message-ID: <DDDFF99B-0305-499B-8070-ACAC94763170@gmail.com> (raw)
In-Reply-To: <5288b53c.09d20e0a.5ff0.ffffaea5SMTPIN_ADDED_BROKEN@mx.google.com>
Am 17.11.2013 um 13:23 schrieb honyk <j.tosovsky@email.cz>:
> On 2013-11-17 Wolfgang Schuster wrote:
>> Am 17.11.2013 um 11:04 schrieb honyk <j.tosovsky@email.cz>:
>>>
>>> in my document I combine both regular and bold small caps.
>>> As there is no predefined alternative for bold small caps variant,
>>> moreover, combining bold style and small caps has no effect, I've
>>> had to override an unused one:
>>>
>>> \definefontsynonym[SerifCaps][file:pala.ttf][features=small-caps]
>>> \definefontsynonym[SerifBoldSlanted][file:palab.ttf][features=small-
>>> caps] % bold caps
>>>
>>> Now I can switch styles using \sc and \bs.
>>>
>>> It would be nice to have a dedicated alternative for this. Or am I
>>> missing something?
>>
>> When you use a opentype font you can enable the small caps feature
>> with the \feature command, there is no need for an additional font
>> synonym.
>>
>> \setupbodyfont[pagella]
>>
>> \starttext
>>
>> Text {\feature[+][f:smallcaps]Text} {\bf Text
>> {\feature[+][f:smallcaps]Text}}
>>
>> Text \smallcaps{Text} \bold{Text \smallcaps{Text}}
>>
>> \stoptext
>
> Thanks for pointing me to this nice feature! This is even more robust.
>
> All my font definitions are based on this example
> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV
You can save a few lines in the font setup when you the new simplefonts code (works only with a recent beta).
\definefontfamily[mainface][rm][Palatino Linotype][features={default,quality}]
\setupbodyfont[mainface]
\setupalign[hanging,hz]
\starttext
How you, O Athenians, have been affected by my accusers, I cannot tell;
but I know that they almost made me forget who I was—so persuasively
did they speak; and yet they have hardly uttered a word of truth.
Ὅτι μὲν ὑμεῖς, ὦ ἄνδρες Ἀθηναῖοι,
πεπόνθατε ὑπὸ τῶν ἐμῶν κατηγόρων,
οὐκ οἶδα· ἐγὼ δ' οὖν καὶ αὐτὸς ὑπ'
αὐτῶν ὀλίγου ἐμαυτοῦ ἐπελαθόμην,
οὕτω πιθανῶς ἔλεγον.
\stoptext
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-17 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528894b2.866f0e0a.230f.fffff2c8SMTPIN_ADDED_BROKEN@mx.google.com>
2013-11-17 11:16 ` Wolfgang Schuster
2013-11-17 12:23 ` honyk
[not found] ` <5288b53c.09d20e0a.5ff0.ffffaea5SMTPIN_ADDED_BROKEN@mx.google.com>
2013-11-17 12:58 ` Wolfgang Schuster [this message]
2013-11-17 14:33 ` honyk
[not found] ` <5288d3b3.c2b00e0a.7b33.5469SMTPIN_ADDED_BROKEN@mx.google.com>
2013-11-17 15:38 ` Wolfgang Schuster
2013-11-17 10:04 honyk
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=DDDFF99B-0305-499B-8070-ACAC94763170@gmail.com \
--to=schuster.wolfgang@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).