ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: new lucida font
Date: Sat, 24 Mar 2012 13:04:17 +0100	[thread overview]
Message-ID: <54C4FAE7-65D6-41E9-BE05-DF263F38092F@googlemail.com> (raw)
In-Reply-To: <4F6D1C40.50507@nibua-r.org>


Am 24.03.2012 um 01:58 schrieb Renaud AUBIN:

> Le 19/03/2012 11:36, Wolfgang Schuster a écrit :
>> Can you try to attached typescript file, I replaced the files for italic and 
>> bolditalic fonts for the sans style with the names from the latex example 
>> document. The slanted and boldslanted alternatives for the sans style are also 
>> fixed.
>> 
>> Wolfgang
>> 
> +Small Caps support:
> 38,42d37
> <     \starttypescript [\s!serif] [lucidanova,lucidaot,otlucida]
> <         \definefontsynonym [\s!SerifCaps]        [\s!Serif]
> [\s!features=smallcaps]
> <         %definefontsynonym [\s!SerifBoldCaps]    [\s!SerifBold]
> [\s!features=smallcaps]
> <     \stoptypescript
> <
> 
> The SerifBoldCaps line is commented out since I get an error at
> processing… and can't figure why…

For smallcaps you can use the following command in your document:

\unexpanded\def\sc{\setff{smallcaps}}

With this you can get also smallcaps for the bold or italic style while with
the definition in the typescript (as in your patch) smallcaps are a font
switch and you can only get smallcaps for the regular style.

Bold doesn’t work because the typescript use a wrong name for the files
and Hans hasn’t released a new beta yet with the correct names.

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
___________________________________________________________________________________


      reply	other threads:[~2012-03-24 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  8:38 Meer, H. van der
2012-03-19  9:01 ` Wolfgang Schuster
     [not found]   ` <8351EB84-7C4D-4666-ADD2-27AEDA168765@uva.nl>
2012-03-19  9:48     ` Wolfgang Schuster
2012-03-19 10:12   ` Meer, H. van der
2012-03-19 10:36     ` Wolfgang Schuster
2012-03-24  0:58       ` Renaud AUBIN
2012-03-24 12:04         ` Wolfgang Schuster [this message]

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=54C4FAE7-65D6-41E9-BE05-DF263F38092F@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).