ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jeff Smith" <ascarel@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: XeTeX old style numerals
Date: Sat, 18 Oct 2008 17:19:45 -0400	[thread overview]
Message-ID: <2e8813a0810181419r1a389ff5g5f7f9b55bf24704b@mail.gmail.com> (raw)
In-Reply-To: <115224fb0810140507u368c3a5fx32e105a4899e4332@mail.gmail.com>

Hi all! It's been a while!

I haven't been able to use ConTeXt since last spring, when my laptop
was stolen. I got a shiny new one a week ago (don't look at me -- it's
the insurance company's fault!) and now that I'm FINALLY back to
ConTeXt, I understand that a lot of time has passed since then and
that much must have changed.

So I would like to follow-up on this below.

By the way, I've installed the minimals and it works flawlessly. It
was a real pleasure to have ConTeXt set up and work in 5min. :-) (It
wasn't you guys' fault before, but mine).

That being said, I still use mkii and XeTeX. The typescripts quoted
below work for me also, but I would like to know again how to, or just
if I still can, combine this with \definefontfeature.

The thing is, I need more than oldstyle or smallcaps. I need frac=yes
for one document, and dlig=yes for another (those are the historical
ligatures contained in my font).

When I try to use my own set of features, something seems to stop
working: the trep feature. I get all the ugly apostrophes.

I made a dummy document using the typescript definition quoted below,
changed the font (I use Garamond Premier Pro) and I added the
following to use instead of default:

\definefontfeature[bodyfeatures][method=node,script=latn,language=dflt,liga=yes,onum=yes,kern=yes,trep=yes,dlig=yes]

I get the onum and dlig working with this, but, like I said, the trep
doesn't work. If I am not mistaken, it's this feature that makes the
apostrophe look like the comma. Am I right?

Can anyone help?

Thanks a lot in advance! It's very nice to be back to ConTeXt!
Jeff



On Tue, Oct 14, 2008 at 08:07, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
> The better way (works for MkII and MkIV):
>
> \starttypescript [serif] [minion-pro]
>  \setups[font:fallback:serif]
>  \definefontsynonym [Serif]           [MinionPro-Regular]    [features=default]
>  \definefontsynonym [SerifBold]       [MinionPro-Bold]       [features=default]
>  \definefontsynonym [SerifItalic]     [MinionPro-Italic]     [features=default]
>  \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic] [features=default]
> \stoptypescript
>
> \starttypescript [serif] [minion-pro-os]
>  \setups[font:fallback:serif]
>  \definefontsynonym [Serif]           [MinionPro-Regular]
> [features=oldstyle]
>  \definefontsynonym [SerifBold]       [MinionPro-Bold]
> [features=oldstyle]
>  \definefontsynonym [SerifItalic]     [MinionPro-Italic]
> [features=oldstyle]
>  \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic]
> [features=oldstyle]
> \stoptypescript
>
> \starttypescript [serif] [minion-pro,minion-pro-os]
>  \definefontsynonym [MinionPro-Regular]    [file:MinionPro-Regular]
> [features=default]
>  \definefontsynonym [MinionPro-Bold]       [file:MinionPro-Bold]
> [features=default]
>  \definefontsynonym [MinionPro-Italic]     [file:MinionPro-It]
> [features=default]
>  \definefontsynonym [MinionPro-BoldItalic] [file:MinionPro-BoldIt]
> [features=default]
> \stoptypescript
>
> \starttypescript [minion-pro,minion-pro-os]
>  \definetypeface [minion-pro] [rm] [serif] [\typescriptone] [default]
> \stoptypescript
>
> %\usetypescript[minion-pro]
> \usetypescript[minion-pro-os]
> \setupbodyfont[minion-pro]
>
> 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  : https://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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-10-18 21:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 18:07 Mohamed Bana
2008-09-19 18:57 ` Mojca Miklavec
2008-09-20  2:09   ` Mohamed Bana
2008-09-20 10:49     ` Hans Hagen
2008-10-11 20:10       ` Mohamed Bana
2008-10-14 12:07         ` Wolfgang Schuster
2008-10-14 17:16           ` Mohamed Bana
2008-10-18 21:19           ` Jeff Smith [this message]
2008-10-18 21:56             ` Mojca Miklavec
2008-10-19  0:47               ` Jeff Smith
2008-10-19 15:31           ` Mohamed Bana
2008-09-21  5:44   ` Yue Wang
2008-09-21 16: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=2e8813a0810181419r1a389ff5g5f7f9b55bf24704b@mail.gmail.com \
    --to=ascarel@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).