From: Antoine Junod <toto@tots-ns.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: small caps and old numbers with open type fonts
Date: Wed, 16 Apr 2008 12:34:47 +0200 [thread overview]
Message-ID: <87prsqm6k8.fsf@zapata.tots-ns.net> (raw)
In-Reply-To: <115224fb0804160317vae24b72y67997fd127fe8a50@mail.gmail.com> (Wolfgang Schuster's message of "Wed, 16 Apr 2008 12:17:16 +0200")
"Wolfgang Schuster" <schuster.wolfgang@googlemail.com> writes:
> On Wed, Apr 16, 2008 at 11:59 AM, Antoine Junod <toto@tots-ns.net> wrote:
>> Hi Wolfgang!
>>
>> "Wolfgang Schuster" <schuster.wolfgang@googlemail.com> writes:
>>
>> > On Sun, Apr 13, 2008 at 8:39 PM, Antoine Junod <toto@tots-ns.net> wrote:
>> >> Hello list,
>> >>
>> >> I actually use my font as simple as possible with a
>> >> \definefont[boum][MyFont at 12pt]. Is it the problem?
>> >>
>> >> It the same with the \sc command.
>> >
>> > \definefont[boum][MyFont at 12pt]
>> > \definefont[scboum][MyFont*smallcaps at 12pt]
>>
>> Wow, beautifull, thanks :) Where is the * and what we can put after
>> (smallcaps for example) described? I have the strong feeling to
>> search in the wrong place without any result.
>
> The * is used to assign a feature to the font and you could find a
> description in font-ini.tex /grep for \definefontfeature) but the
> better way is to use typescripts for your fonts.
Okay. That's what I'm trying to do right now.
> ConTeXt has the following features predefined:
> - default
> - smallcaps
> - oldstyle
Yep, I saw them in font-ini.tex, as you pointed me to.
> It is also possible to change the features of a font within the text
> with the command \setfontfeature{...}.
But, if I've understood the point, there is no reason to do that if I
use a proper typescript. Right?
Best regards,
-AJ
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-16 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 18:39 Antoine Junod
2008-04-13 19:04 ` Henning Hraban Ramm
2008-04-16 9:57 ` Antoine Junod
2008-04-14 8:23 ` Wolfgang Schuster
2008-04-16 9:59 ` Antoine Junod
2008-04-16 10:17 ` Wolfgang Schuster
2008-04-16 10:34 ` Antoine Junod [this message]
2008-04-16 10:56 ` Wolfgang Schuster
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=87prsqm6k8.fsf@zapata.tots-ns.net \
--to=toto@tots-ns.net \
--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).