From: Willi Egger <context@boede.nl>
To: NTG-Context ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fonts... bold smallcaps
Date: Thu, 8 Oct 2015 15:20:51 +0200 [thread overview]
Message-ID: <3B09062F-0107-4CB3-A0BD-A931C746E36E@boede.nl> (raw)
In-Reply-To: <99A94056-4DF1-4A48-920C-979B12A3323B@elvenkind.com>
Wolfgang and Taco,
thank you for this!
Tac, the font Seravek I have is a bought font from processtype.
Willi
> On 8 okt. 2015, at 12:24, Taco Hoekwater <taco@elvenkind.com> wrote:
>
>>
>> On 08 Oct 2015, at 12:09, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>
>>> Willi Egger 8. Oktober 2015 um 11:40
>>> Hi all,
>>>
>>> sorry for bothering you with this.
>>>
>>> I have a font Seravek-Regular.otf and Seravek-Bold.otf. It is actually my company font.
>>>
>>> Now I needed to use bold-smallcaps. But I can not get it working, though otfinfo tells, that in the bold font there are smallcaps
>>>
>>> In my typescript file I have the following two lines, from which the Regular variant works perfectly well.
>>>
>>> \definefontsynonym [SansCaps] [Seravek-Regular] [features=smallcaps]
>>> \definefontsynonym [SansBoldCaps] [Seravek-Bold] [features=smallcaps]
>>>
>>> I tried to get bold smallcaps with \bf\sc but without success.
>
> SansBoldCaps does not have a ‘short form’, afaik.
>
>>> Can anyone point me what to do?
>> \bf\setsmallcaps
>
> (or \let\sc\setsmallcaps, somewhere in the setup section, which is what I usually do).
>
> Note that this method does not need nor use the SansCaps and SansBoldCaps synonyms in the typescript, and that it only works for well-behaved opentype fonts. Oh, and it may give you italic smallcaps, something the old ’SansCaps’ based method never did.
>
> Best wishes,
> Taco
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2015-10-08 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 9:40 Willi Egger
2015-10-08 10:09 ` Wolfgang Schuster
2015-10-08 10:24 ` Taco Hoekwater
2015-10-08 13:20 ` Willi Egger [this message]
2015-10-09 15:06 ` Alan BRASLAU
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=3B09062F-0107-4CB3-A0BD-A931C746E36E@boede.nl \
--to=context@boede.nl \
--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).